Audio mode an byte by byte are activated. Why does DC calculates hashes?

[Dupp]

Audio mode an byte by byte are activated. Why does DC calculates hashes (when byte by byte is activated)?

And why is it so incredibly slow? 30 min. for 326 GB not yet finished.Is it like it should be?

[therube]

Audio mode an byte by byte are activated

Can't be, AFAIK.
Byte-to-Byte is only available in a Regular mode search.


Though, Audio mode, Match exact audio data, is available.

In that mode, AFAIK, DC runs a hash algorithm on the audio data to find exact duplicates of the audio data.

As a hash algorithm is being used, the hashes have to be computed.
(They may also be saved, base on the setting in, Settings | General | Use caching for calculated hashes.)


There are different hash methods (available via ffmpeg) that can be used, & not that I particularly understand them "enough", but on my end, for my purposes, I use (in a batch file that I came up with) a stream copy method (rather then streamhash or framehash) because it's quicker & is sufficient - for me.

[DigitalVolcano]

Yes, the hash setting is for Regular mode hashing only.

Audio mode hashing uses SHA-1 hashing which is fine and just as accurate as byte-to-byte.

[Dupp]

Many thanks!

Still running after about 5, 6 hours or longer.

Very sorry for my bad understanding. What does that mean to the issue? What do I have to do now?

[Dupp]

Sorry for asking again, what setting(s) do I have to change to make DC work here? To complete searching for dups?

[DigitalVolcano]

Is it stuck on the same file? It may be an issue with the file, and if so it may be worth trying to scan a subset of the folders to isolate it.

Are you doing an Exact or Similar audio mode scan?