video element ignores H.264 video_full_range_flag - by Snowknight26

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


ID 777629 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/27/2013 12:29:58 PM
Access Restriction Public

Description

The video element ignores the H.264 video_full_range_flag resulting in incorrect black levels (crushed blacks).
Sign in to post a comment.
Posted by Snowknight26 on 9/20/2013 at 10:08 AM
Still not fixed.
Posted by Microsoft on 6/27/2013 at 6:32 AM
Thank you for your feedback.

This issue was resolved in Windows 8.1 released on 06/26/2013 and we have verified this fix against the release build.

Please very the issue is resolved by installing the Windows 8.1 update(from the Windows site only) and install the latest display drivers(crucial),
If the issue is not resolved, please file a new Feedback or reactivate the existing one including a new IEDiag and any new information pertinent to your Feedback.

You can download the official Windows 8.1 preview here --> http://windows.microsoft.com/en-us/windows-8/download-preview

Best regards,

The Internet Explorer Team
Posted by Snowknight26 on 6/13/2013 at 11:37 AM
See the attached zip, 'IE10 color range.zip'.

'in=pc,out=pc.mp4' was encoded with full color range (0-255). The H.264 SPS header has video_signal_type_present_flag and video_full_range_flag set.
'in=pc,out=tv.mp4' was encoded with limited range (16-235). Because of this, both of those flags are not needed (and are not set).

Both files should display correctly but only 'in=pc,out=tv.mp4' does. 'in=pc,out=pc.mp4' is too dark.
Posted by Microsoft on 6/12/2013 at 11:22 AM
Thanks for providing us the sample clip with bug report.

We have analyzed the bitstream “Alien_Swam.960x540.mp4” and this bitstream does not contain the information to indicate that its full_range H.264 video. Video_signal_type_present_flag is 0 which is required along with video_full_range_flag =1 to indicate that video is full_range.”

Best regards,

The Internet Explorer Team
Posted by Microsoft on 5/20/2013 at 12:18 PM
Thank you for your feedback. We will be investigating this issue further.

Best regards,

The Internet Explorer Team
Posted by Snowknight26 on 5/7/2013 at 4:54 PM
On one hand, this issue is only present on one system I can test, leading me to believe it's an AMD issue.
On the other hand, the issue only presents itself in IE (and not Chrome, which I believe Media Foundation Transform filter to decode the video [Microsoft H264 Video Decoder MFT?], or Firefox). Does that mean it's an IE issue? I can't say.

I honestly don't know. Is it somehow possible to get a hold of someone from AMD to collaborate to get to the bottom of this? Hopefully that'll not fall into the realm of paid support.
Posted by Microsoft on 5/7/2013 at 1:51 PM
Snowknight26,
What would you like us to do with this case?

Best regards,

The Internet Explorer Team
Posted by Microsoft on 2/4/2013 at 1:22 PM
Thank you for your feedback.

Your input is very important to us, and it helps us improve the quality of Internet Explorer. However, we are unable to address your feedback during this release.

We continue to welcome user input, so please don't hesitate to report other ways that we can improve Internet Explorer.

Best regards

Internet Explorer Team
Posted by Snowknight26 on 2/4/2013 at 12:59 PM
I have spoken with AMD; they recommend that Microsoft also takes a look at the issue. As such, I am reopening the bug report.
Posted by Snowknight26 on 1/28/2013 at 5:27 AM
Nevermind, please close this bug report. I submitted it before investigating all avenues.