Hi everyone!

Just wondering if anyone would be so kind to enlighten me here? To keep it short and sweet, does anyone know if any of the Openssh releases from a few years back will work with OSX Mojave?

Can the Dlib file be modified to play nicely with the latest version of OS X?

Many thanks for any response in advance

 

Lol thanks for all your help. Appreciate it.

 

Just disable SIP and replace the dylib as always.No need to modify any files.

 

Works on High Sierra, try libstdc_10.10.2,make back up first.

 

Thank you fellas! So it should work on Mojave then? I know High Sierra is fine as I'm running that currently...

 

Hi @baldman
Do we need to enable csrutil again after?

 

only if you want to protect you OS from malicious idiots and such

 

The choice to re-enable SIP or not is entirely up to you. @statik makes a valid point. Just remember if you enable it, you’ll need to disable SIP if you update OSX so you can replace the .dylib.

 

Thanks guys. I chose to lose Altiverb the other day so I could have the Softube stuff back, with the Openssh way.
And I didn't think to re-enable csrutil again, but I suppose I should really.
I wondered if it would bork the Softube stuff, but obviously not.
Obviously I kept the old .dylib for if I'm desperate for Altiverb again. Hardly ever used it anyway though!
Thanks again.

 

you can use it and it working great on mojave I using it without any problem
or here someone posted how to using the plugin without replacing the dylib but rather to modifying the plugin path of the dylib to the new path
https://audiosex.pro/threads/use-openssh-plugs-without-modifying-system.19163/

here the command from the post

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!

 

Last edited: Apr 9, 2019

Hi guys sorry to bother but I'm going to try this today however I'm seeing that the commands for terminal are for studio one. Stupid question but what would be the appropriate commands for live 10.1 and high Sierra? Any help would be much appreciated before I go down this rabbit hole.

 

Last edited: Jul 10, 2019

do a search on all the sister-like sites (and...including the sister herself) for Adobe-Patched' or any by 'Captain Hook'. They're patched already and it's an easy install... and it doesn't 'mess with the system'. A total of ten in all. Search the above mentioned... for: Antares Auto-Tune v7.8.6, Altiverb 7.0.5, DUY Essential Bundle, Eventide Bundle 2.0.2, Kush Audio Clariphoni UBK-1, McDSP HD Everything 5.1.1 (a few plugs don't work), ReLab LX480 Complete v1.1B, Slate Digital VCC v1.5.2, Softube Bundle v1.3.10 and VocALign Pro v4.2.2. All are in AU and VST...
Some are very hard to find. You'll go thru a million dead links. But... they are out there... and work absolutely fine in Mojave...

 

Thanks I did read all 11 pages but no mention of high Sierra and live 10.1 is why I'm asking. I have altiverb, and downloaded autotune but the others I can't find from the sister site. We're they all taken down? Hopefully we can relink to the H00k version or Adobe patched ones.

Edit: found them all on audionews. Thanks for the recommendation. Will try this out.

 

Last edited: Jul 11, 2019

Hey Guys, All plugins work fine on Mojave/Logic 10.4.7 except Kush UBK-1 that I use a lot ... any help on this ? thanks

 

Yeah, I recall that happened to me too, on Sierra & LPX 10.4.4. Thankfully Clariphonic still works, but not UBK-1.

 

Have you tried the Adobe-patched version of Kush? Both AU work for me and im on high sierra

 

Ah. And UBK-1 is now working again! Strange. And Kush is fine, thanks.
No; not the Adobe-patched version, but the Openssh way, as I mentioned above.

 

I have tried so hard looking for the adobe version of UBK-1. I never have found it, I wish. The open ssh version doesn't work for me on mojave.

 

hello all friends. My system to have them fully working is different from yours ... but you have to have a copy of the system ... and without having it completely updated ...

I usually do it like that from HS, Mojave and now in Catalina. I go to the second system and copy and paste the dlyb on the main disk ... (I do it this way because it is the only way I found to modify the folder) You start the main disk and then install the system update (otherwise things will not work like safari ...) ... In previous versions I directly reinstalled the operating system on top. but in catalina he told me that he could not reinstall catalina. and install a pending update.

Hope this method helps someone.

 

Yeah, that's an interesting workaround I discovered after knowing how to do it properly, but it's wrong.
If you had followed the original way, you would have understood to create a zip in situ of the old dylib file and replace it with the new one, all with top admin privs.
And the folder is a hidden folder too, I think.

Shouldn't be needed.

Great! Due to what we do around these parts , I don't know of anybody who has used Safari in over 10 years and hasn't deleted it instantly!
Why would you use it? And knowing what you know of Apple?

Well, the update install is just a newb thing and you can avoid that, but yes this will almost certainly be the same with Big Sur.
We know this.

Sorry, but it's not really a method because you didn't have to do half of what you did! lol.
You need to do it properly as I said.