FabFilter User Forum
Pro-C 1.23 on Mac not compatible with Pro-C 1.21 on Windows
Hello,
I've got a big issue.
I recently started switching over to Mac from my old Windows setup. Everything was going well until I got to installing and testing FabFilter.
I used a lot of the V1 FabFilters in my older projects. I want to open them on my Mac without having pieces of the tracks missing. Besides Pro-C 1.23, all of the other legacy plugins (Volcano 1.21, Twin 1.21, Pro-Q 1.23, ...) work perfectly on Mac and I have no trouble with opening the old Windows projects, even though the versions don't match 1 to 1. It recognizes them as the same plugin and loads right up.
Pro-C is different though, I can't seem to get it to work. Cubase doesn't recognize the Mac Pro-C V1.23 and the Windows Pro-C 1.21 as the same plugin. Every project which I used the Windows version in just says that Pro-C is missing when I launch it on Mac, even though it's installed and works perfectly fine when I add it into a project.
Why is Pro-C the only one behaving like this? Is there another version that I could download somewhere? I really need it to work, exporting thousands of tracks to .wav isn't really an option.
Any and all help is greatly appreciated!
Here are some additional details I forgot to mention:
Please, Iād greatly appreciate any cooperation in resolving this issue. I've sent an e-mail to info@fabfilter.com over a week ago and still haven't received a response.
Hi Daniel,
We keep replying to your emails but it seems they are not arriving. Can you check your spam folder to see if our replies end up there? I'm trying to send you the plug-in file for Pro-C, but we can't send files over the forum. Please see our reply below:
Please note that the original Pro-C is one of the few discontinued plug-ins we have. These differ from our legacy plug-ins. All our legacy plug-ins are still included in our general updates, which means they are supported on all current systems including natively on Silicon Mac. The discontinued plug-ins have stopped getting updates quite a while ago.
It should not really matter what minor version of a plug-in you are running. For instance sessions that were created with Pro-C 1.21 should be able to be read by a system that has Pro-C 1.23. Can you insert new instances of Pro-C 1 in a session? Please note that there might be an issue with installing the latest version Pro-C 1.23 on modern macOS versions. In lots of cases you'd get a pop-up saying the installer can not be run.
Another issue could be whether you used VST2 or VST3. Please note that the native version of Cubase on silicon Macs does not support VST2 anymore. If you are loading a session with VST2 versions, they could fail to load.
First of all, please note that Pro-C 1 is not natively supported on silicon Macs. You'd need to run Cubase in Rosetta mode in order to access the plug-in.
Can you make sure you have Pro-C installed by checking if it's available from your plug-in list. If it is not, I've included both the VST2 (.dll) file and the VST3 file for the latest version. You can copy those files in the corresponding folders on your system and Cubase should scan for them during startup.
Hello, thank you for the replies!
I'm truly not getting any of your e-mails. I made sure to check both my ''all'' inbox and spam folder. I'm also not seeing any of the replies when I click on the message thread, I just see the messages sent by me. I even made sure to manually whitelist your adress, still nothing.
If possible, could you please try contacting me on another e-mail: (emailucetddf@gmail.com - I created it a few minutes ago.)
Cubase is already running under Rosetta, C11 doesn't have a native Apple silicon version. Those only started coming out with the release of C12 so that shouldn't be the issue. A lot of our older plugins are ''x86 only'' and work like a charm on the M4.
As far as I can tell, the MacOS installer worked just fine. Both the VST2 and VST3 Pro-Cs are in their respective folders and I can add then to a project. Once I receive the files, I'll test everything out and get back to you with the results. I'll try making a project with all of the versions and opening it on the old PC to see if everything carries over properly to that side.
I hope I'm just making a minor blunder somewhere. As I said, all of your other legacy plugins work perfectly.
Also, I'd like to apologize for sending those 2 additional follow up mails. I really thought you were giving us the cold shoulder. š