Those tweaks cut the usage on plugins like Amplitube and Neutron in S1 by 30% or more of what they were.
The 2 biggest culprits (for my situation) that I found to help remedy S1's faults were: disabling hyper-threading (i7 4770) and adjusting the OpenGL settings on my video card. We love S1 and there's no going back but get tired of the performance issues on what are relatively small projects. Plugin counts and CPU usage inside of Studio One suffer compared to some other DAWs. I suggest you try with the CPU monitor application that the OS provides.
So many scenarios, so hard to say what should be done. I've also heard of issues like this can be caused by errors in the coding by the plugin developer and not something wrong with the DAW, but that different DAWs deal with the error differently. I've experienced similar behavior with other processor intensive virtual instruments when comparing the two DAWs.īy the way, you cannot trust findings when comparing Reaper's and Studio One's performance meters. If you used the same preset, latency settings and quality settings, did you also use the same plugin format in both tests? VST2 or VST3 etc.Ĭan you open a processor monitor i the OS and monitor CPU and core usage while playing Pianoteq in each DAW? It could be that Reaper lets you use multiple cores for that single track while Studio One doesn't. I have not tried Pianoteq and have no experience with it. Issues like this can be related to quite a few different parameters.
0 kommentar(er)
