![]() The same sort of applies there too, if the machine is under-scaled or there is some piece of hardware generating unnecessary DPCs and interrupts, adjusting thread behavior is likely not going to help but in general tuning it probably will help. Secondly, better to just control from within Reaper at the thread level since that is based on Justin's knowledge of threads dealing with audio and so on. I wouldn't discourage someone from changing process priority just to see what happens though - most experts become experts from trying everything. ![]() I have seen instances in non-audio scenarios where restricting an app to a particular core for example can be worthwhile but again doesn't really apply here. ![]() ![]() I also think it is a potential futile action via TM 'generally' because the need to do so is likely trying to get around the real issue - whatever that may be. I don't think the priority setting is permanent. I see, so setting this in TM is still relevent then? Is there a way to make the settings in TM permanent? Is there any other solution for this problem, or is this hard-coded into Windows 10? SO: Is there any way to lower the priority for these things? I surely don’t care if the screen has to wait for my audio.Įxcept, THESE THINGS ARE NOT LISTED IN THE TASK MANAGER > DETAILS WINDOW ! (Correct?) So I immediately thought, why not set these all to “normal” or even “low” cpu priority. So obviously, either the usb devices, or the graphics card / driver, are getting higher priority than my audio. If audio is playing, and I move anything in the GUI with my trackball, this causes a terrible sustained crackling! - And if I type anything on the keyboard, the audio completely drops out! When running at 96K and a 128 buffer, again, I can play any tracks and ay VSTi’s I want, and the audio is almost 100% clean. Perhaps such changes aren't needed at all, as long as the audio apps have a higher priority? (though I may completely defeat Explorer at some point, since I only need “Search / Cortana.”) I immediately set “PACE” to low, and also Windows Explorer. What about the four “Reaper Host 64…” processes listed underneath the main “Reaper” one? The article I read about this whole issue mentioned only the “main” DAW setting.įor now, I’ve changed them all, and so far it doesn’t seem to hurt, but can anyone comment on this?Ģ: Should any processes be changed from “normal” to “low” ?Īlmost all of them default to “normal,” and only a few cannot be changed. Maybe it should be set to “High,” so it’s above all the Windows stuff, but below Reaper? I run Traktor concurrently, so for now I’ve set that to real time as well, but I have no idea if that could be a problem. (I know most of them)ġ: Should any OTHER audio processes be changed to “real time?” (I can even set it to 64, with a little crackling, which to me is mind-blowing.)Įven though I will run this session at 256, I am using 128 or even 64 as a test bed, to see what other optimizations might be possible. (Which is crazy fast for the Lynx driver, giving a true in-out throughput of about 3 ms! I can even run this session clean (just barely) at a 128 buffer. I’m now running my large “live performance” session at 96K, with a 256 buffer, whereas before this setting I was getting minor but consistent crackling. Even with Reaper’s “thread priority” prefs set to “Time Critical,” the Task manager cpu priority was still set to “normal.”Ĭhanging this setting to “real time” made a HUGE difference in how small I could set my HW buffer. I thought Reaper did this automatically, when you adjust the buffering preferences, but evidently it doesn’t. I’ve recently become aware of the benefit of setting Reaper to a “real time” cpu priority setting, via the task manager. (Important info for those that didn't know about this, plus some important questions at the end, for anyone who understands this far better than me. SETTING CPU PRIORITY IN THE TASK MANAGER:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |