Ticket #1542 (closed bug: duplicate)

Opened 18 months ago

Last modified 17 months ago

HLS: Squeeze 8 streams giving error #1069

Reported by: jeroen Owned by: jeroen
Priority: Normal Milestone: Plugins
Component: flash Keywords:
Cc: Forum thread:

Description (last modified by jeroen) (diff)

I created an HLS video using Squeeze 8 and found a sample HLS video on developer.apple.com. I have created tests using these two videos using JW Player (adaptive branch, 5.8 release, and 5.8 with HTML5 mode) and plain HTML5. I've only been testing in Chrome and Safari for now. Will test in other browsers once I get these two working.

http://aashbacher.s3-website-us-east-1.amazonaws.com/hls-player-tests/
  • Video from Squeeze 8 plays well using plain HTML5 player and JW Player in HTML5 mode (expected).
  • Using JW Player in Flash results in error 1125 (RangeError).

Change History

comment:1 Changed 18 months ago by jeroen

  • Description modified (diff)

comment:2 Changed 18 months ago by jeroen

  • Description modified (diff)

comment:3 Changed 18 months ago by jeroen

The issue with these streams is that the TS fragments cannot be played by themselves. This in turn seems to be a result of the fragments not starting with a PAT / PMT packet. The first fragment has the PAT and PMT (pink) in the beginning, the second fragment has them after 15 packets of the first video frame are already processed.

If I lift the restrictions of our parser a little, the stream does load. However, since the PAT/PMT packets in subsequent TS fragments show up after the keyframes, the keyframes are not loaded and the video starts blocking more and more.

I presume iOS does not have this issue, since they load the fragments into a buffer before unpacking the PES streams for decoding. That's something we are looking into as well, but it requires a bit of a redesign around our fragment loading.

comment:4 Changed 17 months ago by jeroen

  • Status changed from new to closed
  • Resolution set to duplicate

Added test stream to suite. This should get fixed as part of #1224

Note: See TracTickets for help on using tickets.