Its 5:25 and after a day of working with this project, the dropouts are lasting about 3 seconds. As an additional problem, I believe that some cc information is not getting through. I am getting many stuck notes and have had to put multiple cc points on each line to make sure that the cc info is picked up.
-
seems like a bunch of you guys were able to figure this out for yourselves. me on the other hand...
this thread has been going since the beginning of october, it is now mid-december, and i have to admit that i'm getting very, very frustrated with this issue. i do suspect that in my particular case this might very well be a networking issue. cubase runs flawlessly, and when i look at the vePro meters, i don't actually "see" the drop outs, so i'm assuming vePro is sending the audio data back to the master, but for the life of me, i can not figure out where exactly the problem lies.
at this point i am using cubase 5 on my master pc (as was suggested to me in an earlier post), and i have three instances of vePro on my slave pc (see detailed specs in initial post of this thread), and i am not able to do a proper mixdown of a 2 minute wav file, since there is always some sort of click, pop, audio drop out, or stuck midi note(s) during export. always in a different spot, always completely arbitrary, and i'm at the end of my wits. if anybody from the VSL crew would like to take this head on, feel free to do so. contact me for any additional details you might need. i'll be glad for any and all help. i can't be sitting here for 3 hours, trying to get a "lucky" mixdown of a 2 minute audio file - i NEED to get this figured out.
thanx,
t
-
Were you able to figure this out? I too am experiencing the same issue using Logic 9 and VE PRO.
-
Yes - I am having all this trouble NOW with 4686. Never had stuck notes on previous builds. Come on VSL - if you are claiming to be the best - sort this problem out for us all. And while you are about it why not make some effort to put the Imperial IN TUNE and add half pedalling, without which it can never be a serious instrument in spite of what it costs us.
Robert John Godfrey
===============================================================================================
Cubase 5.10
Windows XP on DAW - 7 on slaves
-
FYI build 4780 does NOT fix this problem for me.
To complicate matters for my troubleshooting, I switched to 10.6.2 after Christmas. (I thought that I could use 64 bit VE Pro server in Snow Leopard but only 64 bit plugs appear in the menu!?@#?)
But I get the same dropouts...maybe more and eventually a crash.
I wish this could get solved. VE Pro seemed like such an elegant solution. Nothing elegant about it yet. Well, I take that back. When Kontakt is not in the mix, VE Pro seems to work OK.
Of course, the reason I bought it was so that I could load a bunch of Kontakts and keep them loaded as I switched projects.
-
Talk about strange behavior!!!
I accidently left my computer on last night with the same project that I had the above problems with.
I've written this email to tech support and this is very important to my strange results.
I have 6 instances of VE Pro in a VE Pro Server meta template. Without loading or unloading anything (after the initial load sequence) VE Pro Server is using 926.2 M of RAM.This is with 5 instances using Kontakt 4 and one instance with a totally empty instance of Omnisphere in it.The Kontakt Memory Server only has 452.8M in it.Why would the VE Pro server use more RAM than the Kontakt Memory Server with all of the samples sitting in the Kontakt Memory server and not in VE Pro????Is VE Pro loading all of these samples into it as well? Could this be causing the extreme delays that lead to audio dropouts?I hope you understand my question and why it seems very important to me. Here's a recap.I have only Kontakt 4 (except for an empty OMnisphere (which might take 300M even unloaded). Why is the VE Pro memory use so high when there are no samples in it?But, after I left the computer on all night... it worked perfectly the next morning. No audio drop outs, no memory warnings in Logic. EVerything was perfect.Except VE Pro had crashed during the night. whenever I put the cursor over VE Pro on my desktop the beachball would appear. (this signifies that the app that is under the cursor has crashed) Logic was fine. But the Kontakt Memory Server no longer appeared in my top bar. It had crashed too??So, I worked all day with VE Pro crashed and Kontakt Memory Server missing from action AND it all worked perfectly.Now if I can just figure out how to crash VE Pro every morning after I boot it all up!Note that in the Activity Monitor, VE Pro Server is not responding (which is how it appeared on the desktop) and the Kx Memory Server has the 471 M or so that it should have but its icon was not apparent on the top of my screen. The spinning becahball cursor did not show up in the screen shot. When it hovered over VE Pro it was a beach ball. When it hovered over Logic it appeared normal . Logic worked great.Since the samples for Kontakt are loading twice, both in Kontakt Memory server and in VE Pro, I assume that VE Pro and Kontakt's memory server are not playing together. I'll try Kontakt without the memory server and hope that will fix the problem.Althoug, I hope there will be a solution because I don't want to have to switch the Kontakt Memory server on and off with each project.
-
From your report, it sounds like Kontakt Memory server crashes and causes the Kontakt instance to get stuck trying to communicate with the (non-existing) memory server. VE Pro in its turn waits for Kontakt to finish its call, but since it never finishes - it gets hung.
If you have any useful crash / hang reports I'd be happy to read them.
-
I have since been able to reduce these problems to an acceptable level by experimenting with the threading settings on the slaves. There seems to be no obvious logic as to how to set this parameter. However it seems that you can change this parameter "on the fly". In otherwords - no need to unload/reload.
Robert John Godfrey
===============================================================================================
Cubase 5.10
Windows XP on DAW - 7 on slaves (dual and quad core respectivley)