Hi Don, many thanks for helping.
My processor is a 1.7 Ghz, intel core i5.
Quote:
Originally Posted by Don Schenk
Thank you serr.
@hermitcrab
What is the RT latency in Reaper's performance meter?
|
RT CPU is around 43 % after doing Serr's tips with only 6 tracks with 3rd party plugins with anticipative Fx turned off. 10 tracks in total. Previously RT CPU was 3%. I Did exactly what Serr said except for disabling hyperthreading. Will try that when i get CCC. Total CPU seems to have gone up a bit like Serr said.
Quote:
Originally Posted by Don Schenk
I asked serr about the AfxP settings, because I was curious about that. Did you set AfxP on globally and turn it off for the tracks with s-gear plugs?
Did you relaunch Reaper and your interface after a crash or after changing global settings?
|
Yes to both questions.
Quote:
Originally Posted by Don Schenk
My wife's MacBook has the i5 (a little bit faster one), and it runs Reaper with 3rd party plug-ins without a glitch. It is even running 4 threads. I tested Reaper with UAD plugs and other plugs first before buying a MacBook for myself.
|
Can i ask which OS is that please ?
Quote:
Originally Posted by Don Schenk
Thousands, if not tens of thousands of musicians are running Reaper on a Mac, and using various plug-ins The problem is not Reaper. It is something in your Mac causing the problem.
|
This is what is frustrating me and the reason why i am working so hard to to solve these problems before i conclude ( albeit very speculatively and sadly - as i will be missing out ) that reaper is not stable with Lion 10.7.5. I had everything set to default within Reaper until I started to get help from this great forum but I cannot say how much my OS problems ( if i have any ) are contributing to instability - i would love to know what they are ! I really wish i was one of those that reaper just works for without problems but that has not been my experience so far.
My poor knowledge with computers in general may well be responsible for some of my current performance issues ( OS related ) but certainly not all regarding reaper. There is a long list of plugins that have problems at the top of this page and it is not comprehensive. I have had it verified from the developers that the only two 3rd party plugins i now use have either bugs on reaper ( ignite amps AU, VST not yet verified but it is also looking to be crash related ) or are unable to/excluded from doing certain actions ( amp A/b swiching in S-Gear) due to unusual midi implementation by reaper. I have put in a bug report/feature request for this to Reaper. It is debatable whether the later ( midi ) problem is a bug in reaper or an unusual feature but it is certainly responsible for s-gear not being fully functional within reaper. I have given crash reports to s-gear dev and identified the problems for Ignite Amps AU which they are now working on a fix for ( after being able to repeat the bug on their new osx system ).
I probably do have some problems in my OS as it is over 3 years old now and with little maintenance unfortunately due to lack of knowledge ( not lack of trying ! ). I don't know how to diagnose and remedy them unfortunately but my system has been and still is totally stable except for with reaper. It is starting to get a little slower to startup and possibly do intensive tasks but i don't know how to solve that problem. If you have any suggestions then i would really appreciate them thanks.
Quote:
Originally Posted by Don Schenk
|
Wow, thanks for that. That is a lot of things to check. I have previously done most of them ( from focusrite's recommendations ) but will look into the rest asap.
Quote:
Originally Posted by Don Schenk
Eight months. Yikes! Obviously something worked for a while.
|
Reaper has not been stable from early on ( possibly from the start ) for me unfortunately but i started using 3rd party plugins early as well so i don't know how much is due to that.
Quote:
Originally Posted by Don Schenk
Have you now tried them?
So..... What happens if you record a lot of tracks without any plugs? I realize you want to use the s-gear, but just for testing purposes, create a project with 24 or even 30 tracks. They don't need to be long - 30 seconds is fine. Play guitar into each track - even playing the same 2 chords on each track if you wish. It's is not about the quality of music for this test. The purpose is to get a group of tracks into Reaper without any plug-ins of any kind.
What happens when you do this?
Now add one s-gear plug-in. What happens?
:-Don
|
The trouble is that most of the problems have always been intermittent and sporadic ( although getting more problematic lately ) and so difficult to diagnose. These include crashes, pops and crackles ( not recording related and even in raw audio without plugins added) , latency on playback and plugin problems ( both third party and Reaverb and ReaDelay and now to a small extent ReaComp ). The ignite amps AU problem was easier to solve as every time i swapped I.A plugins around in the signal chain on a track, Reaper crashed. It was repeatable. Thats the thing, most of these problems are not easily repeatable, and if they are repeatable the exact conditions to cause them have alluded me so far.
I have done as requested by Serr except for the hyperthreading. As mentioned it has dramatically increased RT CPU ( to ~43 % from 3 % i think ) but i cannot comment yet on stability as i have not had enough time to try it all out due to health problems. I also get confused at times so apologies to both you and Serr if i get mixed up or don't reply very soon. I will definitely let you know what happens though.
I should mention that both ReaDelay and ReaVerb have not worked properly for me since getting reaper v4.71 and now v4.77 but only recently ReaComp's meter has started flashing / flickering in an unpleasant way and i don't recall it doing that until recently. I have read the user guide sections on these and forum posts here related to these problems ) and implemented the preferences and problem solving tips gained but still no luck. Both cause all tracks within a project with sends to them to be delayed badly ( not latency or setting's related ) and have exhibited instability ( whilst in use ) preventing me from using them.
Thanks again.