Scanning does stuck the software at the same file number in hashing

[Danny_T]

Hi,

I want to see what it is currently processing as file name. Because the software seems stuck at the same rehash item even if I restart it to scan. I need to know what file is making DCP to hang. Cancel is not working, I waited for days, Only exit is, taskmanager, killing DCP.

Regards,

[therube]

I don't know that there is a way to see that in DC?
Doesn't appear that the .log file would record that.

You might be able to... hmm.

I was going to say Process Explorer should probably see the file name (but figuring out how to set up & what to look for with that utility, that's a different story [& I'm not sure, particularly, offhand].)

Now, aside from DC's .log file, it also stores data in %appdata% in a sqlite files (.data).
And maybe, that might hold a clue as to what file it's getting caught on, not sure?
(And again, not sure offhand how to extract that data, & also whether it would come out in the order it went in, thereby potentially pointing out the file in question.)

[DigitalVolcano]

There's isn't a way to see this in version 5 (it's a feature in the upcoming v6 though). The only thing I can suggest to to limit the scan by either folder or excluding large file sizes (eg audio files > 100MB) to see if this helps by process of elimination.

[Danny_T]

It are a few big folders, so thats not a easy task. The files are not big, a few MP3, and the most are WAV and FLAC upto about 40Mb.

Can you suggest a time frame for the V6? I can wait and process other parts of the hugh music library if its not too long. I am happy that I found the right tool and bought it last month, it saves me a lot of time now instead manualy doing things for many years now. Keep up the good work at it.