Vienna Symphonic Library Forum
Forum Statistics

181,814 users have contributed to 42,187 threads and 254,604 posts.

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

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. A strange thing in a Mac World with Cubase5 and VSL

  • A strange thing in a Mac World with Cubase5 and VSL

    P
    P

    Hi guy find this issue on my laptop. 

    Macbook Pro 17" unibody 2.8ghz 4gb ram MacOsX 10.5.8 
    Prosonous audiobox. 
    CUbase 5.1


    1.Open cubase-loading project (pretty heavy), all rocks!! 

    2.Close project-open an other one (also the same), cubase crash during loading instruments (some ViennaIns and Kontakts3.5) 

    3.Relounch cubase, everything is fine. 

    Notice this, when cubase crash i check my activity monitor in macos and a "VSL-server" is still in works using a lot of ram, i need to close this process forcely. 

    Seems that cubase doesn't have ram available becouse this process is still active. 
    My question is: Whena i close a project the ram return available with free space? yes. So why i've to close this precess by my self? 

    Is it a cubase bug or VSL?


    Strange things in MacWordl? 

    Thank a lot guys 
    Piernicola
  • M
    M
    last edited
    last edited

    Dear Piernicola,

    please let us know which version of Vienna Ensemble Pro you have installed and send this info and the crashlog (!) to our support.

    Thank you!

    /Regards,
  • C
    C

    "why i've to close this precess by my self? "

    From my experiences with Kontakt in Cubase, even with considerably more resources as you report, a 'heavy project' can simply max out your available RAM and cause cubase to quit. If you are running VE, which is what 'server' suggests to me, that is a separate process and isn't competing with Kontakt for RAM the same as it would as a regular VI plug in. If you are using VI as a plugin, with heavy instance(s) of Kontakt (with the Kontakt Memory Server not enabled), chances are high that this is no bug but simply a lack of available RAM to load as many samples as you are trying to.

    Have you enabled KMS? That alone might sort out your troubles here, if you have not.
  • P
    P

    Thanks,

    no, my KMS is not enabled!