Tweet
I apologize if this has been previously addressed, or if I am overlooking something simple.
On Version 15, if a track ripped insecurely and dbPowerAmp indicated "Error", the file was still written to my hard drive. On Version 16, if this happens, the file is not written. If I am ripping a hard-to-find CD, and I get an error, I would still want the file; perhaps it might still play.
Is there a setting I can use on Version 16 that will allow the file to be written to my hard drive in spite of the error?
Thank you!
On Version 15, if a track ripped insecurely and dbPowerAmp indicated "Error", the file was still written to my hard drive. On Version 16, if this happens, the file is not written. If I am ripping a hard-to-find CD, and I get an error, I would still want the file; perhaps it might still play.
Is there a setting I can use on Version 16 that will allow the file to be written to my hard drive in spite of the error?
Thank you!
Comment