My System :

Mac Pro 2,8 8core , 16 Gb Ram , OSX 10.5.8 , RME Fireface 400

I have loaded 5 Kontakt 3.5 Instances into the VSL Pro using LASS. 1 VI for using a Flute Patch. 

Each of the K3 Instances has 1 Insert FX which is a Waves Q 1.and i use 2 Busses with Altiverb.

For Midi stuff i use IAC Busses and trigger them using Logic 8/ Logic 9. Logic itself has no Plugins loaded.( 0% CPU ) 

VE Pro has a Buffer size of 265 and uses all 8 Cores.

CPU Performance on the VE Pro site is between 24 and 30 %.

After some time the Dropouts occour. If you try to close the VE Pro after 20 min of Working , the whole System gets sluggish and it takes some time that VE Pro get closed.

best regards,

D

any news ?

D

I was hoping to see a solution for this.

To verify it i´ve started a thread in the Audiobro forum. The behaviour is replicatable. Have a look to see if this Information can help you to further investigate:

http://www.audiobro.com/forums/viewtopic.php?f=9&t=546&p=3467#p3467

I forgot to mention that i own the VSL Special Edition as well and it happens with that one too.

Best Regards,

D

Hi D. Is this new behavior since 4.0.5436?

I did not had the previous version so i can´t really tell. If there is any way i can help , let me know !

cheers,

D

I previously tested it with the VST3 Plugin version on Cubase 5 and it´s happening here as well.

1 Vienna ensemble Instance , running 4 K3 Plugins, 4 Waves Q1/Q2 and 2 Altiverbs. The VE Pro GUI freezes for some seconds, no Midi , no Sound. After that everything is going back to normal. I experienced also Notehangs. 

cheers,

D

I would suggest that you test it with no waves and no Altiverb and see if it still happens. In fact I would go right back to the start and load the least possible, start adding more and then see when the problem occurs. Also try disabling any Wireless network and see if that makes a difference.

DG

I removed the Waves and the Altiverb but it is still the same. Dropouts occur. So , it must be something different. I also did a Test were i loaded all K3 Instances into Logic to check if it´s a Kontakt bug but everything is working fine here !

There is an another thing happening here:

When i close the Server/VE Pro my System gets sluggish until the Instance or Server is getting closed. Can anybody confirm ?

What kind of HD do you have ? 

I have a Samsung Spinpoint T166 SATA. ( 7200 rpm , 16Mb cache )

I also see that if i have a VE Pro AU Plugin Instance and i open a Send Bus on this channel, the VSL E PRO Interface says " Project saved " and it takes some time in Logic before the Bus Knob becomes available.

D

I am getting a lot of note hangs too. And some notes simply don't play. If I moved them around a bit, they may play. The GUI doesn't hang though. And it's only with Kontakt (I only have version 3.5), Vienna Instruments are fine. No effects are inserted in VE Pro. Wireless is disabled on all computers. When I ran VE Pro standalone I didn't have this problem. It doesn't matter how busy the arrangement is. CPU is rarely above 10%.

DAW: Logic 9.1.1, OS 10.5.8, VE Pro 5436

Server: Kontakt 3.5, Windows 7 64bit  (also tried XP64),  VE Pro 5436

Has anybody with this problem tried Kontakt 4?

I am also getting this behaviour. Fairly certain that the behaviour is fromhaving BOTH Vienna Instruments AND Kontakt running at same time within the VE PRo server.  If only Kontakt instances are running there are NO dropouts. As soon as a VIenna Instrument is added to the mix dropouts start occurring.

Mac Pro, 16 gig RAM. 10.6.3..latest and greatest VE Pro stuff, Kontakt 3.5

SvK

@svonkampen said:

Fairly certain that the behaviour is fromhaving BOTH Vienna Instruments AND Kontakt running at same time within the VE PRo server.

Not here. I tried it on a computer that has no Vienna Instruments installed at all and I get the same behaviour. 

Tried going back to VEPro 4.0.4686.....Of course this doesn't work as one can not open projects / metaframes that were saved with the newer 4.0.5436.

friggin' nightmare

SvK

Praying for a next VE Pro version fix here too...

DITO !! :-(

There is a compromise that worx.....IF you are not running huge amounts of Kontakt samples (I'm running circa 1 gig of RAM within Kontakt)......Goto Kontakt / preferences / memory and UNCHECK "Use Memory Server".......now you wont have that conflict between the Kontakt Memory server and the Vienna one.....

best,

SvK

Interesting, so it looks like on Mac it has something to do with Vienna. However, on PC, there is no memory server anyway, and the problem is still there, even without any Vienna Instruments. 

@svonkampen said:

There is a compromise that worx.....IF you are not running huge amounts of Kontakt samples (I'm running circa 1 gig of RAM within Kontakt)......Goto Kontakt / preferences / memory and UNCHECK "Use Memory Server".......now you wont have that conflict between the Kontakt Memory server and the Vienna one.....

best,

SvK

Sorry, never heard about that. It doesn´t make any sense because it works with Kontakt only perfectly, even with Bidule !

I can't seem to reproduce this here. From what host are you guys connecting to the VE Pro Server? And more specifically, which plugin format (AU/VST/VST3/RTAS)?

Thanks for looking into it, Karel. 

DAW: Logic 9.1.1, OS 10.5.8, VE Pro 5436 (AU)

Server: Kontakt 3.5 (VST), Windows 7 64bit  (also tried XP64),  VE Pro 5436

It doesn't always happen. But when it does happen, it happens on the same section repeatedly, about 80% of the time. Often moving a note away from the barline helps. The worst is when all notes are quantised to 1/4 notes.  It seems to happen most often when there is a section with 4 intertwining legato string parts. I am using a private Kontakt strings library. I also tried removing all controller data from the tracks, but that doesn't help either. I am not getting the GUI hang, just note hangs, or non-playing notes. As mentioned the same patches work fine when VE Pro is in standalone mode.  

I am ruling out the sleep mode explanation, as over a section some of the notes play, some don't, some hang, all over the course of a few seconds. 

Karel

Host = VE Pro

Kontakt 3.5 AU

OSX 10.6.3

it will take hours for the behavior to start occurring. Once it does, it will happen every 30 seconds or so  and get consistently worse and more frequent.

SvK