Latest FabFilter Forum Posts

(Topic) regarding the new updates from FabFilter

Tue, 31 Mar 2026 19:31:29 GMT

Hi, I have: One, Twin 2 Micro FF Saturn, Pro-C 2 Pro-DS Pro-G Pro-L 2 Pro-MB Pro-Q 3 Pro-R Saturn 2 Simplon Timeless 2 Timeless 3 Volcano 2 Volcano 2 (Mono) Volcano 3... what do I do, to get the new updates? Will it update all my existing FF plugins or do I have to individually update them - one-by-one? thanks. F

(Comment on) instance button

Tue, 31 Mar 2026 18:19:44 GMT

Thank you if I’d known I wouldn’t have upgraded. Will you announce if they do this as it’s really handy to see the clashing EQs

(Comment on) FabFilter Pro-Q 4 VST3 Plugin Crashes in JRiver Media Center 35

Tue, 31 Mar 2026 13:06:12 GMT

Hi Thanks for the reply. I'm running the latest version of Windows 11 Pro. Asus NUC Performance 14. Here's a couple of them from Windows Event Viewer. If you need any additional information, please let me know. Faulting application name: Media Center 35.exe, version: 35.0.63.0, time stamp: 0x69c69fc4 Faulting module name: FabFilter Pro-Q 4.vst3, version: 4.1.1.12, time stamp: 0x69b823a7 Exception code: 0xc0000005 Fault offset: 0x0000000000125fd7 Faulting process id:...

(Comment on) Pro-C 3 not catching transients like Pro-C 2 and other compressors

Tue, 31 Mar 2026 09:44:20 GMT

Hi Mark, I'm afraid I can't seem to reproduce your issue here. When I load two tracks, one with Pro-C 2 and one with Pro-C 3, they will null out completely. I've tried different attack settings. There really should not be a difference between the two. If you're still experiencing differences, can you send over a project file so we can have a look?

(Comment on) FabFilter Pro-Q 4 VST3 Plugin Crashes in JRiver Media Center 35

Tue, 31 Mar 2026 09:34:22 GMT

Hi Mike, can you send us a crash report? What OS version are you using?

(Comment on) Pro-C 3 access to instance list

Tue, 31 Mar 2026 09:03:03 GMT

Hi Karl, For now the instance list can only be accessed from within Pro-Q 4. The plug-in intercommunication requires quite some data, and it can get messy very quickly if multiple plug-ins need to access all that information and control all other plug-ins. So for the time being the instance list is really a Pro-Q 4 feature only. Hope you understand.

(Topic) FabFilter Pro-Q 4 VST3 Plugin Crashes in JRiver Media Center 35

Mon, 30 Mar 2026 22:53:38 GMT

Hi, Last night I tried using the FabFilter Pro-Q 4 VST3 plugin with JRiver Media Center 35, and I am getting tons of crashing with it. I posted more about the issue on their forums here: yabb.jriver.com/interact/index.php/topic,143375.msg995151.html#msg995151 Any suggestions? Thanks!

(Topic) Pro-C 3 access to instance list

Mon, 30 Mar 2026 22:36:13 GMT

After trying Pro-C 3, I'm surprised that it can't open the plugin instance list itself. It feels weird to need a null instance of Pro-Q 4 to access a bunch of different compressors at once. Hopefully this can be changed in a future update. Until then, I think I'm gonna wait to upgrade.

(Comment on) Problems with external spectrum off

Sun, 29 Mar 2026 18:38:40 GMT

Hi Ralph, You don't need three instances to see an overlay of another track. If you have Pro-Q 3 on Bass and Kick, you can open one instance and select the other track for the external spectrum. Open the analyzer menu at the bottom bar of the plug-in. At the top right of the menu you will see SC with a small arrow. If you click the arrow you will see all other instances of Pro-Q 3, and you can select which one you want to see in the external spectrum.

(Comment on) instance button

Sun, 29 Mar 2026 18:34:56 GMT

Have you just updated to macOS Tahoe? There is a small issue when using Logic, but unfortunately that's on Apple/Logics side so we are unable to fix that. In Logic the area just above the plug-in name at the bottom has been made unclickable. This results in any button just above the plug-in name in our button bar becoming harder to access. There still is a small area at the top of the button that you can still click, but a large part of the button is unclickable. We've reported this to...