(The log is part of what I've got on my invocation of ffmpeg, which you can see at the bottom of this thread.) It said https is not on the protocol whitelist & then it listed the whitelist: file,crypto,data. But ffmpeg logged an interesting error message. Bat file (which I will include at the bottom of this post, but not here because it went through a few iterations before I hit upon the magic formula).
Then I tried executing ffmpeg directly from a little. That's just the name I chose & it's the name I used on the invocation of ffmpeg. Also, there's nothing special about the name index.m3u8. Obviously, your drive letter & directory structure will almost certainly be different. Then I saved my modified manifest as Q:\PH\index.m3u8. So I copy/pasted the missing bit from one of the entries that looked good onto the front of the first entry, which looked bad. They all begin with and the name of the web site hosting the video. It's easy to figure out what's wrong with the first entry. Maybe it wasn't but that's how I interpreted it. But looking at the manifest, I saw that the first entry looked damaged to me. As in the other thread, the first entry in the monitor was the master manifest. As in that other thread, I opened the monitor before visiting the page. I tried your example video & it wouldn't download for me, either. I'm not going to intervene in this thread further. Either you're sufficiently technical to do this or not. I'm not going to rehash what I've explained at length there. If you want to get some background on the techniques I used to figure this out, you need to read this thread: !topic/video-downloadhelper-q-and-a/8V2cRB-bcK4.
0 kommentar(er)
