Adding WOOD to the fire? And you thought you were being completely safe for work . . .
No banning will happen as long as we do things like refer to one of our preferred sites
like po rn hub like that.
For the record, I am running Windows 11 Pro 64-bit version 23H2 build 22631.3007, Firefox
121.0.1 64-bit, VDH 8.1.3.0a1 beta (supposed to be the same as the general availability
release), CoApp 2.0.11.
In the past, I have had no problems downloading content from there with VDH. Today, I've
got problems. I picked a page at random & without launching playback, VDH showed me a
Side Download at 1920x1080. It started but never finished. It claimed to finish but I
had a useless small file. So I reloaded the extension, reloaded the web page, & tried to
do the same Side Download again. Same result. Then I reloaded the extension again,
reloaded the page again, & this time, I launched playback & let it run for maybe 5
seconds before stopping it. The same Side Download actually got a playable file this
time. Problem is it was only 15 seconds of a 15 minute video. After my results below,
I'm not sure it was even the first 15 seconds of the video.
Time for Plan B. And everybody knows what that is:
https://groups.google.com/g/video-downloadhelper-q-and-a/c/sNfTCMYfiTU
The Network Monitor showed me 2 HLS manifests, files with .m3u8 in their names & in the
Type column the value application/vnd.apple.mpegurl. But looking at the Response column
in the right half, it was obvious that the first one was a master manifest & the second
one was a stream manifest. See attached image #01, which is censored to be safe for
work. So I ignored the second one & ran ffprobe on the first one. Those results are in
attached file ffprobe.txt. Looks pretty ordinary but I note the presence of the hated
timed_ID3 data. I'm pretty sure they never had timed_ID3 data before. Still, Side
Downloads use ffmpeg & ffmpeg has always simply ignored timed_ID3 data, so that should
not have been a problem for VDH. In the ffprobe report near the bottom, the "Unsupported
codec" messages indicate ffprobe is ignoring the timed_ID3 data. In any case, my
experience with trying to get content off that site with ffmpeg has been that it would
give me 403 Forbidden errors. Very unusual. VDH would work but ffmpeg would fail. So I
didn't hold out much hope that this was going to work today. I'm too much of a
pessimist. The proof is in attached file PH Test mp4 Log.txt. As you can see, the
download went swimmingly, in fact, with a well above average download speed. I ended up
with the full 15:07 that ffmpeg reported it had downloaded. The mp4 played just fine in
VLC, video & audio for the entire 15:07. In case anybody might want to try to replicate
my results, I am attaching the URL of the web page on the site in image #02. This is the
safe-for-work way of dealing with these things. Safe-for-work meaning this is how you
foil the bluenosed Google bots & don't end up with your post marked for abuse or simply
deleted.
I don't see anything about this HLS master manifest that should have tripped up VDH. It
should have done a successful Side Download on the first try. What I did as Plan B is
the equivalent of a VDH Side Download. They should both have worked exactly the same.
But VDH failed & manual ffmpeg succeeded. This is clearly something for the VDH folks to
investigate. Which gives me the perfect opportunity to point out once again that I don't
work for VDH. I'm just another user, like most of us posting in this forum. So when I
say investigate, I mean I've done all I can & I can't do any of the further investigation
that I say is required here.