Initial scan stage detected all videos (by count) then during second stage, seemingly randomly stopped.

[CmdrNemo]

Sorry if this doesn't make much sense... I have over 65k videos, all in one folder with subfolders.

During first stage scan, it detected the correct number of videos. That stage took several hours.
During second stage scan, where screenshots are generated, it just stopped and count dropped down to about 1/3 of original count.

I tried to "rescan" but the progress icon on top-right would quickly fill then stop at 99%. I tried enabling "watch" but it didn't seem to do anything. Rebooted PC (Windows 11) and tried steps again, same issue.

After reading the user guide, in the "move hub" section, it says that the folder name shouldn't have a space. ("C:/movies" and not "C:/my movies") Does this also apply to initial set up because my base folder does have a space in the name of it. Any help?

[whyboris]

Sorry about my UI (user interface) getting a bit crappy: there is an Add missing thumbnails button but it's not obvious where. I suspect this is all you need - to trigger another attempt at adding missing screenshots.

Because I was expecting screenshot generation to work well for most users, I shoved the button far away:

Click on "settings" (gear, top right), click on 4th tab (current hub), and then on "edit folders" button and finally on "add missing thumbnails". That will be the button you want (clicking "rescan" just checks for new videos in the "source folder" and does not try to add missing thumbnails).

I'm thrilled VHA is handling 65,000 videos almost-well for you. A note about screenshots:

The second phase is tricky as the app tries to extract screenshots. First off, it's best if you're not running other apps during this process; depending on the extraction settings (how many screens per video and how large the screenshot resolution), it may take a while for each video. For 4K videos, sometimes it takes a long time to generate screenshots as your PC tries to render the video around the frame of video it is extracting.

Getting stuck can happen when a video is corrupt (partially downloaded or some other corruption), but there is a "timeout" which is set per-video when it starts generating screenshots; if the timeout (say 1 minute) occurs before the screenshots are extracted, VHA should skip that video. I suspect the timeout could be as long as several minutes if the resolution is high and the number of screenshots is high. Perhaps it's stuck processing those.

But of course I could have a bug somehow - and maybe the app crashes mid way. This could also happen if the app runs out of RAM during extraction and has to dump RAM onto the hard drive so as to free up more RAM to continue extracting screenshots. Thankfully - this should only happen per video so if it craps out on one video, it should continue on the others after the timeout.

Please let me know if you have any trouble.

[whyboris]

One more thought: if the videos are on a network drive, consider using "Attach network drive" rather than through its network location (e.g. "//server") - it seems network stuff behaves worse than a "local address" 🤔