I ran dump3 against 100 mp3-files wherein I copied a certain file to test.mp3. Flabbergasting, dump3 doesn't show me anything. The 'Ergebnisse' (result page) remains empty but in the MYsql-table 'filename' I can see that test.mp3 has an identical entry in the field 'statusid' - just like the original mp3.file has. How comes that I can't see a result?
btw: I tried checksum-fingerprint with 80% threshold and finding fingerprints of doublettes with 100% threshold...
Cheers - Steff
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do not look at the statusid except if it is not 0. If statusid is not 0 then there is a problem with reading the file and you will most likely get the result you got. (does not find the duplicate) The status table defines all the error codes. You should also see an error logged in dump3.log.
If the statusid is 0 then you can check the fingerprint of the files by using the sql statement:
select * from filename,fingerprint,fingerprinttype
where filename.filenameid = fingerprint.filenameid
and fingerprint.fingerprinttypeid = fingerprinttype.fingerprinttypeid
and (filename.filename like 'path/to/file1-%'
or filename.filename like 'path/to/file2-%');
The 'like' and '%' sign are needed because the size and modified date are appended to filename.
The result should give you 2 fingerprints per file and the prints for file1 should match those for file2.
If they do match and dump3 is still not returning a duplicate, then there is definitely a bug that needs fixing.
Alex
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I ran dump3 against 100 mp3-files wherein I copied a certain file to test.mp3. Flabbergasting, dump3 doesn't show me anything. The 'Ergebnisse' (result page) remains empty but in the MYsql-table 'filename' I can see that test.mp3 has an identical entry in the field 'statusid' - just like the original mp3.file has. How comes that I can't see a result?
btw: I tried checksum-fingerprint with 80% threshold and finding fingerprints of doublettes with 100% threshold...
Cheers - Steff
Hi Steff
Do not look at the statusid except if it is not 0. If statusid is not 0 then there is a problem with reading the file and you will most likely get the result you got. (does not find the duplicate) The status table defines all the error codes. You should also see an error logged in dump3.log.
If the statusid is 0 then you can check the fingerprint of the files by using the sql statement:
select * from filename,fingerprint,fingerprinttype
where filename.filenameid = fingerprint.filenameid
and fingerprint.fingerprinttypeid = fingerprinttype.fingerprinttypeid
and (filename.filename like 'path/to/file1-%'
or filename.filename like 'path/to/file2-%');
The 'like' and '%' sign are needed because the size and modified date are appended to filename.
The result should give you 2 fingerprints per file and the prints for file1 should match those for file2.
If they do match and dump3 is still not returning a duplicate, then there is definitely a bug that needs fixing.
Alex