Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Ripping with XLD to Lossless. (Read 3144 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Ripping with XLD to Lossless.

I know that "lossless is lossless" but I'm looking to rip my CD collection for archiving on a newly purchased external drive and want to make sure that there are no errors in the Rip.  Are the settings below good?  Should I add the "verify suspicious sectors" setting? 


 

Ripping with XLD to Lossless.

Reply #1
I check also "Test before copy (half as fast) and select "Only when track does not exist in AccurateRip DB."

Other than that you should be good as long as the read samples offset value is configured correctly. "Should I add the "verify suspicious sectors" setting?"  ...I would.
The Loudness War is over. Now it's a hopeless occupation.

Ripping with XLD to Lossless.

Reply #2
Sweet.  Thanks for the quick response.  I'll go with the settings you suggested. 

Ripping with XLD to Lossless.

Reply #3
Sweet.  Thanks for the quick response.  I'll go with the settings you suggested. 


As said many times on this board, to go faster (and maybe give less stress to the drive mechanics and beam): if the CD you're going to rip is in Accuraterip db (and you can know it before starting, looking at the flag lower left of the main window), you can use Burst mode. At the end of the process, look at the log window and if there are tracks whose AR test have failed, select and re-rip them only, enabling Secure mode and "Test before copy - Always".
One or more tracks might actually fail the test without being necessarily wrong ripped, if you happen to have a different press than the ones whose results are saved in the AR db. I think this is more likely to happen if the "confidence" value shown by the other matching tracks is low.
... I live by long distance.