FabFilter User Forum
Pro C3 gui state not stored in preset?
Major aggravation: the state of the gui in Pro C3 is not remembered by a preset. I create a preset with the gui like I want it and the next time I insert an instance of Pro C3 and open said preset the gui layout is not remembered. Anybody else seeing this? Why is it Fabfilter can make such amazing plugins but fall down with something as simple as this?
Jack — Feb 2, 2026
Hi Jack,
Do you mean the actual plug-in size, or the expandable side-chain panel?
The plug-in size is not stored in a preset, but rather in the plug-in's preference file. If you adjust the plug-in size from the bottom left, the new settings will be included in the preference file. Any new instances of Pro-C 3 that will be loaded will use this size. Instances that were already inserted before the size change will remain their original size.
The expendable side-chain panel was a big discussion point. In Pro-C 2 the features in the side-chain panel were only active if the side-chain panel was open. Say you wanted an external side-chain, you had to open the panel to set this up and keep it open. If you closed the side-chain panel the external side-chain was disabled. This was a complaint we received often, as people wat to be able to close the side-chain window for various reasons but keep the settings they just set up.
In Pro-C 3 we decided to change this. Now hiding the side-chain panel does not disable the parameters anymore. Instead it will give some visual feedback whether something in the side-chain has been adjusted.
This also removed the necessity of opening or closing the side-chain panel when switching through presets, something that has always bothered us. Just like the window size, the side-chain panel setting is now stored in the plug-ins preference file and not in the preset.
Hope that clears it up.
I'm talking about the sidechain panel. I like to keep it open. So what should I do if I want it open all the time? A plugin should be able to store everything about a plugin instance and not just parameters in a preset. I consider this a fail that it does not do so. Every other plugin I use can store the entire state of the plugin in a preset.