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

Issue 598107 link

Starred by 2 users
Status: WontFix
Owner:
█ lionel.g...@intel.com
Last visit > 30 days ago
Closed: Apr 2016
Cc:
█ servolk@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

GetVpxCodecParameters needs adjustment for different VP9 profiles

Project Member Reported by servolk@chromium.org, Mar 25 2016 
Previously we didn't distinguish between different VP9 profile in Chromium media stack, but that is about to change (see crbug.com/592074). So at the moment GetVpxCodecParameters is using identical quantizer and cpu_used values for all VP9 profiles, but after https://codereview.chromium.org/1769593002 lands those numbers could be fine-tuned for each VP9 profile.

Comment 1 by lionel.g...@intel.com, Apr 4 2016 

It seems you've made changes to your CL, removing modifications to the Pepper APIs. Is this still relevant?

Comment 2 by servolk@chromium.org, Apr 4 2016 

Right, after most recent changes to that CL we only support VP9 profile 0 through PPAPI for now, so this issue is not relevant atm, so I'll close it for now. We might want to revisit it later, once we start supporting other VP9 profiles through PPAPI.

Comment 3 by servolk@chromium.org, Apr 4 2016

Status: WontFix (was: Available)
►

Sign in to add a comment