-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support DASH manifests that have content spanning multiple Period
definitions
#55
Comments
I'm not sure what you mean to be quite honest. The DASH parser and downloader is currently limited to only use the first An example MPD would likely be best. |
Yes, that's exactly what i mean, and do you have a email or something, i would like to send mpd privately |
Well, there's a problem with supporting multi-period manifests. While it might or might not be the case for your manifest, most manifests do not have any way to link one Representation (or even Adaptation Set) between one Period and another. There might not even be the same bitrate's available, or even the same resolution, across periods. There isn't usually a reliable way to link representations to their correspondents. Some manifests have literally no identifiers to go by at all either. It's a difficult task to do. |
ok, not in a hurry, and nm3u8-re can completely download the track across multiple period, maybe can refer to the source code. |
Period
definitions
Is your feature request related to a problem? Please describe.
a track from mpd is splitted by multi-init, like "id=7 init link startNumber=1 t="1992" d="48048" r="149"" and "id=7 init link startNumber=151 t="7209192" d="48048" r="558"".
In this case, only first part can be download.
Describe the solution you'd like
Combine these parts with same id and continuous startnumber in a track.
I can provide example mpd if needed.
Thanks in advance
The text was updated successfully, but these errors were encountered: