Use OpenSSH plugs without modifying system

mmmmusic · Jul 11, 2019

Can anyone confirm if the Sonnox plugins with openssh work with Mojave? Based on the different answers above it's unclear.

SAPO · Mar 8, 2020

HPF said: ↑

short answer, there is no reference to libstdc++.6 ;) You try to change a non existing reference ... Just forget the DAW ... focus on the plugs ... you do not need to patch your daw! But you should codesign the hex edited dylib if on mac os 10.9+
Click to expand...

Hi ! Someone can tell how to codesign the hex edited dylib ? Thanks !

Edit: that's ok ! My bad, i didn't wait enough

Last edited: Mar 8, 2020

Manon42 · Aug 21, 2020

Hello all,

I would like to know if is it possible to have somebody who explains how to use OpenSSH without modifying system, for beginner

I tried to follow the steps describe from Belarri on the page 5, but didn't managed...

I'm on Sierra 10.12.6 and already downloaded hex fiend.

I really need to have access to the GRM tools.

Grazie!

Manon42 · Aug 21, 2020

To be more clear. I manage to do till the step 3. But then, if i understood well, the process is different for GRM tools?

Thank you.

Manon42 · Aug 22, 2020

Nobody?

Manon42 · Aug 23, 2020

I managed finally. I can open and use the plugins from GRM Tools but when i try to open Reaper and while it check the VST, I have an authorization error. Somebody have an idea? Thank you!

Edit : same issue when i tried to load the plugins on GRM Player

Last edited: Aug 23, 2020

Lenny Belardo · Aug 24, 2020

This thread started 5 years ago. I'm not sure there's much up to date info now.

Manon42 · Aug 24, 2020

Ok. It is sad because it seems that it miss me very little, i tried again to do it again today, but same issue. I can open directly the plugins but impossible to use it on DAW

Tiger Studio · Jun 14, 2021

DEKAR said: ↑

Good morning, after reading all the post has not even clear to me where I have to put the file libstdc ++. 6.0.9.dylib, I am installing the plug ins McDSP and I can not find the way and I'm really desperate, I appreciate any help possible.
Click to expand...

hi did u make it work 100% mcdsp plugin?

Tiger Studio · Jun 15, 2021

Kyrad said: ↑

Same here! Sonnox not working
Here is what i have testet so far.

Working ones:
- DuyEverythingBundle
- Antares7.6.8
- EventideBundle (Blackhole / H3000)
- Flux.Alchemist.v3.3.6.35839
- LX480Complete
- SlateVCC1.5.2
- Softube
- McDSP

Still need to Test:
- Altiverb
- Antares AVOX4
- clariphonic
- GRMTools
- TCElectronic
- UBK1
- VocalignPro4.2.2
Click to expand...

Hi can u help me with Mcdsp hd everything bundle for mac osx
how u install and copy lib file? can u show step by step
im using mavericks 10.9.5 that hav lib file in crack folder but when u install and copy in usr lib and lauch the pro tools 10.3.10 it skip asking for ilok ((

Tiger Studio · Jun 15, 2021

artattack said: ↑

Hello all. So I've wondered if this method could work and gave it a try. Now I have LX480 working on Studio One v2 (OS X 10.9.5)!

Important note: For this method to work you have to patch both the plugin file and the DAW

What I made was:

1. Changed the name of openssh's libstdc to libstXX++.6.0.9.dylib and altered it (please use my attached lib - 10.9.5 or do as the user Manta correctly described if your OS version is different):

Go to the openssh dylib file for your system, change in a hex editor (I used Hex Friend) the name libstdc++.6.0.9.dylib to libstXX++.6.0.9.dylib and save this file to your usr/lib/ folder

2. Copied that lib to /usr/lib using the terminal app:
sudo cp -p libstXX++.6.0.9.dylib /usr/lib

3. Linked the lib to the name "6" as the original lib (terminal):
cd /usr/lib
ln -s libstXX++.6.0.9.dylib libstXX++.6.dylib

4. Now it's time to patch the plugin. Go to the plugins folder (/library/audio/plug-ins/components) and right_click the .component (or .vst) you want to patch (in my case was LX480Complete x64.component). Choose the option "Open with -> Terminal".

5. Then navigate to the folder Contents/MacOS and read the plugin dependencies (terminal)
cd contents/MacOS
otool -L <your plugin file> (in my case otool -L LX480Complete\ x64)
NOTE: when the file name has space(s) like the above you should put a "\" character before each space

The output of the otool command was the following (note that the default system libstdc is a dependency for the Plugin as shown in the output):

LX480Complete x64:
/System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 44.0.0)
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 152.0.0)
/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 103.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 550.0.0)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 38.0.0)

6. Let's patch it! Just execute the following command:
install_name_tool -change /usr/lib/libstdc++.6.dylib /usr/lib/libstXX++.6.dylib LX480Complete\ x64

7. Let's now confirm that the library was patched into the plugin (note that now it shows our "xx" library instead of the system "dc" library)!
otool -L LX480Complete\ x64

LX480Complete x64:
/System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 44.0.0)
/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (compatibility version 2.0.0, current version 152.0.0)
/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libstXX++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 103.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 550.0.0)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 38.0.0)

Now we should repeat this process in our DAW executable file (it also needs to be patched). In my case it's Studio One 2. Make a backup of your .app folder before beginning, right?

8. Navigate to you DAW folder in Terminal:
cd /applications/Studio\ One\ 2.app/

9. Then navigate to the folder Contents/MacOS and read the plugin dependencies (terminal)
cd contents/MacOS
otool -L <your DAW executable> (in my case otool -L studioapp)

The output of the otool command was the following (note that the default system libstdc is a dependency for the DAW as shown in the output):

studioapp:

/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 47.2.0)
@executable_path/libipp.dylib (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/cclgui.framework/Versions/A/cclgui (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/cclsystem.framework/Versions/A/cclsystem (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/ccltext.framework/Versions/A/ccltext (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/cclnet.framework/Versions/A/cclnet (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/cclsecurity.framework/Versions/A/cclsecurity (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 19.0.0)
/System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 55179.13.0)
/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 744.19.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 945.18.0)
/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)

10. Let's patch it! Just execute the following command:
install_name_tool -change /usr/lib/libstdc++.6.dylib /usr/lib/libstXX++.6.dylib studioapp

11. Let's confirm that the library was patched into the DAW (note that now it shows our "xx" library instead of the system "dc" library)!
otool -L studioapp

studioapp:

/usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 47.2.0)
@executable_path/libipp.dylib (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/cclgui.framework/Versions/A/cclgui (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/cclsystem.framework/Versions/A/cclsystem (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/ccltext.framework/Versions/A/ccltext (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/cclnet.framework/Versions/A/cclnet (compatibility version 1.0.0, current version 1.0.0)
@executable_path/../Frameworks/cclsecurity.framework/Versions/A/cclsecurity (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (compatibility version 1.0.0, current version 19.0.0)
/System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 55179.13.0)
/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
/usr/lib/libstXX++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 744.19.0)
/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 945.18.0)
/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)

Now try it!

This is not a very complicated procedure, but it will make you sweat if you are not used to work in the terminal app.

The thing is that you need to edit the lib with an Hex editor and then execute several commands.

If you think I should detail more I can do it.

Cheers!
Click to expand...

hi did u make it worked with McDsp plugin hd everthing bundle for mac os?
im using 10.9.5 and i install mcdsp v5 open ssh then i copy lib file in usr lib folder than launch pro tools 10.3.10 and it skip asking for ilok ((
can u show me step by step with McDsp plugin?

Tiger Studio · Jun 15, 2021

SOURLITO said: ↑

What version of MCDSP?, I cant get lx480complete to work, what am I doing wrong. Sonnox also not working. I will try eventide
Click to expand...

hi can u show step by step how to do with McDsp hd everything bundle for mac os 10.9.5 ?
i installed and copy lib file to usr lib folder but it skip asking for ilok in pro tools 10.3.10

Similar Threads - OpenSSH plugs without	Forum	Date
Problem Propellerhead Reason 5 after instal libstcd++ (openssh plugs)	Mac / Hackintosh	May 27, 2015
Any way to get old openssh plugins to work in m1 native DAW?	Software	Mar 16, 2023
Openssh Big Sur	Mac / Hackintosh	Nov 19, 2022
McDSP Openssh on Logic Pro X	Software	Mar 4, 2022
openssh plugins in Reaper macOS	Reaper	Dec 4, 2020

Use OpenSSH plugs without modifying system

mmmmusic Newbie

SAPO Ultrasonic

Manon42 Newbie

Manon42 Newbie

Manon42 Newbie

Manon42 Newbie

Lenny Belardo Guest

Manon42 Newbie

Tiger Studio Newbie

Tiger Studio Newbie

Tiger Studio Newbie

Tiger Studio Newbie

PROFESSIONAL AUDIO LOVERS

Use OpenSSH plugs without modifying system

mmmmusic Newbie

SAPO Ultrasonic

Manon42 Newbie

Manon42 Newbie

Manon42 Newbie

Manon42 Newbie

Lenny Belardo Guest

Manon42 Newbie

Tiger Studio Newbie

Tiger Studio Newbie

Tiger Studio Newbie

Tiger Studio Newbie

Useful Searches