EXT-X-BYTERANGE parsing incorrect when offset not present

[mjneil]

The offset portion of the EXT-X-BYTERANGE tag is optional, and should be calculated using the previous segment's offset and bytelength, however the parser currently just assumes a missing offset should default to 0.

https://tools.ietf.org/html/draft-pantos-http-live-streaming-23#section-4.3.2.2

If o is not present, the sub-range begins at the next byte following the sub-range of the previous Media Segment.

[mrlika]

Hi,
Is it going to be fixed? When will be the next release?

[gesinger]

A fix is in progress: #98

[jaredstehler]

PR #98 fixes this issue for me; can we resolve this and publish a new release?

[AwokeKnowing]

Is this released?

[gesinger]

Sorry for the delay, published as v4.4.3

[AwokeKnowing]

@gesinger Thanks! sorry for my ignorance, we use videojs with eme plugin. Does this m3u8 parser get bundled into videojs?

[gesinger]

We'll have to get the new version into https://github.com/videojs/http-streaming, but we should be doing that soon.