Decoding artifacts during playback of H.264 content
Reported by
maarten....@opentelly.com,
Mar 2 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Example URL: https://dl.dropboxusercontent.com/u/6679751/fragments%28video%29-new.mp4 Steps to reproduce the problem: 1. Open the MP4 reproduction URL 2. Play the 2 second MP4 content 3. Notice that you did not see any decoding artifacts 4. When the content ends, click the play UI control to return back to the start and replay the content 5. Notice that half the screen is black/green during the first second What is the expected behavior? 5. There should not be any decoding artifacts What went wrong? 5. There are decoding artifacts during playback of the MP4 Did this work before? N/A Is it a problem with Flash or HTML5? HTML5 Does this work in other browsers? No Firefox 44.0.2 Chrome version: 48.0.2564.116 Channel: stable OS Version: 6.3 Flash Version: Shockwave Flash 20.0 r0 This is a new issue but also a follow up on issue 585452 The problem has been reproduced on Windows 8.1 The problem does NOT occur on OS X The problem does NOT SEEM to occur when using VLC to play the MP4 The same problem occurs in the Firefox 44.0.2 browser, so it is not Chrome specific. The same problem does NOT occur in the Internet Explorer 11 browser. The MP4 is created from a segmented stream, but that should not be relevant for the issue. When playing the segmented stream I can see these decoding artifacts during playback (without seeking) when the stream switches to a different representations during playback or at the start of the stream.
,
Mar 4 2016
=> sandersd who was looking at the other issue.
,
Mar 7 2016
+ananta@ for DXVA
,
Mar 17 2016
I have a suspicion that issue 594266 is related, although the symptoms are very different. If we can determine the particular situation that causes this bug, we can create a fresh decoder when this behavior may be triggered.
,
Mar 17 2016
Whoops, that issue is still Restrict-View-Google. Publishable summary is that in certain cases, DXVA misbehaves when crossing fragment boundaries. Fix will be to construct a new decoder at such boundaries.
,
Apr 11 2016
Not visible on Win10 running in VM on OSX. Visible in Win7 on a hardware.
,
Jun 12 2017
This bug has been stale for > 1 year. If you still want to keep it, please change StaleAssigned label to StaleKeep. If you don't want to keep it anymore, you don't need do anything, I will close it in 30 days. thanks
,
Jul 18 2017
this bug has been stale for > 1 year. resolve as won't fix with label StaleClosed. If you think it's worth to keep, please re-activate and assign appropriately. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by yini...@chromium.org
, Mar 4 2016Owner: dalecur...@chromium.org
Status: Assigned (was: Unconfirmed)