After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 757605 - Does not honor H.264 YUV coefficient flag
Does not honor H.264 YUV coefficient flag
Status: RESOLVED DUPLICATE of bug 750882
Product: GStreamer
Classification: Platform
Component: gst-libav
1.6.1
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 757604 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-11-04 18:58 UTC by Steinar H. Gunderson
Modified: 2018-01-13 12:46 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Encoded with BT.709 YUV coefficients (1.03 MB, video/mpeg)
2015-11-04 18:59 UTC, Steinar H. Gunderson 		Details

Description Steinar H. Gunderson 2015-11-04 18:58:51 UTC 
Hi,

The attached two video files should decode near-identically to each other and to http://www.imagescience.com.au/kb/images/BeEyeCalibrationImages/colourWedges.jpg.  (They are encoded with different YUV coefficients, and no other real differences.) They don't; in Iceweasel the BT.601 is right but the BT.709 is washed out (the brightest greens are all 255), while in gst-play-1.0, the BT.601 is too dull (G=233 at the brightest or so) and the other colors contaminated (e.g. the brightest red has B=15).
Comment 1 Steinar H. Gunderson 2015-11-04 18:59:26 UTC 
Created attachment 314851 [details]
Encoded with BT.709 YUV coefficients
Comment 2 Steinar H. Gunderson 2015-11-04 19:00:26 UTC 
It seems I cannot attach the BT.601 sample. You can find it at http://storage.sesse.net/test-bt601.ts.
Comment 3 Sebastian Dröge (slomo) 2015-11-04 19:09:16 UTC 
*** Bug 757604 has been marked as a duplicate of this bug. ***
Comment 4 Nicolas Dufresne (ndufresne) 2015-11-04 21:06:27 UTC 
Colorimetry is not implemented iirc in gst-ffmpeg.
Comment 5 Tim-Philipp Müller 2018-01-13 12:46:02 UTC 
This seems to work now.

*** This bug has been marked as a duplicate of bug 750882 ***