I am experiencing audio spikes/dropouts when using jbridge

#I am experiencing audio spikes/dropouts when using jbridge plus#
#I am experiencing audio spikes/dropouts when using jbridge windows#

#I am experiencing audio spikes/dropouts when using jbridge windows#

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.

#I am experiencing audio spikes/dropouts when using jbridge plus#

(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: