FabFilter User Forum
Fabfilter Pro-C Missing Plugin in old Cubase projects
Hi there.
I recently switched to Mac from PC and reinstalled my Fabfilter plugins.
All of them works flawlessly and are correctly initialised by my host, Cubase 7.5 (64bit). I'm on OSX Mavericks.
When I try to open some of my old projects (August 2013-December 2013), it recalls all Fabfilter plugins correctly on all tracks EXCEPT for Fabfilter Pro-C. It states that it's a "missing plugin"
I can choose Pro-C in the list of plugins just fine as a new insert, and it works like it should. It can't however, recall the instances of the plugin that were used in the project already.
This has made me try to install as many different versions as Pro-C as possible to see, if I've had a version installed with a different VST ID. I've had to find installers for the following versions of the plugin: "v1.12, v1.14, v1.17, v1.20, v1.22, v1.23".
I've tried them all as VST and VST3 and all of them are loadable and usable by the host but all of them are still reported missing in the session, which means that I have to set up a new insert and go mix these sessions all over again.
I can't get my head around this. Every other Fabfilter plugin are functional just as they should be and are not reported missing for existing instances.
Have Pro-C changed VST-ID in one specific version? And in that case, which one?
Has it something to do with the host running on OSX and not Windows? And in that case - why are all other Fabfilter plugins recalled as they should?
I really hope someone can help me.
Thanks in advance
The only Pro-C version I haven't yet tried is v1.21. Could anyone maybe upload a demo .vst and .vst3 of the file so I can try it out?
Hi Frederik,
This is due to a mistake we made when creating the VST3 version of Pro-C: the Mac and Windows versions have different identifiers so they aren't compatible with each other. We can't really do anything about it unfortunately because that would invalidate earlier sessions using Pro-C on one of the platforms.
The VST 2 version doesn't have this problem. If you still have access to a PC running Cubase, you can recall the session, save the Pro-C settings as a temporary preset and then replace it with a VST 2 instance that will load correctly on Mac.
My apologies for the inconvenience!
Cheers,
Thanks a lot for your reply. It helps me tremendously at that is a solution I will definetly pursue. I know this is A LOT to ask, really, but I can't imagine being the only one who has run into or will run into that kind of scenario, so here goes: Could you guys maybe release a modified vst3 for support-issues like this one with identical identifiers along PC and Mac for Pro-C? Not as an official release, but as a legacy download for guys like me. Going in and saving plugin presets for all instances of Pro-C for several sessions could take days. I love your work and dedication to your plugins and fixing an issue like this with a modified vst3 for cases like this would mean the world to me. Thanks again for your solution. Best regards Frederik.
Believe me, we did consider this, but it would only aggravate the issue as your Mac projects would be totally incompatible with any other Mac projects created with the official version of Pro-C...
Cheers,
I was wondering about this. I had the same problem last month and wondered if it was an installation issue, so I haven't touched Pro-C since.
You know, I'd be happy to get a copy of Pro-C for Win and OSX with the same ID.
For old projects, I'll just keep a copy of the old Pro-C in the project folder, swapping out when things don't load. For new projects, I'll just use the new compatible ones so it's no longer an issue.
That really would save folks like us a ton of time, because I have to go back and forth between OSX and Windows pretty often, and I've had to avoid using Pro-C at all because of that.
Say, instead of bothering you to poke the software, could I just trade Pro-C for another compressor that won't collect dust and doesn't have inconvenient consistency issues? Pro-MB looks pretty snazzy ;)
You can use the VST 2 version of Pro-C on cross-platforms projects in Cubase if needed. The only thing is that it makes side-chaining more difficult, but there's a workaround for that described in the help file:
www.fabfilter.com/help/pro-c/support/vstplugins
Cheers,
Hi Frederik,
Could you release it as a plugin named Pro-C Bridger (or similar) – but with the OsX Pro-C Identifier? As the problem isn't to make new songs with a VST 2.4, but to convert all the old ones, and there's MANY of them.
I realise you don't want to create more confusion, but as stated, a legacy version would be much, much, MUCH appreciated.
Best regards,
-Ari
The problem is not with the VST2 plugin version of Pro-C: you can use the same sessions on Windows and OS X. The problem is with the VST3 plugin. So a workaround is to use the VST2 version of Pro-C (and Twin 2) if you need to use different platforms.
Cheers,
Yes, but my songs are allready in VST3, so it will take forever to
A: Change all my vst3's to vst 2
or
B: save the presets for each projects pro-c with vst3.
This problem makes working on my Mac laptop a complete waste of time. Why not provide a "super secret" link download to updated OSX versions for users who know understand what is going on here? Perhaps a link could be provided via email for anyone who requests one. Seriously though, it is unacceptable that a solution of any sort has not been provided yet.