Restoring Missing Plugins

Hi,

When you upgrade a plugin, or move one or something similar, when you open your Live set you get a message saying "Some plug-ins could not be loaded and are disabled".  

So, for example, I upgraded my Native Instruments Komplete.  So I no longer have Absynth 3, I have Absynth 5.  All of the sounds that were in 3 are also in 5, so I just have to go into Absynth and find the new path to the sound I'm interested in.

But I don't remember each sound I used to use, and I don't really feel like auditioning 500 synth sounds (that's per plugin). Is there a way to get, from the information about the now-disabled MIDI track, the name of the sound we were using in the old version of the plugin?

Thanks!

Aaron

13 followers

GroverGrooves 4 years ago | 0 comments

10 answers

  • [daw] Ableton staff
    contribution
    202 answers
    237 votes received
    2 votes

    Hi there, 

    The issue you are experiencing is related to the way DAWs and plugin manufacturers deal with plugin IDs. Basically if you install Absynth 5 when you previously had Absynth 3 installed, Absynth 5 is a new plugin, with a totally new ID. 

    Therefore Live can not simply adapt the settings from Absynth 3 in your set. Incremental updates, like going from version 5.0 to 5.1, usually don't get stamped with a new ID, but with major updates of your plugins it is mostly unavoidable to manually load the according preset again. 

    Best ,

    David

    3 years ago | 0 comments
  • jmgeorge
    contribution
    1 answer
    2 votes received
    2 votes

    No answers I'm afraid, but I wanted to point out in turn just how useful it would be to have a feature that would enable you to relink with the missing plugin in the advent of it having changed name since you last loaded the project (therefore causing the "missing plugin" error).

     

    Why ? Because :

    1) plugins that change names due to a version update (typically Vn to Vn+1) is a very frequent issue

    2) There's every chance that the patch that you were using in the missing plugin kept the same reference in its updated version*, and of course that information has to be stored somewhere in the Live project along with the rest of the track parameters, so it's stupid not to be able to access it.

     

    (*) The vast majority of VST / sound library manufacterers out there are smart enough to maintain consistent patch-lists from one version update to the next, short of which they wouldn't be around for long.

    9 months ago | 0 comments
  • GroverGrooves
    contribution
    3 answers
    3 votes received
    1 vote

    Bump.

    4 years ago | 0 comments
  • GroverGrooves
    contribution
    3 answers
    3 votes received
    1 vote

    It's a year later.  Anything?

    3 years ago | 0 comments
  • JamesMiles
    contribution
    34 answers
    21 votes received
    1 vote

    Not as far as I know.

    Should'a named the track after the preset...  Or printed it to audio.

    Grammy organization has a document on guidelines for DAW's when collaborating with other engineers/producers or archiving projects.  Good guidelines for organizational habits, and insulating yourself from an "upgrade derail"

    http://www.grammy.org/recording-academy/producers-and-engineers/guidelines

    http://www.grammy.org/files/pages/DAWGuidelineLong.pdf

     

    3 years ago | 0 comments
  • seanclark
    contribution
    1 answer
    1 vote received
    1 vote

    Hi,

    I am experiencing the same problem here. My laptop was damaged and i had to transfer my projects over to my new laptop. Upgrading Komplete in the process as Komplete 7 was not longer compatible to install with OS X Yosemite. I now have Komplete 10 running

    When i load up all my previous projects i get the same message saying "some plug-ins could not be loaded and are disabled"... Is the only way to fix this going through manually finding and re-loading the old preset used? Or is there another possible solution? As that seems very long and tedious

    Regards,

    Sean

    3 years ago | 0 comments
  • Jake Blue
    contribution
    1 answer
    1 vote received
    1 vote

    Anyone? This is doing me head in...

    3 years ago | 0 comments
  • NickDesigner
    contribution
    1 answer
    1 vote received
    1 vote

    For me the important thing that is being lost is the automation. It would be nice to be able to copy the existing automation envelopes to a instance of the newer version of the plugin.

    I have found that it is possible to see the envelops in the track automation still, so I'm going to try to copy them over manually.

     

    2 years ago | 0 comments
  • Pirkka
    contribution
    2 answers
    5 votes received
    1 vote

    It would be awesome if Ableton was able to store the preset names somehow, so that users would not have to go through all that trouble. 

    Not sure if that would be feasible technically (I have no idea in what format the preset info is stored within Ableton or the plugins). 

    While lacking this type of solution, I thank JamesMiles for the guidelines. 🙏🏻

    2 years ago | 0 comments
  • twobob
    contribution
    6 answers
    7 votes received
    1 vote

    Okay so I did some research. When the ALS file is unzipped to XML the selected program will be listed as <ProgramNumber Value="0" />  (no helpful name, 0 offset index)

    IF and I say IF you are lucky enough to have a VST that lets you select the presets from the LIVE :: "DEVICE :: SELECT VST PRESET" dropdown dialog then this value WILL be the offset from the presets like

    <ProgramNumber Value="1" /> (second choice in list)

    However many of the vsts seem to proffer no helpful semantic values in their respective section of the XML.

    Others are very welcome to have another look.

    So: In some cases you can do this. in others (like Kontakt, sadly) you are possibly stuck


    (I tested altering the stored values and Yes, you can update the selected preset via adjusting the XML, thus that is the right data for some of the cases)

     

    TEST:

    Make XML
    d:\Mirror\bin\test\test Project>d:\mirror\bin\cat test.als | d:\mirror\bin\gunzip > test.xml

    Edit the XML:

    <ProgramNumber Value="0" />  to be <ProgramNumber Value="3" />

    Make ALS
    d:\Mirror\bin\test\test Project>d:\mirror\bin\cat test.xml | d:\mirror\bin\gzip > test.als

    Observe that preset choice 4 has been selected in the project. It is. PASS.

    One can test with the VST's here https://www.fullbucket.de/music/vst.html  they respect populating and selecting from the Live :: DEVICE :: SELECT VST PRESET dropdown list

    Further details might possibly be gleaned from the stuff in https://www.steinberg.net/en/company/developers.html - The BUFFER value may contain Data that initialises the VST with that information - perhaps a Live dev can give a nod on that.  It may just be the last served audio slice. Hope it helps someone

    5 months ago | 0 comments

You need to be logged in, have a Live license, and have a username set in your account to be able to answer questions.

Answers is a new product and we'd like to hear your wishes, problems or ideas.