What I find strange is that nobody on internet reported this kind of bugs. I'm sure I'm not the only one with a 2019 macbook pro intel under sequoia and Logic...

 

Last edited: Dec 2, 2025 at 5:16 PM

Spoiler: Source: ChatGPT KI

️ What “black GUI” could refer to — and caveats

• On the official site, EQuilibrium offers a “custom-designed ... user-adaptable design” including a “configurable UI”. dmgaudio.com That suggests you may be able to customize colours or themes.
  
  
• HOWEVER — there are users reporting problems under macOS: e.g. “plugin not displaying correctly: buttons missing, no plot points, only analyzer works.” AudioSEX - Professional Audio Forum+1
  
  
• The manual notes that on Windows the UI uses OpenGL and has an option to disable it; but that option does not exist on macOS builds. AudioSEX - Professional Audio Forum+1
  
  
• This means if there is a “dark / black GUI theme” on Windows via OpenGL, it likely doesn’t carry over to macOS — or if it does, it may work imperfectly depending on your system/Daw. Several users report GUI-issues on macOS. AudioSEX - Professional Audio Forum+1

⚠️ What to check / what to expect

• If you install EQuilibrium on a modern mac (Intel or Apple Silicon), compatibility is supported. dmgaudio.com+1
  
  
• But “black GUI/dark theme” may not work reliably on macOS. Some users say the GUI breaks (missing controls, broken plot display). AudioSEX - Professional Audio Forum+1
  
  
• If you run into GUI issues: check you’re using the latest plugin version (currently 1.68) and update your DAW; and also check whether the plugin’s graphics settings are compatible on macOS (since some UI features like OpenGL are Windows-only). AudioSEX - Professional Audio Forum+1

✅ Conclusion: Yes — EQuilibrium can run on macOS (Intel or Apple Silicon), but if you heard about a “black GUI / dark GUI” that refers to Windows (OpenGL) version; the macOS version doesn’t guarantee a stable dark-theme. Many report graphical issues on macOS, so you should test with the demo before relying on it.

Spoiler: Source: ChatGPT KI - OpenGL Problem

On macOS Catalina → Sequoia, all VST/AU plugins that rely on OpenGL can show GUI problems — missing controls, black windows, slow rendering, or full crashes.
This is because of Apple’s long deprecation and partial removal of OpenGL starting in macOS 10.14 and tightening over each release.

Here’s what’s happening and how it affects audio plugins:

Why OpenGL Problems Occur (Catalina → Sequoia)
1. OpenGL is deprecated and not fully supported
Apple stopped updating OpenGL years ago.
By macOS 10.15 (Catalina) → 14–15 (Ventura/Sonoma/Sequoia):

• rendering glitches began
  
  
• context creation failures increased
  
  
• plugins using older OpenGL calls break
  
  
• GPU drivers behave erratically depending on Mac GPU
  

Plugins that haven’t been rewritten to Metal (Apple’s graphics API) can fail.

️ How This Affects VST/AU Plugins
Common symptoms:

• Black or blank plugin GUI
  
  
• Missing UI elements (knobs, curves, buttons)
  
  
• Analyzer not showing or only partially
  
  
• UI freezes
  
  
• DAW crashes on opening the plugin window
  
  
• Very slow / laggy GUI
  
  
• Plugins working in Rosetta but broken natively (Apple Silicon)
  

This matches issues seen in plugins like:

• DMG EQuilibrium / Compassion
  
  
• Old FabFilter builds
  
  
• Old Waves V-series
  
  
• Some U-he betas
  
  
• Many legacy freeware plugins (KVR-era)
  

Why It's worse on macOS 12–15 (Monterey → Sequoia)
Apple removed several “compatibility fallbacks”:

• Intel GPU OpenGL compatibility lost on Apple Silicon
  
  
• Deprecated GLSL shaders fail to compile
  
  
• Framebuffer handling changed
  
  
• Some DAWs isolate GPU contexts differently
  

This means a plugin that worked on Catalina might break on Monterey, Ventura, Sonoma, or Sequoia.

✔️ Workarounds (what actually helps)
1. Run the plugin inside Rosetta mode
Some OpenGL plugins work better when the DAW is launched under Rosetta:

• Logic Pro: “Get Info → Open using Rosetta”
  
  
• Ableton Live: duplicate app + sign it to run under Rosetta
  

Older OpenGL code sometimes works better in Intel emulation.

2. Disable GPU acceleration (if plugin allows it)
Some plugins have:

• “Disable OpenGL”
  
  
• “Use software rendering”
  
  
• “Legacy UI mode”
  

DMG plugins: this option exists on Windows, but not on macOS.
So DMG users have fewer fixes.

3. Use older plugin versions
Some companies released OpenGL → Metal updates.
Sometimes older builds work better under Rosetta than newer “half-Metal” hybrids.

4. Use a different DAW version
Some DAWs changed their GPU sandboxing:

• Logic Pro 10.7+
  
  
• Cubase 12+
  
  
• Ableton 11.2+
  

Rolling back DAW versions sometimes restores UI functionality.

5. Switch to Metal-based plugins when possible
Developers that fully migrated to Metal:

• FabFilter (latest revisions)
  
  
• U-he (most synths)
  
  
• Soundtoys (V5.4+)
  
  
• iZotope (recent builds)
  

These are future-safe.

In short
From Catalina → Sequoia, macOS killed off old OpenGL behavior.
Plugins still using OpenGL—especially older versions—will increasingly break:

• Black/blank GUI
  
  
• Missing controls
  
  
• Analyzer not showing
  
  
• Random crashes
  
  
• Better in Rosetta than native ARM
  

This is expected, not a bug: OpenGL is effectively obsolete on macOS.

If you want, tell me which specific plugin is giving you OpenGL issues (DMG? FabFilter? Others?)
I can explain the exact cause and provide the best workaround for that plugin.

 

If i tweak for exemple the dmg plugin and close it it crash 1out of 3 but if click on something else in logic for exemple another channel and close the window of the plugin after seems reduce the crashes. Still crashing...

 

Last edited: Dec 2, 2025 at 6:35 PM

Perplexity KI Answer as a PDF :

 

Arf this AI answers are going nowhere

 

What do they want to do now? Use a different plugin?

 

Last edited: Dec 2, 2025 at 8:02 PM

there is nothing particularly GUI heavy about this plugin. Do any other plugins do the same thing in Logic? Do you have any heavy Graphics using plugins? Did you try reinstalling it? They deauthorize very easily. Are you using Little Snitch to block your DAW, the plugin, and the domain? What about hosts file entry?

Get it to crash and when AUValtool (Logic) pops up the Window copy the top half of the error, or the whole thing; and pm me it.

The AI answers aren't going to go anywhere when the person using the AI has never even used a Mac before.

 

The problem it don"t even let crash report... and nothing in the console

 

luckily logic 11 backup well the project and load fast

 

did you try starting Logic with the plugins disabled, if that is a problem? I would remove it from the project and reload it. I would cleanly remove and reinstall the plugin or entire bundle. Or cleanly reinstall Logic. Downgrade Logic. Or pick another plugin to use. Does the rest of the bundle even do stuff like this? There's nothing special about just Equillibrium that it wouldn't likely have the same problem in others. It would be all of them.

Did you re-codesign everything when you updated MacOS? I'd probably try to do it again with just the one plugin....

 

Yes I tried everything I made a fresh install of the OS, Logic also and the plugins, I downgraded from 11.2.2 to 11.1.2 on which one I can at least open the projects without crashing on opening. Logic 11.2.2 crashed also on opening the projects with instances of DMG plugins...
Yes the suite TrackComp, tracklimit... have the same problems. Only Compassion and Pitch Funk are not crashing. The AuValTool validate all the buggy plugins.

Honestly I don't want to downgrade the OS. Sequoia is working fine for now except this problems and a few one with the wifi...

 

Last edited: Dec 3, 2025 at 11:43 AM

Here an exemple of the crash that I encunter.

 

I just tried Logic 11.2.1 the same problem... I had some hope because was the only version that i didn't tried. I think it's linked with Sequoia because even on Logic 10.8.1 the crashes are happening... but on ableton or thru patchwork all fine.
I don't know anymore what to do... I think i tried everything

 

Last edited: Dec 3, 2025 at 11:43 AM

You've really tried everything; there's nothing more you can do. Time to look for an alternative. How about FabFilter?

 

Ai again... I testes this command
Defaults write com.apple.logic11 AUCompatibilityMode -bool true

but didn't arranged nothing.

The AI suggest me this one also :
export MTL_HUD_ENABLED=0

export MTL_DEBUG_LAYER=0

export LIBGL_ALWAYS_SOFTWARE=1

open -a "Logic Pro"


Should i try ?


I'm pretty sure it's about the graphic used in the plugins so I try to force logic to not utilise the opengl of the plugins... What do you think ?


I have seen also that in the com.apple... in the preferences :

bplist00“Wglobals\loadingFlags_!{"FFT Update throttle":1,"AutoListen Enable":0,"AutoListen Gain":0,"AutoListen Q":0,"AutoListen Ignores Q":0,"AutoListen Disabled":0,"Solo Mode":0,"A/B Automation":1,"A/B Toggle":1,"Clip threshold":0,"ProTools Opt/Shift":0,"Band Linking":1,"Save Compression":3,"OpenGL":1,"VST Gestures":1}R-1


I changed OpenGl to 0 but also, not working...

 

OpenGL discontinued on macOS - August 6, 2018
In the future, there will be no more OpenGL on macOS. It's outdated technology, and everything is being switched to Autodesk's own Metal platform. As part of this process, Autodesk is withdrawing from the platform and now recommends Windows.

You no longer have OpenGL on macOS; you've already read that here, and besides, you can't disable it.Since the plugin in question works perfectly fine elsewhere, it's more likely due to faulty programming by DMG for your Logic and/or Sequoia.

If you had purchased it, you would ask DMG to fix it. If no one complains and reports the bug, there won't be an update.