Bitrate limit for chromecast Gen1

[hawken93]

Describe the bug CC gen1 is likely to fail on high bitrate files even if they're within spec, it's a weak device

steps

1. get cc gen1
2. play high bitrate file
3. something is guaranteed not going to work

Expected behavior reasonable max bitrate for the device

Logs I'm going to my parents where I'll have access to a gen1 device to try and do experiments with

Additional context This problem hasn't been proven in practice yet but I know it exists, and I would love to see the gen1 have some more useful life left

[YouKnowBlom]

Gen 2 have the same hardware iirc so unless the 2.4GHz wifi limit is the bottleneck they should have the same issues

[ferferga]

@hawken93 I'm with @YouKnowBlom : I played 59 GB remuxes without issues using Videostream on my gen 1. However, my chromecast was 1 meter away from my AP and my 2G radio had stable speeds above 150 Mbps, which is not really usual.

We shouldn't limit per-se. Detecting the signal quality of the device might be a good reference.

Even better would be to move to Network Information API (although I don't know if it exists in Chromecast): https://developer.mozilla.org/en/docs/Web/API/Network_Information_API

[hawken93]

The bitrate detection seems okay but I think it may be a little optimistic. Peak speed is not a guarantee, so maybe going down to 70-80% of detected will give a better safety margin. As long as it doesn't get overwhelmed then I agree. For HLS the experience seems to be different but that's its own topic

[hawken93]

I think we can ignore this until someone hits this kind of problem