Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent results ("Too short" messages) #6

Open
ShareBugreports opened this issue Nov 1, 2023 · 0 comments
Open

Inconsistent results ("Too short" messages) #6

ShareBugreports opened this issue Nov 1, 2023 · 0 comments

Comments

@ShareBugreports
Copy link

ShareBugreports commented Nov 1, 2023

So, i noticed some invalid "too short" messages. I have a directory with a lot of non-movie stuff.
Including source/compiled files of vid_dup_finder.

I did a scan a couple of times, inceasing the logfile number each time, like:

rm /home/test/.cache/vid_dup_finder/vid_dup_finder_cache.bin
./target/release/vid_dup_finder --files ~/TEMP/fingerprint/ 2>&1 |tee -a log5

Now we check the output messages (redacted the output. I used the same replacements for each file)
number=5; cat log${number} |grep short |sed 's|.*Too short : ||' |sort > log${number}_parsed.log

For example check "log5_compared_to_6_and_7.png".
In run 5 we got a "too short" message for "[rarbg]/.mp4". This did not happen in run 6.
I got a "inserting" in run 6 for this same file.

The same for "log8_compared_to_9_and_10.png"
"cache2/.mp4" failed in run 8. But was inserted in run "9".

As every run the order of the scanned files is different i think some variable is the loop. Or ffmpeg gets confused about all the non-movie files.
log5_compared_to_6_and_7
log8_compared_to_9_and_10
log5_parsed.log
log6_parsed.log
log7_parsed.log
log8_parsed.log
log9_parsed.log
log10_parsed.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant