Vienna Symphonic Library Forum
Forum Statistics

197,882 users have contributed to 43,084 threads and 258,680 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. [SOLVED] Vienna Instruments Pro Takes 22 Minutes Per instance to load... WHY?

  • [SOLVED] Vienna Instruments Pro Takes 22 Minutes Per instance to load... WHY?

    A
    A

    When I load an instance of Vienna Instrument Pro in Cubase 6, it takes no less than 22 minutes for Cubase to load it. I just can't imagine why it would take so long just to load the VST instrument with NO SAMPLES. Then, if I build a Matrix and save it, that takes ANOTHER 20-minutes to save. So for a "work-around" I decided I would build my orchestra in Vienna Ensemble Pro. Well... the story gets worse... because even just unsnapping the instance of Vienna Instruments Pro takes 20-minutes!... with zero samples loaded! What a joke. Every task I do takes at least 20-minutes just for Vienna to "do it's thing"... This is just no damn fun at all. I've spent over $15,000 on my VSL and I can NOT even use it. This is just maddening. I've reported everything to tech support... that was 3 days ago and still haven't heard back. Frustrated, annoyed, and just flat-out pissed off at this point. My computer: Mac 10.6.8 2x2.93 GHz 6-Core Intel Xeon 32 GB 13333 MHz DDR3 Ram Thanks for any help, Brian
  • D
    D

    Are you using the latest versions of all software (including eLicenser, hint  hint)?

    DG
  • Cyril BlancC
    Cyril BlancC

    Are you using VI and VE Pro 8008 ? 
  • A
    A
    Yes.... thanks.
  • A
    A
    Yes... thanks.
  • A
    A

     Looks like this thread has changed to SOLVED, but no mention of what solved the problem..... ???
  • PaulP
    VSL Team
    PaulP

    Hi, 

    I assumed that the usual updates worked out fine. This actually solves around 80% of our support cases.

    Best, 

    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • M
    M
    last edited
    last edited

    @andyjh said:

     Looks like this thread has changed to SOLVED, but no mention of what solved the problem..... ???

    I had a remote session with Brian last night, and found that he had accidentally set the VSL content drive root as the Custom Data Folder. VI/VIP will then scan through the whole drive upon start, which can take a very long time.

    We will add some protection for this in an upcoming release.