

I am curious what the disconnect is on this subject.

(It's black and white like an on/off switch.) Forget to disable AfxP on just one track with a 3rd party plug in a larger project and it crashes to its knees. Reaper is insanely powerful with very low CPU use in large projects (200+ tracks and just as many or more plugins with HD audio). I can tell you it doesn't work for any of mine (Waves, Soundtoys, Universal Audio). I've seen the claim before that AfxP was intended to work with 3rd party plugins. The anticipative fx processing doesn't need special support from the plugins involved, it works just the same for the plugins that are included in Reaper or 3rd party VST plugins.Īnticipative fx processing must be disabled for any track with a 3rd party plugin inserted or you can get system crippling performance.
