gapu / google-cast-sdk

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

This error is not propagated to the sender app: Uncaught NotSupportedError: Failed to execute 'addSourceBuffer' on 'MediaSource': The type provided ('video/mp2t; codecs="avc1.66.31,mp4a.40.2"') is unsupported.media_player.js:102 #609

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I have an m3u8 file that apparently is not supported by the Chromecast however 
my sender app is never notified that the file failed to play. 

The error: 

Uncaught NotSupportedError: Failed to execute 'addSourceBuffer' on 
'MediaSource': The type provided ('video/mp2t; codecs="avc1.66.31,mp4a.40.2"') 
is unsupported.media_player.js:102 memedia_player.js:111 Demedia_player.js:118 
h.updatemedia_player.js:117 h.openmedia_player.js:219 h.Hf

The m3u8 looks like this:

#EXTM3U
#EXT-X-VERSION:3
#EXT-X-STREAM-INF:BANDWIDTH=2048805,CODECS="avc1.66.31,mp4a.40.2",RESOLUTION=128
0x720
chunklist_w517510829.m3u8

I am using this player sample https://github.com/googlecast/Cast-Player-Sample

Original issue reported on code.google.com by casol...@gmail.com on 6 Jul 2015 at 9:26

GoogleCodeExporter commented 9 years ago
Some builds of Chromecast reject "avc1.66.31" so it is recommendation to use 
"avc1.66.30" instead either by updating the playlist or using 
host.processManifest workaround

host.processManifest = function(manifest) {
  return manifest.replace(/CODECS=\"avc1.66.([0-9]*)/g, 'CODECS=\"avc1.66.30');
};

in a custom receiver.

Original comment by anad...@google.com on 7 Jul 2015 at 8:33

GoogleCodeExporter commented 9 years ago
Thanks for the information and that might solve my issue but shouldn't the 
error get propagated to the sender app if I don't apply that fix? I mean isn't 
there a case where that could be a valid error and the sender should find out 
about it?

Original comment by casol...@gmail.com on 8 Jul 2015 at 1:04

GoogleCodeExporter commented 9 years ago

Original comment by jonathan...@google.com on 8 Jul 2015 at 5:21

GoogleCodeExporter commented 9 years ago
We run into the same problem. Will that be fixed in a future chromecast 
firmware?

Original comment by team2...@gmail.com on 29 Jul 2015 at 2:18