There is one tricky bit I should point out. Let's take the example of the first manifest
URL in your file you attached to your first post:
\"
https://174vod-adaptive.akamaized.net/exp=1677467958~acl=%2Fe44d4cef-3a16-4d4b-91cc-bb0adfd40005%2F%2A~hmac=8a210951ae97a0cb2bde2ea06400c23aa7ec014c6733ad017d2b16f6ccb0a47c/e44d4cef-3a16-4d4b-91cc-bb0adfd40005/sep/video/3d53e023,a1b08b14,c3e14cbb,cccc5e55,d76428d5/audio/92adc3d6/subtitles/74789014-English%20%28auto-generated%29-en-x-autogen-cc/master.m3u8?external-subs=1\\u0026query_string_ranges=1\\u0026subcache=1\\u0026subtoken=e50dda4c13494ff03dd8ab0272df94bc5202ef7945ee786abcb53f9d510dfb86\"
If you can keep your eyes from spinning out of control, you will see master.m3u8 inside
there. The m3u8 tells us this is an HLS manifest. The further appearance of master.m3u8
means it is almost certainly a master manifest.
First off, whatever language the weird file is written in, it uses \ as an escape
character. That means that, for example, the leading \" really means just ". Similarly,
the trailing \" really means just ". But " isn't part of the URL anyway. It's just that
in order to figure out the beginning & end of any URLs in that weird file, you need to
look for the \" pair surrounding the URL.
You'll see a few instances of \\u0026 within the URL. Again, \ is an escape character.
The real string is \u0026. But even that is kind of smoke meant to confuse us. \u0026
is really just &. I had to Google that to learn that little tidbit. Try it yourself.
Do a web search using \u0026 as your search key. So your URL is really this:
https://174vod-adaptive.akamaized.net/exp=1677467958~acl=%2Fe44d4cef-3a16-4d4b-91cc-bb0adfd40005%2F%2A~hmac=8a210951ae97a0cb2bde2ea06400c23aa7ec014c6733ad017d2b16f6ccb0a47c/e44d4cef-3a16-4d4b-91cc-bb0adfd40005/sep/video/3d53e023,a1b08b14,c3e14cbb,cccc5e55,d76428d5/audio/92adc3d6/subtitles/74789014-English%20%28auto-generated%29-en-x-autogen-cc/master.m3u8?external-subs=1&query_string_ranges=1&subcache=1&subtoken=e50dda4c13494ff03dd8ab0272df94bc5202ef7945ee786abcb53f9d510dfb86
If you decide to use a command script, as I strongly urge in that tutorial, you will also
need to double all the % signs, a topic I touch on in the tutorial. So your URL would
become this:
https://174vod-adaptive.akamaized.net/exp=1677467958~acl=%%2Fe44d4cef-3a16-4d4b-91cc-bb0adfd40005%%2F%%2A~hmac=8a210951ae97a0cb2bde2ea06400c23aa7ec014c6733ad017d2b16f6ccb0a47c/e44d4cef-3a16-4d4b-91cc-bb0adfd40005/sep/video/3d53e023,a1b08b14,c3e14cbb,cccc5e55,d76428d5/audio/92adc3d6/subtitles/74789014-English%%20%%28auto-generated%%29-en-x-autogen-cc/master.m3u8?external-subs=1&query_string_ranges=1&subcache=1&subtoken=e50dda4c13494ff03dd8ab0272df94bc5202ef7945ee786abcb53f9d510dfb86
But that's only if you use a .bat file. If you handle this some other way, you wouldn't
double the % signs.
The URLs you are likely to encounter almost always contain strings, sometimes rather long
strings, of gibberish letters & digits. These strings uniquely identify your online
session. They connect your browser session to the web server. They may even somehow
contain your user ID & password in some sort of encrypted form. It is also common for
these gibberish strings to expire. The URL I'm quoting above from your file attachment
no doubt pointed to the manifest we want. But it no longer does. You have to visit the
page again to get the web server to generate a new manifest with new gibberish in its
URL. Then you have to give that URL to ffmpeg within a reasonably short period of time,
usually within 20 minutes or so. Otherwise, you have to reload the page & start over.
I also see mention in that URL of "subtitles" & "auto-generated." I suspect there are
captions associated with your video. We can figure that out once you run your manifest
URL through ffprobe. It will tell us where the captions are, if they exist. On the
other hand, if they are automatically machine generated, I wouldn't be surprised if they
turn out to be pretty worthless. But we can't know that ahead of time. We have to get
them & see how well they match up with the video content. The captions might be closed
captions. I do see cc in that URL. If they are closed captions, you will just get them
as part of downloading the video. Closed captions are typically embedded within the
video track & you just get them automatically when you download the item. Only if
ffprobe tells us there are external captions would we need to download those in their own
invocation of ffmpeg.
Are we nearing enlighentment yet?