Wild Willy
unread,Aug 9, 2022, 11:51:32 PM8/9/22Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Video Download Helper Google Group
There's an issue you should be aware of when trying to download multiple files
concurrently. Michel decided that the moov atom was something he could keep in program
storage. What's the moov atom? I don't totally know but it is my understanding that it
contains information like resolution, duration, frame rate, you know, minor unimportant
stuff like that. Stuff that, if it's not present in an MP4, then the MP4 won't play.
Like I say, minor stuff. In any case, VDH accumulates the moov atom in program storage &
does not write it into the target file until the download completes. But keeping the
moov atom in program storage means it is managed by the operating system's paging
algorithm. It has been my experience that if I have multiple downloads going & a few of
them complete at the same time, my page file goes crazy, my system locks up, & I can't do
anything until it sorts itself out. On my system (Windows 7 64-bit), it has always
sorted itself out after about 20 minutes, half an hour. Usually, one of the downloads
completes successfully, some others crash, some others fail because they've timed out, &
some others are zombies like what you're apparently observing. Sad but true, if you have
a bunch of downloads to do in VDH, you're better off single-threading them. Set the VDH
Setting for Max concurrent downloads to 1 & let everything else just hang out in the
queue. It's quite likely (you tell me if I'm wrong in your case) that the web site
you're downloading from throttles your bandwidth. Typically, the site will let you have
anywhere from 2 to 9 million bytes per second of bandwidth usage, but if you are doing 10
downloads, each one gets its fraction of the total allotment. So there's really no edge
in doing them concurrently. The time it will take to do 10 downloads one at a time adds
up to the same as it would take if you're trying to cram all 10 through at the same time.
So there's usually no benefit to trying to do multiple concurrent downloads. This
situation has nothing at all to do with the resolution of the files you're trying to
download, nor does it have anything to do with the free space on your hard drives.
Your observation about part files is correct. But part files exist only for MP4
downloads. In my experience, there is no part file for WEBM or MKV target files. If the
download of an MP4 does fail, the part file is useless. The moov atom got lost so the
MP4.part file is just wasted space on your hard drive. It is my understanding that this
issue with moov atoms is not applicable to MKV. A download of an MKV can fail & what you
would have could be playable, although incomplete. But the intermediate partially
downloaded MKV is not kept in your target download directory, so you'll have to hunt it
down. Since the download failed, the temporary file may or may not exist. I leave this
to you to discover as an experiment.
The easiest way to determine whether a download is really running is to look in the
Windows Resource Monitor on the Network tab. You didn't say what operating system you're
running. If it's not Windows, then surely your system has some other equivalent tool for
monitoring system activity, including network load. You'll see a line item for the CoApp
in the Resource Monitor if a download is running. And if there is no such line item,
well, I think you know what that means. So don't waste hours waiting for VDH to tell you
it's done. Use your operating system tools to monitor network activity. When that drops
to 0, the download has stopped. If it has completed normally, VDH will give you its
popup notification. If you don't see that, you'll know something has gone wrong.