Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
VE PRO 1 second freeze every couple seconds
Last post Sat, May 02 2015 by samphony, 9 replies.
Options
Go to last post
Posted on Thu, Apr 23 2015 11:01
by samphony
Joined on Mon, Apr 10 2006, Posts 68

Hi chaps.

I am running a Mac Pro 6,1 2013 with:
3,5ghz 6core, 64GB Ram, Blackmagic MultiDock 2
Mac OS 10.10.2
Latest eLicencer 6.8.5.1166
Latest Kontakt 5.4.3
Latest VE PRO 5.4.13715

When working with Logic Pro X I have:
18-22 instances per Kontakt 5 instrument in a Metaframe so Logic has a single track relation to VEP/Kontakt5

VEP Instance is configured to
1 Midi port
2 Threads per instance
2 Audio ports

Now if I open my template and start playing on lets any instrument track that relates to an instance
and hold a sustain note after a couple of seconds the note will be interrupted (like an audio dropout) for 1-2 seconds and then continues the audio.

I tried to turn onoff/ "prevent App nap" but that doesn't resolve the issue. If i switch to VE PRO and open the about screen I can visually see this interruption. The about scroll text get stuck for 1-2 seconds and continues and then get stuck and so on.
I have tried installing and reinstalling VEP/Kontakt/ elicenser 
I have even clean installed a complete new yosemite system but the issues remain.

 

Any ideas?

Posted on Fri, Apr 24 2015 03:55
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1518

oh NM I didn't notice you were indicating only the one computer.

MacBook Pro 2.6GHz 6-core i9
32GB 2400MHz DDR4
OSX 10.14.5
Posted on Fri, Apr 24 2015 03:58
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1518

How many instances? 2 threads per; you have 12 to work with.

MacBook Pro 2.6GHz 6-core i9
32GB 2400MHz DDR4
OSX 10.14.5
Posted on Tue, Apr 28 2015 12:48
by samphony
Joined on Mon, Apr 10 2006, Posts 68
Originally Posted by: civilization 3 Go to Quoted Post
How many instances? 2 threads per; you have 12 to work with.




Just a couple of days ago I'm setting up new templates with either one instance with everything loaded or 3 instances for sections.
If I host VEP in Bidule the 1 second freeze is non existent. It happens only if I connect VEP directly to Logic or Studio One.

If I use 1 instance for all I've setup multi threading to 10 per instance if I use 3 instances I use 2 per instance (testing new setups aiming at ultra fast loading times when switching projects)
Posted on Tue, Apr 28 2015 16:47
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1518

I used to think I needed to leave one or two cores for [Cubase]. Someone once told me it wasn't necessary to allow for it; and you know what, I believe they were right.

I was experiencing terrible performance the other day, and it turns out I had forgotten that I had set instance "3" to one core, from a project where very little was going on in it. And subsequently this instance in metaframes had been special in this regard. But now it was actually as heavy as any demand on my resources.

Are all your instances equal? In any case you have 12 logical cores so all things equal you can give three instance 4 each.

For me, distributing cores is very important.

 

You can distribute particularly to an instance, rather than the global. I have instances which are unequal as I pointed out. Project Settings, under edit menu.

Another thing is, are these troublesome instances coupled to the host?

MacBook Pro 2.6GHz 6-core i9
32GB 2400MHz DDR4
OSX 10.14.5
Posted on Tue, Apr 28 2015 17:40
by samphony
Joined on Mon, Apr 10 2006, Posts 68
Thanks for your reply.

In my new test run I send midi from either logic or studio one via bidule midi to plogue bidule.
Inside bidule reside one or three VEP server VST3 plugins. Audio goes back to LPX or Studio One via rewire.

This new approach allows me to switch instantly between projects and still have my main palette loaded.

As I pointed out the freeze issue only happens if I host the server plugin inside the DAW and connect directly to VEP.
Posted on Tue, Apr 28 2015 20:56
by civilization 3
Joined on Sat, May 16 2009, SF Bay Area, Posts 1518

Working decoupled allows for the same thing, close the DAW project leaving the metaframe alone.

For instance, saving the DAW project while coupled could be an interruption. It takes quite a bit more time; in addition to disconnecting and in general more tedium.

MacBook Pro 2.6GHz 6-core i9
32GB 2400MHz DDR4
OSX 10.14.5
Posted on Wed, Apr 29 2015 06:34
by samphony
Joined on Mon, Apr 10 2006, Posts 68
Originally Posted by: civilization 3 Go to Quoted Post
<p>Working decoupled allows for the same thing, close the DAW project leaving the metaframe alone.</p>
<p>For instance, saving the DAW project while coupled could be an interruption. It takes quite a bit more time; in addition to disconnecting and in general more tedium.</p>


I run VEP always decoupled! Since years ;)
Posted on Sat, May 02 2015 00:01
by samphony
Joined on Mon, Apr 10 2006, Posts 68

Have a look. As you can see the about screen freezes (without playing back anything) the same happens to audio when playing just one patch in kontakt via VEP

Freeze Gif animation

You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.