Can someone please explain why PerfectTunes AccurateRip analysis depends on rip metadata?
Example (latest): I rip one CD with dBpoweramp, which says the disc is in AccurateRip, with the default metadata writing enabled. All tracks are ripped accurately except one, which is declared Secure but disagrees with AR. I then run PerfecTunes on the rip, which confirms the rip has only one track with ripping errors. So far so good. But if I now strip the ripped files from their metadata (using Exiftool or Tag Stripper) - OR I disable metadata writing in DP - PT says the album IS NOT IN AR.
What gives? What are EXACTLY the reliability boundaries of PerfectTunes?? One can so easily fool it into opposite conclusions? Do I have to suppose one can just as easily take a flawed rip and modify its metadata to lead PT to certify its accuracy??
Edit: It is even worse than that. If I strip a perfectly accurate rip of its metadata, PT may say it cannot check because some tracks have different length than CD original. PT hallucinates.
Example (latest): I rip one CD with dBpoweramp, which says the disc is in AccurateRip, with the default metadata writing enabled. All tracks are ripped accurately except one, which is declared Secure but disagrees with AR. I then run PerfecTunes on the rip, which confirms the rip has only one track with ripping errors. So far so good. But if I now strip the ripped files from their metadata (using Exiftool or Tag Stripper) - OR I disable metadata writing in DP - PT says the album IS NOT IN AR.
What gives? What are EXACTLY the reliability boundaries of PerfectTunes?? One can so easily fool it into opposite conclusions? Do I have to suppose one can just as easily take a flawed rip and modify its metadata to lead PT to certify its accuracy??
Edit: It is even worse than that. If I strip a perfectly accurate rip of its metadata, PT may say it cannot check because some tracks have different length than CD original. PT hallucinates.
Comment