Vienna Symphonic Library Forum
Forum Statistics

183,169 users have contributed to 42,281 threads and 255,001 posts.

In the past 24 hours, we have 6 new thread(s), 18 new post(s) and 63 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. Can't load patch
  • E
    E
    last edited
    last edited

    @Conquer said:

    You're doing this on the 'Patch Assign' page, right?

    Yes. The 1x1 matrix is A1. It seems like a bug to me too, because when I delete the instrument and then create it again, all works fine, until the bug occurs another time.

  • C
    C

    I see - is the 1-cell matrix something you created from scratch, or did you edit a VSL matrix?
  • E
    E

    The 1x1 matrix into which I load is the default empty matrix whenI open the instrument first.

    It happens like that : while composing I load a patch to try it out, then I replace it by another patch, and again another, and so forth, and suddenly it gets locked.

  • C
    C

    OK - as you say, you're only using one patch at a time so you shouldn't be running out of RAM. Have you tried opening the VI standalone outside Cubase to see whether the same problem occurs?
  • E
    E

    No, I have never opened a standalone of an VST-Instrument (I even don't know how I should manage the connection with my sound card).

    Of course my RAM is also used by other instances, so theoretically it could be the RAM.  But I don't belive it since the empty patch can't be loaded too and since the matrix is locked to its size.  These things don't have anything to do with the RAM.
  • C
    C
    last edited
    last edited

    If you look inside the Vienna Instruments folder on your PC hard drive you'll see a program called ViennaInstruments.exe. Clicking on that opens the standalone player. Hooking it up to your sound card is easy - once you've launched the standalone VI, select Options -> Configure (top left on the UI) and select your sound card and MIDI interface from the menu that appears. This selection won't affect the running of the VI in Cubase.

    It's best to open the standalone with no other programs running. It takes time to load (maybe 2-3 minutes), after which you'll see the same interface on screen that you're used to working with in Cubase. The advantage of doing this is that you'll be able to establish whether the bug has anything to do with Cubase!

    @elsner said:

    Of course my RAM is also used by other instances, so theoretically it could be the RAM.  But I don't belive it since the empty patch can't be loaded too and since the matrix is locked to its size. 

    I agree, but to be absolutely sure it's not a RAM issue you should test it using a single instance.
  • E
    E

     I opened the standalone.  It seems to work fine, at least during the minutes I tried...

  • C
    C

    Great - if the problem never occurs with the standalone VI, you'll then know it's likely to be a Cubase issue.
  • E
    E
    last edited
    last edited

     

    @Conquer said:

    Great - if the problem never, you'll then know it's likely to be a Cubase issue.

    I don't know that it NEVER occurs with the standalone VI since I didn't spend much time on the standalone.  And it doesn't happen all the time within Cubase.

  • C
    C

    Those intermittent faults are the worst. Good luck with discovering the cause![8-|]