+Ali Naddaf I'm posting to comment on your (chromecast's) attitude to HLS. You say 'HLS is expected to work when stream is conforming to the specs.'

This seems reasonable on the surface - but it really isn't. Ask what would happen if the Chrome Browser promised only to render pages which 'conformed to the specs'. -Particularly if the response to non-conforming web pages was to crash or become unresponsive.

I'm guessing 10-50% of the web would stop appearing in Chrome and your developers would be sacked.

Video is just like web-pages. The specs are large and labyrinthine, and most people who produce video or web pages have never gone near them. The only sane way for a player to approach the problem is to render what you can and degrade gracefully. Of course - that's what all video players (with it seems the exception of chromecast) actually do. You play the chunks you can and discard frames or even segments when you can't.

To put it more simply:
-If I can crash chromecast with a malformed HLS stream, then that's a chromecast bug.
-If chromecast gives up on an HLS stream after encountering an error in one segment, then that's a chromecast bug.
-And more generally, if a stream plays in other players, but not in Chromecast, then if not a bug - it's certainly a chromecast inadequacy.

I know we have been butting heads for a while - but I sincerely hope this will encourage you and your team to reassess your approach to HLS. As I have said before, I'd love to see chromecast successful, and I believe that to achieve success, it is important that you make life easier for developers who want to support you.
Shared publiclyView activity