Printable View
Suddenly CD Ripper on a Windows 10 Professional PC stopped using multiple cores when ripping a CD.
After ripping a track the process proceeds to encode the track and does not proceed to rip the next track until the encoding is complete.
I am using version 16.2.0.3, last modified/installed 10/25/2017.
Has this been observed before?
Any known culprits that cause this?
Updated to 16.4 and removed/reinstalled anti virus suite.
Working again now
I'm running the fully registered version 16.6 on Windows 10 Pro with Intel Xeon W3540 (4 cores), but the ripping tool only uses one core.
I uninstalled the antivirus software and dBpoweramp, rebooted the pc, installed dBpoweramp 16.6, and ripped a CD, but still one core is used.
But when converting audio tracks, all four cores are being used.
What am I doing wrong?
CD ripper does not use more than one core normally, because the cd drive is 1000x slower than encoding.