-
Notifications
You must be signed in to change notification settings - Fork 315
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
Question: #EXT-X-MEDIA:TYPE=AUDIO #96
Comments
Yes, I agree this is a bug, Did you want to take a stab at fixing this? It might require a bit more post processing to keep a list of all Relevant parts of the RFC: https://tools.ietf.org/html/rfc8216#section-4.3.4.1:
https://tools.ietf.org/html/rfc8216#section-4.3.4.2:
Two good examples: https://tools.ietf.org/html/rfc8216#section-8.6 and https://tools.ietf.org/html/rfc8216#section-8.7 |
hi @bradleyfalzon probably i can take this bug and fix it, but currently pretty busy, so i think some more or less good output will be somewhere end of next week or week after. |
we probably can keep as additional all alternatives mapped by group id separately, and add methods to Variant to get correct alternatives if Variant Audio match any Variant Group-ID? |
That sounds great, if you start running out of time or it's getting hard, let me know.
That's how I'd probably solve it given if this was adding the functionality, but because we're trying to maintain backwards compatibility, we'd first need to correctly populate those For a backwards compatibility point of view, we could (not a complete set of tasks):
This is backwards compatible, but we could add methods as you've suggested, something like Does that sound possible? |
yea, i think this way we go. |
Found one more bug or "feature" :D
While i'm agreed that this is not a bit normal, but this i got from Akamai multiple times. so i will combine probably initial ticket with this one together or should i create another ticket to cover this problem? |
Appears to have been added in e045850, but the commit doesn't appear to indicate why. https://tools.ietf.org/html/rfc8216#section-4.3.4.2.1 says:
So the playlist appears to be perfectly valid, and there's definitely a bug in this library. @grafov do you know anything about this commit and why this behaviour might be occurring? At first sight, it looks like we should revert the commit, I can't see why we'd deduplicate it OR if we do want to keep it, let's include the URI in the algorithm: Line 88 in d137fcd
|
@bradleyfalzon I didn't remember details about this commit. If you found that it is breaks the logic described in the standard this commit should be reverted. |
Pardon for been quite for while (insane amount of work had), will have time next week to work over this issue. |
Hi, i have problem with time at this moment, probably we'll put this issue on-hold for a bit and as soon ill have time, i'll take a look into this since i need this functionality at the end. |
No problems, we're all in similar positions. |
Looks like i can get information about alternatives only from first element from variants array.
Playlist example:
Dumped Variants from
masterpl := p.(*m3u8.MasterPlaylist)
This is correct behaviour, shouldn't we have information about alternatives for each variant?
The text was updated successfully, but these errors were encountered: