This thread is just a few months shy of 4 years old. Since the original poster told us
about his environment, there have been several new releases of VDH, several new releases
of the CoApp, & many new releases of Firefox. I have had problems with recording
livestreams that have been solved by VDH 7.6.3a6 beta. There are several threads on this
forum in which I have discussed the issues. Try VDH 7.6.3a6 beta & CoApp 1.6.3, which
are the current releases as of the moment I am writing this. Also, use the current
Firefox, which is now 106.0.5. Tell us your experience with the current software & then
maybe we can have a discussion.
The thing that goes at the end of an MP4 that acts as a sort of table of contents is
called, as far as I know, the moov atom. The problem with the moov atom in VDH is that
Michel has made a bad design choice. He keeps the moov atom in program storage & allows
the operating system's paging management to take care of that data. VDH then writes the
moov atom into the MP4 when the download completes. But keeping the moov atom in program
storage means it is volatile & subject to being prematurely discarded. Aside from the
problems of unplayable files, letting that data be paged causes problems, at least in
Windows. When multiple concurrent VDH downloads happen to complete more or less at the
same time, I have observed my Windows 7 system thrashing for as long as half an hour. My
entire system becomes unusable until Windows sorts things out. It does always sort
things out, but some of my concurrent downloads either are corrupt or simply never
started. So on top of everything else, you need to be judicious about trying to do
multiple concurrent downloads in VDH. A corrected design for VDH would involve keeping
the moov atom in a file on disk. That way it's persistent & there's the possibility of
successfully completing an interrupted download, possibly even after a complete system
reboot. It also takes management of that data out of the utterly untrustworthy hands of
Microsoft.
VDH uses ffmpeg but not for the actual download operation. VDH uses ffmpeg in the
aggregation & conversion functions, but not the download. The ffmpeg distributed with
VDH is a slimmed down build that Michel customized for use by VDH. It is not suitable
for general use the way the official ffmpeg from
ffmpeg.org is. I have tried to use the
captive ffmpeg included with VDH & I can assure you it is not satisfactory for general
use.
I have found that using the stop button on the VDH blue dot status menu is not entirely
reliable, even in 7.6.3a6. Sometimes it terminates the download & you have a playable
file. Sometimes it terminates the download & you have a junk file that you have to
discard. Perhaps one of your editing tools would repair such a damaged file. Good luck
with that. The only way I have found to make VDH reliably terminate a download before it
is done is to physically disconnect the Internet connection. I unplug it from
electricity. VDH recognizes that as a termination of the input connection & happily
writes the moov atom into the MP4. The file is then playable. It is my understanding
that downloading into MKV files is not subject to this problem since the MKV format is
simply completely different from MP4. I am under the impression that you can interrupt a
download into an MKV & you will have a file that can be played. Every time. I believe
MKV is even playable while the download is still in progress. Note the weasel words in
what I'm saying. You would have to test my claims about MKV. I have not verified them.
I am simply going on what I have read & what I have read between the lines.