I discovered a few files with sizes < 100k, and where the log shows "Secure". Evidently, it has lost connection to the spinner, and happily gotten zero-bit files (AccurateRip CRC: 0). I am using the Sony XL1B2, and yes it is sometimes buggy.
But it should be possible to avoid things like this? (And: is it desirable to have zero tracks in AccurateRip when there is this danger of false entries?)
One idea might be to flag silent tracks. Or in the very least, log a warning message when AccurateRip CRC of zero shows up and there is a nonzero CRC for the same track in the AR database.
(Now, search time. Small FLAC files and log files with zeroes ... 1500 CDs ripped and I hoped it was once-and-for-all ...)
But it should be possible to avoid things like this? (And: is it desirable to have zero tracks in AccurateRip when there is this danger of false entries?)
One idea might be to flag silent tracks. Or in the very least, log a warning message when AccurateRip CRC of zero shows up and there is a nonzero CRC for the same track in the AR database.
(Now, search time. Small FLAC files and log files with zeroes ... 1500 CDs ripped and I hoped it was once-and-for-all ...)
Comment