New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 649758 link

Starred by 2 users
Status: Fixed
Owner:
█ servolk@chromium.org
Last visit > 30 days ago
Closed: Sep 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Find a way to transfer gfx::ColorSpace info into Chromecast VideoConfig

Project Member Reported by servolk@chromium.org, Sep 23 2016 
My proposal to add getters for gfx::ColorSpace components has stalled for now, since gfx folks don't think having gettering in ColorSpace is a good idea (see https://codereview.chromium.org/2349923002/).
So we might need to find another way to get color space info from Chromium's VideoDecoderConfig into Chromecast VideoConfig (or convince gfx folks that having getters is the right thing to do).
Project Member

Comment 1 by sheriffbot@chromium.org, Sep 25 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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

Comment 2 by servolk@chromium.org, Sep 25 2017

Status: Fixed (was: Untriaged)
This is fixed, now that VideoDecoderConfig uses media::VideoColorSpace instead of gfx::ColorSpace. The media::VideoColorSpace struct allows access to individual color space parameters.
►

Sign in to add a comment