Vienna Symphonic Library Forum
Forum Statistics

194,188 users have contributed to 42,912 threads and 257,929 posts.

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

  • vienna instrument startup problems

    hello,

    after installing my new vienna instrument with orchestral strings 1 (latest version of syncrosoft and vienna instrument software), I get the following message:

    "Der Schlüssel konnte nicht identifiziert werden:
    Das Format des Schlüssels ist ungültig."

    ( the key can not be identified, invalid key format)

    Reinstall, restarting etc. does not work.
    I use XP, Cubase SX.

    pls help me!

    thanx!

    Markus

  • ok, I got it:

    Do not install syncrosoft version 5.0.7.0

    Syncrosoft Version 5.0.6.2 works...

    Thats it.
    But I hate Syncrosoft now [:D]

    Markus

  • I've been reading about a lot of problems with 5.0.7.0 lately .. is this just a PC thing. Or does the Mac version suffer as well.

  • the one or other issue came to my ears (on PC) but maya confirmed today 5.0.7.0 is running fine on the MAC(s)
    christian

    and remember: only a CRAY can run an endless loop in just three seconds.
  • I'm on a Mac, and I still think the whole Syncrosoft issue varies from one computer to the other. It's *supposed* to work, but it doesn't always work on everyone's machines.

    I'm in the middle of a major headache right now and will dedicate some time this weekend to sort it all out. This has been going on for about a week-- started last Friday. I had to find other ways of finishing a demo because LCC 5.0.7.0 simply quit working.

    (Note: I've already done several days of troubleshooting of every imaginable kind, thanks to the advice of members here and the VSL team. No need to rehash the process at this time.)

    Golem said it best: unless the updates offer something specific to address a problem you might have, stick with what you've got until such time it stops working. I'd also like to stress that not everyone is having trouble with 5.0.7.0, which may be good news for some.