Vienna Symphonic Library Forum
Forum Statistics

182,713 users have contributed to 42,254 threads and 254,893 posts.

In the past 24 hours, we have 1 new thread(s), 5 new post(s) and 39 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. iLok Conversion Fails every time

  • iLok Conversion Fails every time

    B
    B

    Hi

    I have tried moving to the iLok version of Vienna Instruments Pro, on my Mac Pro under Monterrey. After the install, done with Vienna Assistant, previously created project tracks that contained patches loaded into Vienna Instruments Pro 2, now load BLANK. 

    I have experienced the same error attempting to load previously created VST Instrument Presets also. BLANK. (This is in Nuendo 12). I am not interested in Vienna Presets - this is not my issue. My instruments settings are saved by VST Presets, or track archives or projects.

    I tried rolling back to 2.5.18664 (the last version I believe before iLok) and the presets and project tracks now load again as originally saved out. So at least I am not insane. 

    Yes, I have updated the directory manager. Yes I am online. Yes I have updated my iLok and activated the relevant licenses. Yes I have taken this to support - and they say "weird enough, VI Pro indeed opened empty here as well. This is the first time I see such behaviour myself here on my system...".

    This is as far as support have gotten with this case. They offer no solution or even hope of one. They have had two weeks with it. I share here to discover if I am alone in this problem, and ask if anyone else is having this issue?

    As a test, to see if the issue is that my VST Presets or Projects were created on really old versions of VI Pro, I created a new Project track with 2.5.18664, saved this, then rolled forwards to iLok using Vienna Assistant and this, too, loads BLANK. 

    Also for the avoidance of doubt, I tested the whole of the above on a totally brand new (Silicon) Apple laptop. No dice.

    Needless to say, iLok and the transition to it is a complete non-starter for me. I am currently rolled back to 2.5.18664 and not feeling any too pleased with VSL, where I have spent a small fortune over the years. I frequently must revert to opening legacy projects as my clients often request remixes of tracks going back some time. This is called backwards compatibility and it is a difficult area for us modern composers - affecting how we approach archiving and loading our old work. Vienna Symphonic Library, for me  at least, has added to the stress of this with their iLok transition, as it has proven to be non backwards compatible. 

    I am in fact contemplating employing an assistant to, under the E-License install, load up EVERY SINGLE cue that I have created in the last 5 years, stem all the VSL tracks out as individual audio tracks, and let go of the VSL platform once and for all. 

    Ben Bartlett 
  • marnixM
    VSL Team
    marnixM

    Hi Ben,

    I was finally able to reproduce your problem from scratch here in-house and have notified our developers of this regression/bug.

    So for the moment, please stay on your (hopefully working) eLicenser-based system and I will notify you as soon as the issue is fixed.

    My apologies for the inconveniences and thank you for your patience!

    Best, Marnix
  • B
    B
    Thanks for your response and support emails. I am pleased that you have been able to repeat and verify that there is an issue with the backwards compatibility of the iLok version of Vienna Instruments on my Mac system. I also appreciate and greatly value the apology that you express. These forms of communication go a long way towards fostering teamwork and positivity. 
     
    My understanding is that I must wait for a fix from VSL, and continue using the eLicenser based libraries. I will hold on updating any systems (including OS)  that may affect eLicense functionality in the hope that I can once again resume full compatibility when your fix is release.
     
    Thank you.