Skip to content
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 for parsing extended #EXTM3U header #324

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

johnyxpro
Copy link

Hi,
This pull request add the support for parsing extended #EXTM3U header, for extended M3U playlists with custom attrubutes.

See:
https://github.com/AlexanderSofronov/iptv.example/blob/master/README.md
https://vip-tv.online/forum/68-664-1
https://vk.com/wall278393568_10115

@bbayles
Copy link
Contributor

bbayles commented Jul 11, 2023

For what it's worth, I think this type of parsing is far enough from RFC 8216 and its descendants to recommend using a different library.

@davemevans
Copy link
Contributor

The title references #EXTM3U, but the code changes the #EXTINF parser.

Extended #EXTINF parsing is already well supported by using a custom tag parser to override builtin parsing: https://github.com/globocom/m3u8#custom-tags

@johnyxpro
Copy link
Author

The title references #EXTM3U, but the code changes the #EXTINF parser.

Extended #EXTINF parsing is already well supported by using a custom tag parser to override builtin parsing: https://github.com/globocom/m3u8#custom-tags

Yes you are right. Unfortunately, there is a bit of confusion with the title.
My pull request makes a small change (literally 1 line) to the #EXTINF parser which causes most iptv playlists to parse fine without errors and without involving custom tag parsers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants