Vienna Symphonic Library Forum
Forum Statistics

199,046 users have contributed to 43,151 threads and 258,882 posts.

In the past 24 hours, we have 3 new thread(s), 10 new post(s) and 58 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Cubase 10 hangs 6min after loading VEP6 on server

  • Cubase 10 hangs 6min after loading VEP6 on server

    P
    P

    Hi. I wonder if someone has the same issue.

    VEP is on a PC slave with window 7 and 64GB of RAM - Cubase 10.0.5 is on Mac HighSiera. 

    VEP 6 starts loading after staring cubase as usual. When VEP is ready (2 instances 21 + 15 channels - circa 48GB of used RAM) Cubase will take 6 min to show up on th Then every thing is working fine.

    I had updated VEP to 6.0.17226 but just rolled back to 6.0.17011. Same problem with both.

    My template takes a total of 21 minutes to load!

    Any help would be so apriciated.

    Thanks.
  • PaulP
    VSL Team
    PaulP

    Hi PBV, 

    Maybe reduce the AUDIO Outputs / Inputs in the VE PRO Preferences?

    Best, 
    Paul

    Paul Kopf Head of Product Marketing, Social Media and Support
  • civilization 3C
    civilization 3C

    The template will [tend to]  load faster decoupled from Cubase.

    Start with it, load it fully then launch the Cubase project. I don't know of any upside to having a large load coupled.
  • D
    D
    Not having this issue specifically but if I load the vienna server after cubase 10 instead of the other way around, the amazing elicenser software crashes. Has done this for years though not just with cubase 10 pro.
  • P
    P

    Hi. Thanks a lot for you responses.

    Ok. Reducing the Inputs/Outputs didn't help since I am using all them (32) and Cubase got very confused after doing so. Freezing for good after trying to reconect the missings I/O... I could not load my ongoing projects anymore (2 features in the making. I got a bit scared for while :-( ) Now I got it back to work

    Anyhow the very long time before the Cubase session completed the load and showing up didn't hapen before with the same template and  I/O counts.

    @Civilization Phase? 3 ;-)

    I always been confused about  decoupling and preserving. Hard to find the best solution. I used to decouple only  while working for saving time as the template takes several minutes to save.

    But I tried as you suggested; loading the template manually before Cubase and then connect Cubase with it and yes it's a good work around to skip this amazing long time for cubase to show up (right now more than 10 min!!!) Maybe that's the way to do for to be abble to keep the same template once for all? 

    Still I don't get why it started to do that. I think it was after updating VEP to 6.0.17226.

    @dereck no I don't have elicenser prob! But my VEP server is on a slave PC...

    Best,

     

    P.
  • L
    L

    Same issue here. Why should we have to decouple anyway. Should not have to work around. Not sure if this is a Vienna thing or a Cubase thing. Something happened somewhat recently. Did not have this trouble (guessing) more than a year or so ago. 
  • Dewdman42D
    Dewdman42D
    last edited
    last edited

    @leakybrain said:

    Same issue here. Why should we have to decouple anyway. Should not have to work around. Not sure if this is a Vienna thing or a Cubase thing. Something happened somewhat recently. Did not have this trouble (guessing) more than a year or so ago. 

    I have come to greatly prefer working decoupled.  It does mean I have to remember to save my VEP server instances as saved files seperately from my DAW projects, but working coupled, though convenient, ends up causing things to happen that I don't want to happen, sometimes reloading a long sizable VEP project because I changed the audio buffer or something.  Your DAW projects will be smaller, will load faster and you don't have to worry about VEP loading stuff automatically and taking a long time to to do it.

    Set decoupled and make sure to also set to preserved, so that the instance will not close unless you explicitly say so also.