This is an extremely CPU and memory intensive process, so much so that if some background task starts up (such as an AVG update or a Windows update of any sort) it corrupts some of the audio tracks.
This reminds me a little bit of the Buzz thread, in that you're using software which is insane and broken, but not perhaps in the way you think.
Why does CPU contention cause corrupt output? If I run twenty instances of the C++ compiler in parallel then my PC slows to a crawl, but it doesn't compromise the correctness of the output. Is Tunebite really using a playback engine that detects loss of realtime and skips ahead?
Peter
Previous Topic
Index
