FabFilter User Forum

Possible VST conflict in Reaper?

Hi to the Forum.

Question about Fabfilter Pro-R installation in Reaper. . I just bought some Fabfilter Plugins. Pro-R is acting weird and sometimes become unresponsive . It will start responding again if I re- “focus” on it in the fx chain I am using. It also seems to need it’s own little “bridged” window open. (I am using the VST3 version though both appear in the fx menu)
I am also getting a "bridged” notification as in:
“ Fabfilter Pro-R (X86 Bridged)”. Is this expected from VST3?

Would it be helpful if I moved the VST3 components…
FROM (Fabfilter installation destination: )
C:\Program Files (x86)\Common Files\VST3
TO (Where most of my VST 3’s live):
C:\Program Files\Common Files\VST3

Is this "legal"? I am sureReaper will re-scan the new location. Also… Should I “hide” the VST components (the ones that are not VST3) so it only sees VST3?

It looks like the non-VST3 versions live nearby in:
C:\Program Files (x86)\Steinberg\VstPlugins . Maybe they are creating a conflict?

I am guessing Reaper is loading a "bridged" version that it does not have to.

Manny

Never mind - I downloaded the 32 bit installer instead of the 64 bit! Apologies,
Manny

Manny

Reply to this topic: