Yeah I was getting *really* white knuckled over this - as this was supposed to solve problems.
<P>
I was under the gun and had to get 4 cues delivered - each requiring multi-passes for stems.. 7 each.. and it just kept dropping out. Never in the same spot. The cue would be 2 minutes in and.. hiccup. 2 minutes wasted... multiplied by 20+ times in agonizing attempts to get these files sent out.
<P>
In the end, I had to put my plogue bidule computer back into the scenario, match the routing and bussing work I spent many hours configuring, disabling VSL in these Logic sessions and then matching the verbs/EQ etc etc..... Blarg.. anyway, in the end - everything worked properly - the first time using my B computer recording in 24ch. of audio in one pass. Cues delivered.
<P>
I wasted at least 5 hours trying to get around these glitches during a really stressful writing deadline. Not happy.
<P>
As fantastic as VEPro is, I don't think it's ready as a replacement for secondary systems with audio hardware. Because if I can't create master files without having to really sit there to be sure nothing goofed up... there's no point. The dedicated computers I have with their own hardware don't mess up - ever. It's as invisible a process as having a rack mount sound module being triggered.
<P>
I just wished I had stuck with the demo and not dropped the cash on it so quickly. Here's hoping for fixes sooner than later! :)
It's definitely VEPro doing the dropout because if I'm working on them side-by-side... everything in VEPro freezes (including the meters etc). Logic hums along