ithlony / google-cast-sdk

Automatically exported from code.google.com/p/google-cast-sdk
0 stars 0 forks source link

Stable brain freeze or reboot on certain streams #232

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
- Play the test stream from 
https://www.dropbox.com/s/0mni7al8l4glv4b/BrainFreezeStream.zip

What is the expected output? What do you see instead?
- Playback stops after about 40 seconds and the device either reboots or shows 
'Brain Freeze'.

Original issue reported on code.google.com by mikh...@firecore.com on 10 Apr 2014 at 8:27

Attachments:

GoogleCodeExporter commented 9 years ago
Reported behavior was observed with Chormecast (build 16041), cast_receiver.js 
v2.0.0 and media_player.js v0.5.0.

Original comment by mikh...@firecore.com on 10 Apr 2014 at 8:32

GoogleCodeExporter commented 9 years ago
The problem is still reproducible with the v2.2.1 released on May 21st.

Original comment by mikh...@firecore.com on 23 May 2014 at 4:35

GoogleCodeExporter commented 9 years ago
We are facing the same issue, device brain freezes for every ~20minutes 
streaming of high renditions i.e, 1024*426, 1024*720. Low renditions run with 
no issues anyways.

Attached a file with Logs from chromecast console when freeze happened. 
Problem persists even after updating MPL to recent 0.7.0 version.

Any workaround?

Original comment by s...@spuul.com on 11 Jun 2014 at 4:30

Attachments:

GoogleCodeExporter commented 9 years ago
Same issue seen here after 2 minutes of playback on a Smoothstream, and can be 
reproduced again and again. Seem to be related to high bitrates alternates. 

Original comment by mor...@striboldt.com on 23 Jul 2014 at 1:12

GoogleCodeExporter commented 9 years ago
Have seen it also happen on embedded Youtube iframes in custom receivers. Every 
once in a while there will be a video that freezes at a certain point, and 
replaying the video will again freeze it at the same point in time.

Original comment by m...@juko.fm on 23 Jul 2014 at 1:25

GoogleCodeExporter commented 9 years ago
As a general note, please do not use any stream with bitrate higher than 5 Mbs, 
chromecast hardware will have a hard time handling beyond that.

Original comment by anad...@google.com on 23 Jul 2014 at 3:33

GoogleCodeExporter commented 9 years ago
I am a little puzzled about your 5Mbps comment. We have been streaming up to 
8Mbps over hundred Chromecast devices with no apparently instability solely 
attributed to the bitrate. We do some intermittent media player crashes but 
they can happen at lower bit rates as well.

Are you sure that Chromecast hardware is known to have problem with >= 5Mbps? 

To be clear, we do not use media_player.js - we use MSE API.

Original comment by qcom111...@gmail.com on 31 Jul 2014 at 6:45

GoogleCodeExporter commented 9 years ago
Also if this is a know limitation, Google should make sure that this is handled 
by the internal ABR algorithm - which normally is influenced by two factors 
(CPU and bandwidth). So if for some reason the Chromecast consumes 100% CPU due 
to decoding/rendering of a bitrate > 5Mbit it should switch to a lower 
alternate if available.

Original comment by mor...@striboldt.com on 31 Jul 2014 at 7:48

GoogleCodeExporter commented 9 years ago
We don't use the rate switching facility of manifest based streaming like HLS 
or DASH. We do decrypt on each segment at >> 5Mbps without any problem. We 
capped it at 8Mbps. The CPU profile looks good with 30-70% idle item. Hardware 
acceleration appears to be used for both decoding and decryption.

If there is a real hardware limitation at low level media pipeline for >> 5Mbps 
H264 stream, please let us know so we don't play with fire.

Original comment by qcom111...@gmail.com on 1 Aug 2014 at 9:13

GoogleCodeExporter commented 9 years ago
If you are able to go up to 8 Mbps without experiencing issues, you may 
continue to do so but going higher than that is not recommended.

Original comment by jonathan...@google.com on 12 Nov 2014 at 11:31