HLS bitrates suck, directstream mkv handles higher bitrates

[hawken93]

Describe the bug I think the cast receiver api is very resource heavy when doing HLS streams. On the gen2 and gen3 I have had 10Mbit/s streams stall out and in the performance tab it seems to be CPU starved. Memory can also be an issue but there's a disconnect in that tab between memory usage and GC, because even with relatively low apparent usage the GC can kick in and stall the program.

To Reproduce

1. Play HLS stream of something around 10-12 Mbit/s on gen2/gen3, maybe a bit higher for ultra
2. watch it permanently stall after some amount of time
3. directstream the same file
4. great success

Expected behavior I wish for the same bitrate limits for HLS as the directstream (progressive playback). It seems like HLS is severely capped.

System (please complete the following information):

• Cast: gen2 & gen3

Additional context https://github.com/silvermine/videojs-chromecast/issues/73 https://stackoverflow.com/questions/23268808/hls-playback-performance-and-stability-on-chromecast

[hawken93]

Is there anything we can do to tune the chromecast player for higher bitrates? Things like limiting the amount of HLS segments it tries to keep in RAM?

[Artiume]

https://issuetracker.google.com/issues/148084484 https://issuetracker.google.com/issues/139175785

[hawken93]

https://github.com/mgile/Cast-Media-Player-Library-Sample/blob/master/MediaPlayerLibrarySample.html Using MPL with the old cast.receiver api https://github.com/digitalegarage/chromecast/blob/master/player.html

trying this to attempt dry-run of MPL in a browser