Vienna Symphonic Library Forum
Forum Statistics

180,807 users have contributed to 42,141 threads and 254,364 posts.

In the past 24 hours, we have 1 new thread(s), 7 new post(s) and 72 new user(s).

  • Napping VePro instances cause midi trigger delay

    I'm at a client and I'm running into it interesting issue. When we connect to Kontact running in VE Pro on a slave Mavericks Mac we end up having a .5 delay the first time we press the key for any instrument in that VEPro instance. 
    When we connect to an instance running on a slave PC or an instance on the slave Mac that is not running Kontakt the sound is triggered immediately.  Also if we connect to an VEPro running on the same machine as the daw (a local VEPro server) the sound from the kontakt instruments is instant.  

    I also notice that until I play the first note for a given VEPro instance on the slave Mavericks Mac the CPU meter is at 0, even though the instance is connected.  Playing a note in the Kontakt keyboard does not trigger any sounds either.  Once I send a note or any cc data, the CPU meter in the VEPro instance starts measuring CPU, like it finally turned on.  This is not the case on the local VEPro or the VEPro on the PC, the CPU meter starts measuring as soon as I connect. 

    This is affecting playback as the initial midi notes are out of synch (delayed) if we start the playback on the downbeat.  A one measure lead in allows enough time for things to trigger in synch. 

    We are running Logic 10.0.7 on Mavericks on a 12 Core Mac Pro 20 Mid 2010  and VEPro is running on  Mac Pro 2013 (trash can).  Both are running Mavericks.
    Kontakt is up to date with ver 5.3.1 and VEPro is 5.3.13240.
    AppNap for VePro is turned off for VePro.