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: CUEtools CTDB and filesharers distorting results (Read 2269 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

CUEtools CTDB and filesharers distorting results

Apologies if this has been covered before - a quick search found nothing. Comments please on this scenario: User One accurately rips a CD and the results are uploaded to CTDB. User Two downloads a shared file of the same CD (which has been INACCURATELY ripped) from a torrent site. Both users use CUEtools to check the accuracy of their files. User Two finds that his download is confirmed as accurate because each person who has previously downloaded these files has used CUEtools and their results have subsequently been uploaded. User One is told that his accurate rip differs to the majority of results submitted. Am I missing something here? How does CUEtools deal with this skewing of data?
 

CUEtools CTDB and filesharers distorting results

Reply #1 –
How are these subsequent results being uploaded? CUETools doesn't submit results (after verifying) when a CTDB TOCID already exists. If a CTDB TOCID doesn't exist then CUETools will only submit when there are also 2 or more AccurateRip matches for all tracks. The 'submit' portion of CUETools will be removed in the future as it is no longer needed.

Why should User One care about the majority anyway? If their rip matches one or more others (as in not their own rip) in the CTDB then the rip matches. It is possible for different releases/issues/pressings of the same title to fall under the same CTDB TOCID so this majority/minority thing can happen without skewing the data.
korth