200,409 users have contributed to 43,197 threads and 259,080 posts.
In the past 24 hours, we have 2 new thread(s), 9 new post(s) and 78 new user(s).
@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 !
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
BTW ...I switched to Kontakt 4.1 (public Beta 64bit) today , so now I only run a VE pro 64 bit server. Will report if problems continue.
SvK
FIXED!
The solution is Kontakt 4.1 in 32 bit server. Unfortunately Kontakt 4.1 still wont play nice in 64 bit server along side Vienna Instruments Instances.
SvK
@svonkampen said:
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
Exactly same behavior here! OSX 10.5.8 and 10.6.3. Local machine only. Remote machines work fine.
Dezzo: Does your VEP ever come to a halt with the CPU usage stuck at 95-99%, usually closer to the end of the day? Only a reboot fixes this at my end.
Dezzo: Does your VEP ever come to a halt with the CPU usage stuck at 95-99%, usually closer to the end of the day? Only a reboot fixes this at my end.
My CPU meter is hanging around 17 - 20% . The Dropouts occure randomly.
The Dropouts occure on VEP only but not in Bidule.
@Karel said:
What if you disable the Kontakt memory server?
Hi Karel ,
When i disable the Server, the dropouts dissapear....for some Reason.....
It runs smooth. I will test it again while the Setup is growing. For now, it´s fine.
Is it a Problem from the NI side ? It looks like that.......
D
@Karel said:
It could be a problem in Kontakt or both Kontakt and VE Pro. Disabling the memory server definitely seems to solve it. Kontakt 4.1 comes in a 64bit flavour, so there shouldn't be a pressing need to use the memory server there anyway.
Update: I just added the Wallander Instruments Pro Edition Brass + 1 Altiverb Instance. The Dropout phenomenon came back !No Crash so far.
Memory usage 20 - 25 % and the VSL Ensemble Pro shows me 108 % CPU , 96 Threads, Physical mem = 2.15 GB, Virt. mem = 3.47 GB
Hope that helps.
D
Important to mention: If you let VEP run for some hours and try to close it , the whole system gets sluggish. My 7th Core is peaking to the maximum and i have to force quit the Application which takes some time since the whole System is verry slow.
After the Force quit, everything goes back to normal.
Can anybody confirm this?
D