I've been trying to crack this for weeks. There are tidbits of info strewn across the metropolis. But everything is written in a way that is confusing to say the least. I randomly found this zip containing info on how to patch ilok plugins.

I highly recommend doing this to the fullest. I fucked up my usr/lib and had to reinstall OSX. thankfully nothing was messed up. But seriously don't mess with your directory unless u know what ur doing.

You will need iHex free in the app store. You will also need to change the permissions to the files you change. Simply 'get info' and click the lock, go to the bottom change to read & write for it to work when you save.

So here is what the text file says :

1) Install your ilock demo downloaded from developer website
2) Right-click in plugin and choose "Show Pack Contents"
3) Go to "Contents/MacOS"
4) Open file inside with a text editor (preferably use a Code or Hex Editor, there's one in App Store called iHex)
6) When it opens press "CMD + F" to search for text
7) Type "/usr/lib/libstdc++.6.dylib" in search field, REPLACE ALL instances with "@loader_path/libstdc.dylib", and Save
8) Copy the included "libstdc.dylib" file inside this pack for your OS version and paste it into "Contents/MacOS" folder from step 3


So you do that for the iLock demo and then you do it for any of the plugins you need patched I did H3000 and it worked.

1) Install a demo or whatever comes in that eventide bundle pack

2) Dont Open. Go to where the component is located.--->Finder-->Computer-->Library-->Audio-->Plugins-->Components

3) Show packaged contents of the component---->contents---->MACOS

4.) Right Click open with iHex

5.) Do the same thing you did with iLok. (change instances, copy the file included into the same folder)

6.) Save and it should work.

Wondering if there are any sort of blockers like they have for adobe. I'm going to try this method with the other plugins in the bundle. Does anyone have additional fx folders for the h3000? Just wanted to pass this along.

Adios.

P.S. heres the original zip

http://www99.zippyshare.com/v/aJqcr18k/file.html

 

Sounds interesting.Will give it a go.Thanks

 

Thank you for the info man but I wonder why none of the Teams have done the iLok plug-in bundles this way for all the formats is going back to snow leopard and so on if somebody does end up doing this and uploading them to share he will be held in very high regard basically pre-patching everything so you can just put the VST AU and others in their place and be done

 

they will also be on the radar of the feds. everything can be cracked

 

have you tested this on anything other than h3000? blackhole? what about slate?

 

yes mines says licensesupportinstallermac.zip
you go to applications, right lick ilok license manager, show packaged contents, macos and then youll see the item you do the work on

 

whats slate? and no testing blackhole today. I want to redo my h3000 because i didnt get some of the fx presets I was hoping for like the demo video.

 

i looked up slate, is it better than kramer tape? Thats what I use from the waves collection

 

does this work for ilok 2? exponential audio/soundtoys 5 etc?

 

works on blackhole

 

So what exactly are you trying to achieve with this? Fully working cracks of software? And would this also stop legitimate plugins working correctly with iLok Manager?

Sounds cool though!

Thanks

 

Can this trick be use to crack protools HD on mac?

 

as has been mentioned it would help with pre-cracked plugs.

 

Now that’s Ingenuity. Thanks nupe.

 

I haven't seen that mentioned! But I just simply don't understand quite what this is about as the description is a little vague to my understanding. Essentially editing code within a plugin to make the ilok manager see it as registered?

I don't want to mess around with my existing version of iLok Manager in case something goes bad, do you know if it will have any side effects for my legitimate plugins?

 

I think its something similar as OPENSSH thingy only just you link not out to a modified OPENSSH libstdc.dylib in your system folder then linking it to a local libstdc.dylib file inside the .component as far as i understand it. I use OPENSSH and linking all the necessary .components with a hexedit to my libstdcXX.dylib in my system folder. It is just a more convienient (?) way

 

I tried it on U73b just out of curiosity. Followed the instructions to the letter (actually very easy) and it didn't work. I got this:



I'm not heartbroken as I plan on buying U73b when I get paid this week, but I was curious to see if it worked.

 

yes this is another workaround for the openssh crack.. I guess it works with the plugs we already know....

 

Thanks @404, do you know where I can see a list of those plugs? Also, would we have to find old DL's of those plugs (from when the OpenSSH method first appeared) . . . I would think that those dev's would have closed this "loophole" in more recent updates of their demo downloads.

 

@returnal you might find them on the "other" site, also search for openssh here or look at this thread https://audiosex.pro/threads/use-openssh-plugs-without-modifying-system.19163/
hope it helps