Vienna Symphonic Library Forum
Forum Statistics

182,288 users have contributed to 42,217 threads and 254,748 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Rare crashs and other problems with VEP PRO 5

  • Rare crashs and other problems with VEP PRO 5

    J
    J
    Hello First let me say VEP PRO 5 is a great product , very very stable. I run it on a high end slave with 24 gb of ram, lot of SSDs, etc. The master is a mac mini server I7. 1) I occasionally get crashes but it's very rare. My VEP PRO is loaded around 16 gb ( i've 7 gb left ) with 7 instances ( loaded with kontakt / play mainly ) Do you think I load it too much ? 2) Apart from crashes, I ocasionally get big distortion sound. Yesterday I got that big distorted sound on only one instance , all the 6 left worked perfectly. The bad instance was loaded with a play instrument . ( a side note : the other instances also are mainly play instances mixed with kontakt ) I deleted that instance, created a new one , with the same instruments, and it worked back. Weird isnt it ? 3) Apparently with VEP PRO 5, the logic or cubase session directly saves the metaframe so you dont have to load the metaframe on the vienna server. Thats a very useful function ( you dont need to save the metaframe anymore ! ))) BUT, there seems to be a problem , again with East West Play. All my kotnakt instances load perfectly , and when it's time to load the play one, the loading hangs on "loading samples" windows of PLAY. And it never finish the loading. That problems doesnt occur when you load the metaframe manually. Too bad because that auto-save function is great... Thank you for reading me ;) j.
  • D
    D

    You shouldn't put PLAY and Kontakt in the same instance. That has always seemed to cause problems. As for the rest of what you say, I think that you should contact EW support, because as you say, it all works with Kontakt.

    DG
  • G
    G

    Hi John ,

    a)

    the burst of noise is actually & unfortunatley caused by PLAY , especially when a certain sample is not loaded correctly,

    or  when the overall free system RAM is getting too low .

    b)

    Especially with the big PLAY libraries Hollywoodstrings & Hollywoodbrass , but also with SD2 ,  it is  not a good idea to save

    the VEPRO metaframe in Logic ( or Cubase ) . The sample Data / footprint is quite large for the patches in these libraries , and

    although it is no problem to save those Patches when they are hosted directly in the sequencer ( Logic , etc. ...),

    saving metaframes which contain those PLAY libraries with your sequencer will not be successful .

    You should always switch on the "decoupled mode" for them in your sequencer and load them manually in VEPRO .

    c)

    You can run Kontakt and PLAY within the same VEPRO Server , however  all PLAY patches should load first ,

    before any Kontakt instruments get loaded. The best way to achieve that is to work with a more or less steady setup ,

    at least for a particular cue / song .

    To achieve this please do the following : ... in the VEPRO Server create the VEPRO instances that contain the PLAY libraries first ,

    then all VEPRO instances that contain Kontakt. Save this metaframe , and whenever you open this metaframe ,

    PLAY samples get loaded first  .. Any additional PLAY Instruments should be loaded directly  within the particular sequencer.

    Hope that helps ,

    best wishes

    Gerd