Closed GoogleCodeExporter closed 9 years ago
Based on the output below, it looks like there is a gap in your stream(s)
timestamps and Chrome media pipeline is not able to jump over such a large gap.
[113.839s] [cast.player.core.SourceBufferManager] 0: 63.10441207885742 -
87.12940979003906
[113.843s] [cast.player.core.SourceBufferManager] 0: 97.55541229248047 -
111.6954116821289
Original comment by vadi...@google.com
on 2 Oct 2014 at 8:55
Play generated .ts files with mplayer I see 63s~87s is from tstream8.ts and
97~111s is tstream10.ts, and there is another tstream9.ts.
tstreams are generated by ffmpeg on the fly, this issue happen occasionally,
the time mediaplayer stopped playing seems different every time.
Looks like when SourceBufferManager failed to load tstream9.ts after a while it
will give up loading and player stopped.
For my 8 seconds segments, timeout is 30s.
[375.126s] [goog.net.XhrIo] Will abort after 30000ms if incomplete, xhr2 false
I am trying to reproduce this issue and see if there is any network error on
debug console, but no success so far.
I wonder if it is possible set abort timeout?
Thanks.
Original comment by ksc...@ksc91u.info
on 3 Oct 2014 at 3:30
There don't seem to be any network related errors when this occurs (the Network
tab indicates the entire segment has been downloaded), could the MPL be
silently failing to decode a segment? The fact that the MPL then downloads and
processes the next segment is king of unexpected.
Original comment by willlunn...@gmail.com
on 21 Oct 2014 at 8:11
Original comment by and...@google.com
on 10 Nov 2014 at 7:31
Original issue reported on code.google.com by
ksc...@ksc91u.info
on 1 Oct 2014 at 9:20