I've noticed that in PerfectTunes, it's giving off a bogus ripping error for one track, which is track 3.
The reason it's flagging this file in particular is because it has the same time duration as the second file in playback, and exactly the same file size.
I feel like this shouldn't be flagged as a ripping error, as it is a false claim to make and is not a genuine ripping error. The tracks are perfectly fine, yet it flags the time duration as being the same between two files as somehow wrong, even though it's correct in the rip and how it's supposed to be. Tracks can have the same track duration and size.
Another one of my cds was falsely reported as inaccurate as well for this very reason because of two tracks having the same time duration and file size.
When ripping in EAC, I get an AccurateRip score of 19, so there's no way the tracks have any errors. 19 is a pretty high accuracy and is no joking score.
The CTDB Values are also in their full values, so there's no way there can physically be any errors in the rips. The tracks play just fine.
The reason it's flagging this file in particular is because it has the same time duration as the second file in playback, and exactly the same file size.
I feel like this shouldn't be flagged as a ripping error, as it is a false claim to make and is not a genuine ripping error. The tracks are perfectly fine, yet it flags the time duration as being the same between two files as somehow wrong, even though it's correct in the rip and how it's supposed to be. Tracks can have the same track duration and size.
Another one of my cds was falsely reported as inaccurate as well for this very reason because of two tracks having the same time duration and file size.
When ripping in EAC, I get an AccurateRip score of 19, so there's no way the tracks have any errors. 19 is a pretty high accuracy and is no joking score.
The CTDB Values are also in their full values, so there's no way there can physically be any errors in the rips. The tracks play just fine.
Comment