Tweet
The thread http://forum.dbpoweramp.com/showthread.php?p=96858 leads me to two "wishlist" items for next AccurateRip revision and R14:
1) With dMC R14: a retro-verifier based on dBpoweramp's tagging.
I.e. if the files say inaccurate, then check against AccurateRip using the tag ID and not the files-based-calculated ID -- and report accuracy from verification across pressings.
(With as default accuracy reduced by one, assuming the existence of this tag is highly correlated with the user submitting.)
2) In AccurateRip:
- Provide for an "AccurateRipImageID" calculated by the ripping application, being what the ID would be if it were retroactively calculated from the files;
- Upon submission, let the application submit that AccurateRipDiscID x has AccurateRipImageID y (provided that y is distinct from x). Then map. Maybe even have a different URL suffix for retrocheckers.
1) With dMC R14: a retro-verifier based on dBpoweramp's tagging.
I.e. if the files say inaccurate, then check against AccurateRip using the tag ID and not the files-based-calculated ID -- and report accuracy from verification across pressings.
(With as default accuracy reduced by one, assuming the existence of this tag is highly correlated with the user submitting.)
2) In AccurateRip:
- Provide for an "AccurateRipImageID" calculated by the ripping application, being what the ID would be if it were retroactively calculated from the files;
- Upon submission, let the application submit that AccurateRipDiscID x has AccurateRipImageID y (provided that y is distinct from x). Then map. Maybe even have a different URL suffix for retrocheckers.