On Sun, 09 Oct 2005 11:50:18 +0200, Klaus Schmidinger wrote: > If you're using the current developer version, simply put a call to > > SetPriority(19); > > at the beginning of cCuttingThread::Action(). > Let me know if this helps, the I'll add it to the official code. This is pretty useless on my system because the loss of responsiveness is mostly caused by the disk accesses and not by cpu usage. I have added a usleep() into the copy loop which is executed every 3th loop. This reduces the cutting bandwidth to about 5 MB/s on my system. Something that limits the disk bandwidth used by cutting combined with a cutting queue would be ideal. Emil
