FabFilter User Forum

Pro-C, Pro-L and Pro-Q not recognised by Ableton Live 8

Hello!

I can't seem to get Ableton Live 8 to recognise my Pro plugins on my desktop, for some reason. I have a feeling it might be a 64-bit/32-bit thing, because it has no problems seeing them on my laptop. My desktop is running Windows 7 Home Premium 64-bit, whereas my laptop is running the 32-bit version of the same.

I initially thought the problem was caused by the fact that I initially installed the 64-bit plugins, and when Ableton didn't recognise them, I uninstalled them and installed the 32-bit versions. So, I did a bit of a clean up, deleting the folders that were created in My Documents\FabFilter and Appdata\Roaming\FabFilter before reinstalling the 32-bit plugins, but that didn't help either. I've even copied over the .dll files from my laptop, so I know the plugins in my VST2 folder are definitely the right ones, but Ableton just won't show them. It has no problems with some older FabFilter plugins I have (Timeless 2, Volcano 2 and Twin 2). Also, FL Studio and SoundForge can use them fine.

So I'm confused. It is perhaps a problem with 32-bit Ableton Live on a 64-bit system? Or is there something in the registry that's making it think they're 64-bit VSTs?

David T

Hi David,

It definitely looks like Live is encountering 64-bit plugins, perhaps in a different plugin directory than you think? I would recommend to remove all Pro-L/Q/C DLL files from your system. In Live, check all VST plugin directories that are scanned, and make sure you've removed the DLL files from all these directories. Next, do a fresh reinstall of the 32-bit plugins.

Cheers,

Frederik (FabFilter)

Hello,

Thanks for your response! I figured out what was going wrong in the end, and it was a quirk in Ableton. The Rescan button basically only does a fast rescan, so it still thought they were 64bit plugins. It seems that the only way to do a full rescan is to disable external VST support, and then re-enable it. Not particularly intuitive, but at least it's working now!

Thanks again.

David T

Reply to this topic: