Quote:
Originally Posted by k0nr4d
Yep something like that would work. You could go a little further then a boolean result though.
You could spit back:
result: (int)percentage_match
and then let the script end decide "if its more then x% match, flag as possible copyright", "if its more then y% match, delete immediately"
|
that's not really necessary - without going into the ins and outs of how the matching works, the matching algorithm will only match positives, and discard negatives or "similars". For example, if I created a video compilation of 3 different video clips, one after the other and one of those clips was from a video in the fingerprint db, the video compilation would get flagged, because it contained content
within that was in the fingerprint db. It is possible for the return to tell you were in the query video (start time/end time) the match occurred, but that's a little more complicated and advanced and would slow down the return response.
How does the algorithm know it's a positive match and not something similar? Well, one ball busting method is once a match is found, the weeds are filtered out from the flowers by testing the match in reverse. Only identical videos will match in both forward and reverse (ie video playing in reverse) - the "similars" will fail the reverse test.