Skip to content
This repository has been archived by the owner on Dec 8, 2024. It is now read-only.

Why replace seqNo 0 to 1? #37

Closed
hori-ryota opened this issue Feb 18, 2016 · 2 comments
Closed

Why replace seqNo 0 to 1? #37

hori-ryota opened this issue Feb 18, 2016 · 2 comments
Labels

Comments

@hori-ryota
Copy link
Contributor

I think #EXT-X-MEDIA-SEQUENCE value is allowed 0 (example: Technical Note TN2288: Example Playlist Files for use with HTTP Live Streaming), but 0 is replaced now. Why?

m3u8/writer.go at master · grafov/m3u8

@bradleyfalzon
Copy link
Collaborator

We had been discussing this today, and don't completely understand why it was introduced in b5ae3cd.

Note, we don't have an issue with this (right now at least) in live or VoD, it's just strange to see.

@hori-ryota
Copy link
Contributor Author

My project use hls live streaming starting from 0 SeqNo.
We decode our original playlist and processed it with this library.

Now, this library encode like followings at first chunk.

#EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:5
#EXT-X-MEDIA-SEQUENCE:1
#EXTINF:2.0,
0.ts
#EXTINF:2.0,
1.ts
#EXTINF:2.0,
2.ts

And next,

#EXTM3U
#EXT-X-VERSION:3
#EXT-X-TARGETDURATION:5
#EXT-X-MEDIA-SEQUENCE:1
#EXTINF:2.0,
1.ts
#EXTINF:2.0,
2.ts
#EXTINF:2.0,
3.ts

This stream is broken because SeqNo is not changed.
Player cannot playback normally now.

Will you make modifications without a disadvantage?

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

No branches or pull requests

3 participants