When working on a cue and stopping logic mid way through the piece, ve pro's audio processing seems to stick fast. What I mean is when I next hit play I hear the tail out of the part of the cue where I had previously stopped, so VE Pro is halting, keeping the last stopped moment in memory somehow and then continuing when play is next hit, which means you hear the reverb tail out of the place you last stopped the sequencer. The problem with this is that when it's also trying to process what's coming up it gives itself (and me) a headache and has to 'think' (beachball) for a few seconds before it plays. When you're having to start and stop every few seconds sometimes, this can be mightily frustrating. Conversely, in plogue bidule for example, when you hit stop, the audio tail out (usually the reverb tail) continues. This means when play is next hit, plogue hasn't got to process the audio info for the previous tail out and is free to process only what it is currently playing (no beachball - everyone's happy). Is there something I'm doing wrong that I can easily put right (settings etc) or is this a curious idiosyncrasy of ve pro's programming. If so can it be fixed in a future update as beachballs should be encountered only on beaches, possibly swimming pools. Many thanks for any help or advice. Mac 2.26 8-core; 16GB RAM; All latest softwares
Forum Statistics
200,430 users have contributed to 43,198 threads and 259,083 posts.
In the past 24 hours, we have 3 new thread(s), 10 new post(s) and 80 new user(s).