Hey there,

yesterday i was successful with bridging a 32 bit VST to 64 bit to make it work in Audiogridder on my Macbook M4.

Very cool

I used the Jbridge 1.75 Demo. Everythings working fine.
Now i bought the Jbridge and its crashing when i want to close the plugin window with the activated Full Version.
My nerves are really at the end, because i spent already much time to figure out how it works.

I already wrote the Support, but this situation is very special and i dont know if i get support for this topic.

So the only thing, i can imagine is: The Full Version tries to save data, or store the Information somewhere, when i close the Plugin window -) CRASH
The Demo version doesn´t save, as stated in the info box, when running the demo.
I already made the Plugin folder and JBridge Folder to 777 Everyone full access.

Maybe someone has a idea, i really would like to use my very old VSTs again

EDIT: Same Problem in Crossgridder in Crossover

 

Last edited: Jun 27, 2025 at 10:07 AM

Spoiler: Source: ChatGPT KI

Hey there,

First off—congrats on getting your old 32-bit VST to run on a modern M4 Mac! That’s already a big win, considering the layers of complexity involved (32-bit → 64-bit → bridged → AudioGridder → ARM). You're absolutely right that it's a very niche and fragile setup, and it's understandable that your nerves are frayed. Let’s try to narrow this down and get some stability back for you.

Likely Cause of the Crash
Your suspicion is probably correct:
The full version of jBridge is trying to write plugin state data on window close, which the demo intentionally skips. This would explain why the demo closes cleanly, but the full version crashes.

On macOS, especially on M-series chips running bridged software, any permissions or code-signing conflict during state-saving or inter-process communication can cause abrupt crashes.

✅ Try These Steps
1. Check Rosetta Compatibility
Make sure AudioGridder and the jBridge plugin host are both running under Rosetta, because:

• The bridged VST is x86 (32-bit),
  
  
• jBridge is x86 (emulated),
  
  
• If any one component is ARM-only, it could break IPC (Inter-Process Communication).
  

To force Rosetta:

• Right-click the app (AudioGridder or DAW),
  
  
• Choose "Get Info",
  
  
• Check "Open using Rosetta".
  

2. Sandbox / Permissions Conflict
Even with chmod 777, macOS System Integrity Protection (SIP) or App Sandboxing might still block full file I/O access from jBridge.

Try moving both:

• The jBridge plugins
  
  
• The bridged VSTs
  to a more permissive directory like:
  

bash
~/Documents/AudioPlugins/

Then re-bridge the plugin from there.

3. Run jBridgeM in Terminal and Monitor Output
If you’re using jBridgeM (the Mac version), try launching it from the Terminal to catch crash output.

bash
cd /Applications/jBridgeM/
./jBridgerM

Then load your bridged plugin via AudioGridder. Watch the logs in Terminal for any crash message when you close the window—it might tell you what file or API it's choking on.

4. Try Running It Outside AudioGridder
Just to isolate the issue: Can you open the bridged plugin directly in a DAW (like Reaper or Live) using the full version of jBridge and see if it still crashes when closing?

If it works in a DAW but not AudioGridder, then the problem is likely in how AudioGridder handles VST unloading or saving state.

5. Disable Plugin State Saving (If Possible)
Some bridgers or hosts allow disabling state saving. If jBridge has an option like "Disable saving plugin state" or "Don't persist data", try enabling it as a workaround.

Bonus: Debugging with Console.app
You can use Console.app (in /Applications/Utilities) to trace crash logs:

1. Open Console.app
   
   
2. Filter by "jBridge" or "AudioGridder"
   
   
3. Reproduce the crash
   
   
4. See the crash stacktrace or I/O error just before the crash
   

That might help pinpoint the issue to a file write, permission, or code signing fault.

Final Tip
You might consider wrapping your 32-bit VSTs into AUv2 with jBridge, and then using them inside a wrapper DAW (like Reaper running in Rosetta), then connecting that to AudioGridder. It’s a bit of a workaround, but can isolate the problematic bridge-to-AG interaction.

Let me know what happens with these steps, and if you'd like, I can help you comb through any Console logs or crash reports you can provide. You're very close to a working setup.

 

Thank you PulseWave. I appreciate your answer
But one Question: Are you a bot, or do you copy the questions to Chatgpt?

I luckily found the solution.
I checked the Audiogridder Server Logs and found this:

Code:

[11:33:25.331|worker|2e7c78] trying to hide an existing editor
[11:33:25.331|app|2dfd90] hiding editor: tid=0x4c8
[11:33:25.331|app|2dfd90] failed to hide editor: tid does not match a window owner
[11:33:25.331|worker|2e7c78] setting active window channel to 0
[11:33:25.331|app|2dfd90] showing editor: tid=0x4c8
[11:33:25.342|procwindow|2060cf0] error: can't update screen capture area with empty rect
[11:33:25.342|procwindow|2060cf0] creating processor window for [jBridge]Wizoo Darb

So i checked the Jbridge FAQ:

The seperate GUI mode, made it work.
I don´t know really why. But its working perfectly now.
Also Saving Projects and realoading

I will write a tutorial here today or tommorow how to make 32 bit Windows Plugins working on modern Mac

 

No, I'm a human from planet Earth. Yes, I simply copied your question into ChatGPT.

 

Okay.
Thank you very much for that.
Not everybody has access to GPT so you're really helping with that

Have good day my friend