UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Find a Win 7 (d3d9) machine with nVidia GPU.
2. Make sure everything is default (esp. with hardware accerlation on).
2. Open the attached video or https://www.youtube.com/watch?v=fcCX8ieV3Oc

What is the expected behavior?
The color should be close to the marked value, i.e. 0, 16, 235 and 255 replactively (values are not exact, due to rgb->yuv420 coversion when I was making the video).

What went wrong?
The color is "washed out" due to incorrect color range expansion. The video is in limited/studio range, but Chrome doesn't correclty expand it to full range when rendering. The 0,0,0 will became 16,16,16, and so on.

The attached screenshot shows the color difference between Chrome, Firefox vs in a local video player (mpc).

Did this work before? N/A 

Is it a problem with Flash or HTML5? N/A

Does this work in other browsers? N/A

Chrome version: 63.0.3208.0  Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 27.0 r0

Contents of chrome://gpu: 

This is a long-standing bug in Win 7 + nVidia setup. You can find lots of mentioning of this bug by users all over the Internet in recent years.

Initially it was tracked by  issue 333619  (see my particular comment#98 there too), but later that issue got split into a few (particluarly, please see  issue 576419 ). Since today, most of those saperate issues were closed by hubbe@, I feel like I would make another ticket to notice devs that this bug is still there.

This bug is also reproducable on YouTube, Twtich or similar video websites: https://www.youtube.com/watch?v=fcCX8ieV3Oc

This bug also exsits in Firefox, which is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1161349

This bug cannot be reproduced in IE11 (with the YouTube link, since I can't seem to open local video with IE), but IE doesn't seem to support MSE so things might be different there.

There is also a workaround, which is to manually set your (target) color range to full:
in the NVIDIA Control Panel under: Video > Adjust video color settings,(1) choose which display (monitor) to change, and then (2) under "How do you make color adjustments" switch it from "With the video player settings" to "With the NVIDIA settings" and choose full range (0-255). Of course, this is not desirable as it could mess up other programs.

As far as I know, this bug is D3D9 only, can't be produced on Win 10; and it's nVidia specific. But I can't confirm them 100%. What I can confirm is hardware video decoding is required to repro the bug.

My connection to montior is via DVI, since some people report there are other issues with HDMI ports.
 

Deleted: out.mp4 201 KB

	out.mp4 201 KB View Download

Deleted: screenshot.png 333 KB

	screenshot.png 333 KB View Download