Vienna Symphonic Library Forum
Forum Statistics

190,284 users have contributed to 42,728 threads and 257,087 posts.

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

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Play and Ve Pro 32 bit crashing!

  • Play and Ve Pro 32 bit crashing!

    D
    D
    Hi, Im using VE Pro 32bit server for Play 2.0.18 and 64bit server for Kontakt,Ominsphere on my master Mac Pro(no slaves)in Protools. When I Open VE Pro 32 bit server and 64 bit server,there are no active instances,I then launch Protools (re-opening a session with Ve Pro)and Ve Pro connects automatically to the servers and starts loading both at the same time. Is this the right way to open and load VE Pro servers and Instances? Is there a way to load the 32 and 64 bit servers one at a time? should the saved VE Pro projects(viframes)be located in the VSL custom data folder? also In the middle of midi editing I hear a click then the Play audio engine keeps stopping,then when I try to disconnect Ve pro 32bit it just hangs then Protools hangs then I have to force quit everything. The 64 bit (KontaktOmnisphere)works fine with no problems,any suggestions or ideas as to what might be the problem? Sorry for all the questions! MAC Pro 8 core,2.26 Ghz,16Gb Ram.3 x internal drives(for samples,Audio) OSX 10.6.4 Protools 8.0.4/Digi 002 Rack.
  • PaulP
    VSL Team
    PaulP

    Hello darkmatter,

    here are some answers to you questions:

    1) Is this the right way to open and load VE Pro servers and Instances?

    => Yes.

    2) Is there a way to load the 32 and 64 bit servers one at a time?

    => If you don´t launch one of the servers, it will not load any samples. What would be the advantage, if I may ask?

    3) should the saved VE Pro projects(viframes)be located in the VSL custom data folder?

    => They can be saved wherever you want them.

    4) also In the middle of midi editing I hear a click then the Play audio engine keeps stopping,then when I try to disconnect Ve pro 32bit it just hangs then Protools hangs then I have to force quit everything. The 64 bit (KontaktOmnisphere)works fine with no problems,any suggestions or ideas as to what might be the problem?

    => Play works fine in our environment. Is there a reliable way to reproduce this? Can you check whether this happens with PLAY as a plug-in with the given arrangement, without VE PRO involved?

    Thanks,

    Paul

    Paul Kopf Product Manager VSL
  • D
    D
    Hi Paul, (Big thanks for all your replies and advice so far!) 1)What I mean is,can I launch the servers and open Protools without the Ve Pro instances connecting automatically and the instruments being loaded.Would 'decoupleing' the Ve Pro instances before closing the Protools session stop the instances from connecting automatically each time I open the protools session.( i ask this because I want to load the 32bit ve Pro instance with Play first but at the moment Kontakt is loading first,I think this is causing the problem. 2Im experimenting with Play as Plugin without Ve Pro in Protools with same arrangement,i'll let you know.
  • W
    W
    last edited
    last edited

    @Paul said:

    => Play works fine in our environment.

    Have you experienced the 'noise burst' that people are experiencing with Play?  I've had it happen several times.  I load a metaframe (64 bit server) containing my setup instances (Play, Kontakt 4, Vienna).  Several times when I play a sound in StormDrum2 Play,  the sample plays for a second followed by a huge distorted +0dbFS burst from one of the channels.  OUCH!   Upon reloading the Play preset (16 channels of sounds), it plays as expected.

    This has been reported over at SoundsOnline Forums.

    - Greg
  • W
    W

    Have you tried just manually launching the servers independently, and loading metaframes into the 32 bit server first, then the 64??  When the servers are already loaded, and you launch a ProTools sessions with VePro 'coupled' to the instances (as in a pre-made template), the sounds don't actually load (i.e. VePro does not go into its loading routine like it does when first loading).  Each instance has an arrow button that you can push to refresh the sounds, but you don't have to do that if the sounds are the same. 

    This may do what you are looking for.  

    - Greg
  • D
    D
    Hi, I had these white noise bursts in Play too,I rang EWQL support and they suggested I change the voices to 512 and the engine level to low which cleared up the white noise for me. I also set the number of threads in VE Pro to 8 for one instance or 4 for two instances etc. In Protools I use 7 threads,512 buffer and cpu at 99%,when Im mixing down I set the Protools buffer to 1024 as latency isnt an issue when mixing obviously. these settings cleared up and clicks and pops for me aswell. re Play and Ve Pro Crashing/hanging: After saving the viframe or metaframe I then decouple all instances in Protools(this stops Ve Pro from automatically loading all the instances at once when opening a Protools session(which was crashing Play,VE Pro and Protools!) Also protools auto session saves only last about a second! I always make sure the last thing I do is save the VE Pro viframes before closing a session! Dean.
  • W
    W

    Hmmm... I'll have to look at the engine setting again... I know it was on low at one point, but not sure if I changed it.  Thanks for the heads up.

    Yeah, DeCoupling is the ticket for autosaving in ProTools.  I have not experienced any crashes loading Play and Kontakt 4, but I'm running VePro 32 and 64bit servers on PC, with VePro plugins back into ProTools rig on my G5.  It's working very well for the most part.  Still some slight glitches here and there, but I keep tweaking around on various settings, trying to keep my OSX CPU usage as low as possible.  Definitely running the buffer at 1024 when mixing helps a lot.

    Anyway, it's good to hear that those Play tweaks helped on the noise burst - that's really not cool.... 

    Best,

    Greg