FabFilter User Forum
Analyzer/meter stop working on M1 Mac
FabFilter plugins suddenly stopped showing any analyzer, waveform, meter things.
I'm using Q3, C2, MB, L2 on vst3 format.
All of that plugins have same issues now.
M1 Mac, ver 12.6.7(Monterey)
I can tweak parameters of plugins, and it still change the sound.
It seems that anything but metering is working fine.
I'm forced to use plugins just with my ears(oh, nothing wrong? lol)
I updated plugins to latest version, but it didn't helped.
Is there any advice to solve the problem?
Shonosuke Namba — Dec 12, 2023
Hi Shonosuke,
What DAW are you using?
Sorry, I forgot to include that information.
I'm using Studio One 6.5.1 in native mode (not Rosetta2)
Could you see if this installer for Pro-Q 3 makes a difference:
www.fabfilter.com/downloads/test/ffproq323_metal_fix1.dmg
Thank you for suggesting.
I tried Pro-Q 3 with that installer, however it didn't make difference.
Processing on sound is active, but still no analyzer/metering.
This also happen with AudioUnit, or VST2 version.
I updated mac OS from 12.6.7, to 12.7.2
All plugins now working perfectly.
I don't get the cause of the issue, but the problem has been resolved for now.
I have the same issues. No meter moving. Everything else works.
Apple M2 Max, Logic Pro X.
Jason, what OS version and Ableton version are you using? Just the meter not working, the analyzer is working?
I also have this problem after upgrading to Ableton 11, ProMB still has the visualiser, but Fabfilter doesn't. Tried Au, vst and vst3 versions.
I'm using:
Ableton 11 suite
MacBook Pro (Retina, 15-inch, Mid 2014)
Big Sur 11.7.8 (loathe to update because something else will inevitably stop working)
Any advice very welcome, many thanks.
Hi Gavin,
Could you see if updating to the latest version of Big Sur (11.7.10) makes a difference? All similar issues were resolved with a minor OS update.
I have the same problem. No metering/spectrograms in any Fabfilter Plugin I use (Q3, L2, Pro-C2, Pro-DS)
No matter what format (AU, VST, VST3, CLAP).
On a Mac Mini M1 with Sonoma 14.0
Reaper and Bitwig same problem. Even after reinstalling the plugins and the hosts.
Could you see if updating to Sonoma 14.2.1 makes a difference?
I just started having the same problem. My DAW is Studio One Pro 6.6.2 on a MacBook Pro M2 Max 64Gb and OS 14.6.1. The analyzer and meter work if the plug-in is placed on the instrument track, but not if it is anywhere else (Fx, Bus, Main). I checked some older projects and on those the plug-ins work as they always have, but I can't get them to work on anything new. I downloaded the latest version of the Plug-ins and updated my OS, but it made no difference.
Similar issue here but only for L2 on the output bus (other fabfilter plugins are running the analyser fine). I can see the analyser when running the plugin on a track or on track stacks in Logic Pro X. Im on a Mac mini m1 running Monterrey 12.6.4
Hi Fabfilter team (or anyone else who could help!!!),
Please, is there a fix for the metering not working, or intermittently working with the Fabfilter C-2, L-2, or MB plugins?
Or, is there an update for the plugin's ?
I purchased the plugins on Jan 2, 2025 (couple of months preceding this post).
This issue use to intermittently present in Pro-Q 4 as an AU plugin. Therefore, I now reliably use the Pro-Q 4 VST plugin.
Plugins impacted for me..
- Pro C 2 (AU or VST)
- Pro-L 2 (AU or VST)
- Pro-MB (AU or VST)
My Rig...
- DAW: Reaper
- Version: 7.15 (macos-arm64)
- Computer: M1 macbook pro
- OS: 15.3.1
- RAM: 16GB
- Harddisk: 1TB SSD
- Space Available: 898GB
- Interface: Arturia Audiofuse 16Rig
- Monitors: KRK
I hope the above satisfies the, "What OS".. and system conditions question.
I would love to know if a permanent solution exists, or if there is an update that is the permanent solution, or if this is something that is in the works in future update!
The computer is for recording music (ie., no OBS or photoshop, games, etc....)
Thanks Everyone,
Earl
We noticed that our analyzers can stop working when you are not running the latest security update of your macOS. We're still puzzled by how not updating can make something stop working, but we're investigating. For now updating to macOS 15.4.1 should resolve the issue.