![]() ![]() When I compared this it seemed to ring true. ![]() It was the general recommendation to disable hyperthreading and enable all core use because Reaper likes to manage it's own multicore use. The secret is to disable AfxP for any track with an incompatible 3rd party plugin inserted.Īround the time I discovered that bit I also turned hyperthreading off and set the CPU core use from 1 to the number of physical cores (8 in my case). Turning AfxP off globally however is throwing the baby out with the bathwater. The telltale for that is crashy behavior with nowhere near full CPU use. The only near show stopper I experienced was 3rd party plugins that don't work with Reaper's anticipative fx processing feature. Either the 36 input rig for live sound + multitrack recording or studio projects with 200-300 tracks and plugins with HD audio and 5.1 mixing. I also have a Mac Pro (2009 model in signature) and I haven't found a way to max it out with audio yet. I haven't actually investigated closely myself when/if/what conditions turbo boost kicks in normally when using Reaper. Is the link really only given in a youtube video? People usually do that when trying to hide things that otherwise get taken down quickly.Īnother of the premises is the stock OSX fan control will no longer work with this utility installed?! Don't like the sound of that! ![]() So this utility overrides whatever that restriction is? The premise seems to be that some apps will for some reason not let turbo boost engage normally when the demand comes up. Well, I initially see a lot of red flags here. ![]()
0 Comments
Leave a Reply. |