Summary: On Windows 7 x64 the batch converter stops working after about an hour, using 100% of the CPU but not converting and new files.
I just purchased a very fast multicore Windows 7 x64 Intel based machine. I've used the batch processor for years (purchased v12 and v13).
When I run either Version 13 or the newest trial on your site, the batch runs for about an hour and then slowly each coreconverter stops reading new files but continues to use CPU (and writes temp files). Finally the computer is running at 100% but no new files are being read or converted! It's as if each coreconverter process is working on the same files over and over and writing temp files but not writing finished files. And no new files from the target batched directory are being read.
When I try to cancel the batch, it asks if I really want to do that. But when I say yes, it starts up again at 100% CPU! I have kill each process!
I'm decoding .ape files, checking them for HDCD status with DSP and then encoding them back to .ape.
I have run this 5 times with different tests (turning virtual memory off, running my memory at lower than specified bandwidth etc.). Nothing makes any difference. I see the same behavior with V13 and V14(latest).
Is anyone else having this problem? I upgraded my machine because DBPowerAmp is one of the apps that traditionally has been able to utilize extra resources. Now I can't run it for more than about an hour...
I just purchased a very fast multicore Windows 7 x64 Intel based machine. I've used the batch processor for years (purchased v12 and v13).
When I run either Version 13 or the newest trial on your site, the batch runs for about an hour and then slowly each coreconverter stops reading new files but continues to use CPU (and writes temp files). Finally the computer is running at 100% but no new files are being read or converted! It's as if each coreconverter process is working on the same files over and over and writing temp files but not writing finished files. And no new files from the target batched directory are being read.
When I try to cancel the batch, it asks if I really want to do that. But when I say yes, it starts up again at 100% CPU! I have kill each process!
I'm decoding .ape files, checking them for HDCD status with DSP and then encoding them back to .ape.
I have run this 5 times with different tests (turning virtual memory off, running my memory at lower than specified bandwidth etc.). Nothing makes any difference. I see the same behavior with V13 and V14(latest).
Is anyone else having this problem? I upgraded my machine because DBPowerAmp is one of the apps that traditionally has been able to utilize extra resources. Now I can't run it for more than about an hour...
Comment