FabFilter

Hello,

A couple of weeks ago my Pro-MB visual analyzers stopped working entirely. The audio effect does still work. I tried reinstalling but it still has the same issue. Has anyone else run into this?

Plugin Version VST 3.7.9
Cubase 14.0.32 Build 342 (Apple Silicon)
Apple M4 Sequoia 15.6.1

Oops, Plugin version says 1.31

I just started having the same issue with Pro-MB last night

Issue persists in both VST3 and AU versions

Running a 2021 Apple M1 Pro MacBook Pro
Running on OS Sonoma 14.6.1
DAW: Ableton Live 12.3.6

FabFilter, is there any way other than updating to the latest MacOS that I can resolve this issue?

Is there a way to do a "security update" without updating my OS?

I see in years past, users resolved it by updating their OS. But the problem with updating to the latest OS, is that sometimes it causes bugs in various plugins and software that were otherwise running smoothly. And ofc as you know it can be a big issue if my DAW sessions pull up with a different mix than what I sent to a client a few weeks ago (ie because, say, my Waves S1 imager and Sonny Inflator are suddenly bugging out).

I made no system or Ableton updates between when the ProMB analyzer was running smoothly and when it stopped functioning.

Thanks,
Michael

When you don't see an analyzer or any meters in the plug-ins, it's very likely that you're not running the latest security update of your macOS version.

We have seen that when Apple releases a security update that is not being installed, the visuals can stop working. We are puzzled by this as well, since this means that a properly working system can stop working correctly by not updating. We have not seen that before..

It seems that even with automatic updates disabled Apple can and will still make changes to your macOS automatically. Lots of these times these security updates include fixes or updates for the graphics drivers, but we have not been able to figure out what part of this causes or visuals to stop working. We're still investigating, but for now we can only suggest running the security update for your current MacOS.

Please note you don't need to update to the latest fulll macOS version. We totally understand that is not possible. Just the security update for your current macOS version. e.g. 15.6.1 to 15.7.4 should resolve the issue though.