View Single Post
Old 12-08-2017, 11:46 AM   #31
serr
Human being with feelings
 
Join Date: Sep 2010
Posts: 12,562
Default

Still waiting for the punchline...

Homeopathic audio effects!

The CPU processes floating point math at different speeds depending on what the numbers input to it were?! Sure. Just like this guy I talked to once swears he can tell if a wav file was ever zipped! (Same exact set of ones and zeros that nulled with the original. He could tell. He told me so.)

If this was something real that someone played telephone game with, what was the original story that got this twisted?

If your CPU starts failing floating point operations your computer would just kernel panic if it did anything.


Back to misbehaving plugins...
Giankam, did you try disabling AfxP just on the track? (NOT globally in preferences.) How about the other tips?

What is the largest PDC you see on any track?

You can also try controlling the sample rate and block size for the connected audio interface from outside Reaper. (Uncheck those boxes next to the parameters in Preferences/Audio/Device and use a 3rd party app. Usually your OS audio utility or a control panel app written for the interface.) Reaper gives you these options to deal with all manor of stubborn devices.
serr is offline   Reply With Quote