After pausing encoding, cast sender should flush and issue a key frame |
||||
Issue descriptionWe get into a state where there are many frames in flight, which don't make it over to the Chromecast ... and so then we just stop encoding or sending more frames. Upon recovering from such as situation, we should abort sending any of the old frames that are unlikely to be delivered by the target playout time. We can force a key frame to continue.
,
Dec 11 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 14 2017
,
Dec 14 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by erickung@chromium.org
, Dec 2 2016