I'm doing this on Windows 7 64-bit, Firefox 97.0 64-bit, licensed VDH 7.6.3a1 beta, CoApp
1.6.3. When I first visited your web page, I got what you can see in attached image #01.
I thought about translating the page with Google Translate, but then I thought I'll just
go ahead & download the one variant I have highlighted in the image. It was the largest
variant shown there. The download appeared to complete successfully after about 2
minutes. The Resource Monitor showed I was getting about 2 million bytes per second
download speed, quite decent. The file was 75M & Windows file properties claimed it was
of duration 51:32. But when I played it, it lasted only 20:36 & there was no audio. It
did play fine, but it was clearly not what we wanted here. The original VDH menu said
the file would be 226.9M. Clearly, I had only a partial file, not to mention it was
silent.
So I went to my alternative method of downloading something when VDH cannot download it.
Take a look over here:
https://groups.google.com/g/video-downloadhelper-q-and-a/c/BzPLK2YyL-s
You'll find many topics there that will probably be helpful. In the case of this
example, I used the one you can find by doing a string search on the words "cannot
download." Click through to the link you'll find there & read that. The rest of what
I'm going to say here will make no sense to you until after you read that thread. When I
filtered on .m3u8 in the Network Monitor, I got no results. So then I filtered on .mpd
instead. Presto. I got one result. Clearly, this means this site does not use HLS but
it does use DASH. Another example to encourage Michel to change his mind about not
supporting this type of streaming. Unfortunately, when I tried to do ffprobe on this
manifest, I got these errors:
[dash @ 00000000006032c0] Failed to open an initialization section
[dash @ 00000000006032c0] Error when loading first fragment of playlist
https://kinescope.io/200752471/master.mpd: Invalid data found when processing input
That last line shows the URL of the manifest.
After a couple of reloads of the page, I couldn't get any further than this. Apparently,
this site does not provide media in a generally accepted standard format according to the
international standards. Whatever they are doing, it probably works on their site
because they have special code to make it work for them. It appears to be proprietary.
I wouldn't expect either VDH or ffmpeg to work on this site.
But I didn't completely give up. I double clicked on the manifest in the Network
Monitor. That gave me the browser page you can see in attached image #02. At this
point, I started guessing. This was just pure speculation on my part. I wouldn't expect
this approach to work on another site. I would hope it would work on other pages of this
site but I wouldn't put forward any guarantees. This is just something I tried here & it
seemed to get me somewhere.
I copy/pasted the URL I have indicated with a box in attached image #02 into a separate
browser tab. You can see what I got in attached image #03. It was sort of encouraging.
Then I clicked MB2 in the middle of the playback window to pop up the context menu, as
you can see in attached image #04. On that, I clicked on Save Video As. This opened a
standard Windows file selection dialog. I saved the file on my system, as you can see in
attached image #05. Despite the discouraging results there, I went ahead & played the
file in VLC. I was a bit surprised to see that it would play, as you can see in attached
image #06. I skipped around in it to see whether it was all there & indeed it was, as
you can see in attached image #07, which shows the closing credits just a couple of
seconds before the end. The only problem was that it was silent. Where could I get the
audio?
Remember now, I'm flying by the seat of my pants here. These are all pure, wild-ass
guesses. I did a string search on "audio" in the XML file, the .mpd, the manifest in
attached image #02. Attached image #08 shows this must be my lucky day. As before, I
copy/pasted the first audio URL into a new browser tab (attached image #09). Once again,
I popped up the context menu (attached image #10) & saved the file (attached image #11).
You'll have to trust me that, despite my initial doubts, the audio file played perfectly,
the full 51:32 of it. At least, sampling it here & there seemed to indicate it was all
there.
Next, I set up playing the two files synchronously in VLC. In attached image #12 I have
highlighted the parts of the dialog that you will want to use. There is a reference to a
complete tutorial on VLC synchronous playback in the Table of Contents thread.
At this point, I don't think anybody would be surprised to learn that I now had a
perfectly complete . . . What is this? Some kind of tutorial for writing a program in
some language to use
ASP.NET to control a game controller? Anyway, I had the whole
thing, video AND audio, and I suppose if I spoke Russian, I might learn something from
this. I would first have to be motivated to learn the subject, and then I would have to
be motivated to learn Russian. I have to assume you are already qualified in both areas.
I was & remain a bit puzzled about the file sizes. The original VDH menu (attached image
#01) claimed this would be 226.9M. You can see in attached image #11 that the 2 files
combined are a lot smaller than that, in fact only about 124.5M. I can't explain what
VDH was looking at.
So here you go. This is how you can get this content. I don't want to give any
illusions that this approach would work on another item. You'll have to try it & tell me
whether you can do this with anything else. But at least this worked in this one case.
I still say there is something non-standard about the way this site is presenting its
media content. In light of that, I can't blame VDH for failing on this site. But you
can, with a little persistence, break into it & get what you want. Since it is apparent
that only the 2 items identified as "Initialization sourceURL" are needed, I don't
understand why there were nearly 4000 lines of information in this manifest. It seems to
me they could have gotten away with just 2 lines. In other DASH manifests I have looked
at, there's only a handful of lines. Certain lines look like they are patterns,
templates, within which certain parts are meant to be replaced by gradually increasing
numbers. Typical, some part of a partial URL will contain something like $ID. This
indicates that during processing of the manifest, the player would replace the $ID by 0,
and then 1, and then 2, and then 3, and then . . . and so on. Instead of that, they
appear to have explicitly included every last individual URL. It looks like they have
manually supplied something a program could have automatically generated for them. I
speculate that the web devs on this site don't competely understand how to do this
correctly. But I'm not a web developer so I'm in no position to tell them how to do it
right. It just looks wrong compared to what I've seen on other web sites.
Good luck!