Ableton 11 Mac Users: Izotope Stuff, Ozone 9 etc. and other reportedly problematic VSTs work fine!

Discussion in 'Live' started by jackslab27, Feb 23, 2021.

  1. jackslab27

    jackslab27 Member

    Joined:
    Nov 25, 2019
    Messages:
    27
    Likes Received:
    13
    Hey,
    first up I am in Mojave running new 'inofficial' Ableton 11 from sister site, I know, sorry R2R, was just too curious.
    don't know if this is really news, or someone figured this out before, just wanted to share, after a little trial and error, how I got my VSTs of Ozone 9 and some other izotope stuff to work on Live 11, that initially would not open and could not be codesigned, similar to the issues on newest live 10 versions for mac on sistersite. this will probably work for lots of other plugs that were not working from live 10.1.13 on:

    1: right click on .vst file, click show contents. delete files named "Icon?", "Icon" or "_Icon" from within the plugin contents. could be multiple such icon files in there, mostly just one though.

    2. Open Terminal, run following two commands in this order:

    - xattr -cr [PLUGIN.vst]
    - sudo codesign -fs - [PLUGIN.vst]

    for n00bs, in place of the [PLUGIN.vst] I wrote here you put the path of the plugin vst File. just drag the file into terminal after typing each command. The Space before the filepath is part of the command and needs to be there or it wont work.

    Hope this works for you, Have fun!

    (I never downloaded sistersite ableton versions after 10.1, cause I didnt need any of the updates + people were complaining about the vsts not working, so I don't know for sure, but I'd assume this pretty much should also fix the same issues in the last Live 10 versions that were not running some VSTs, most notably izotope stuff)
     
  2. SamCH

    SamCH Member

    Joined:
    Nov 11, 2020
    Messages:
    22
    Likes Received:
    18
    [​IMG]

    everything is workin well without any extra manipulation.
     
  3. jackslab27

    jackslab27 Member

    Joined:
    Nov 25, 2019
    Messages:
    27
    Likes Received:
    13
    well, this screenshot shows you using the AU version, which we all know is working fine and not a problem, hence I was talking specifically about VST in this thread. Which in turn reportedly many people could not get working from 10.1.13 or so onward.
     
  4. manchesterraver

    manchesterraver Newbie

    Joined:
    Jun 9, 2019
    Messages:
    4
    Likes Received:
    0
    Similar stuff, Massive AU crashing Live 11
     
  5. ALKAWork

    ALKAWork Newbie

    Joined:
    Feb 26, 2021
    Messages:
    1
    Likes Received:
    0
    Hey @jackslab27 , thanks a lot for your advise. It worked for my Arturia plugins and Ozone 9. But certain Ozone plugins give me the following error when running through the last step: "error: The specified item could not be found in the keychain."

    In particular, I am trying to code sign Trash 2 VST 3 (64 bit). I have made sure to also reset permissions which I found was causing an issue for other code-signs, and show hidden-files to delete all 'Icon' files.

    Any idea how I can work around this?

    Thank you.
     
  6. MLooms

    MLooms Ultrasonic

    Joined:
    Feb 8, 2018
    Messages:
    66
    Likes Received:
    29
    For the VST to work, just create a folder under VST. Let's call it Izotope drag all Izotope VST's to it and use BatChmod and code design on that folder and that worked for me. I mostly use Audio units but needed once Massive to work as VST for some projekt and did the same and that worked for me no problematic of some sort. In my opinion no need to edit or to delete anything within the VST content. Just install CodeDesigner and BatChmod. I use Mojave 10.14.6
     
Loading...
Loading...