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

Issue 666868 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
emir...@chromium.org
kcwu@chromium.org
posciak@chromium.org
█ phoglund@chromium.org
hsiangc@chromium.org
vsu...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

WebRTC: Media.RTCVideoEncoderProfile is not generating 1 bucket for h264 loopback

Project Member Reported by avkodipelli@chromium.org, Nov 18 2016 
Chrome Version: 56.0.2923.0
Chrome OS Version: 9000.0.0
Chrome OS Platform: pit, elm , buddy
Network info: Wifi

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Open apprtc.appspot.com/?debug=loopback&vsc=h264
(2) Observe loopback video
(3) Open another tab and run histogram , chrome://histograms/Media.R
(4) Observe Media.RTCVideoEncoderProfile bucket values

Expected Result:
As per https://sites.google.com/a/google.com/chromeos-video/video-histograms-and-flags, it should be 1 bucket 

Actual Result:
but observing 0 bucket 

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.
Screenshot added in next comment

Comment 2 by wuchengli@chromium.org, Nov 21 2016

Cc: emir...@chromium.org phoglund@chromium.org kcwu@chromium.org
Labels: videoshortlist
Owner: avkodipelli@chromium.org
Status: Assigned (was: Untriaged)
avkodipelli@ Please always get a bugreport (generate_logs or feedback).

Kuang-che. Is this a known issue?

Comment 4 by posciak@chromium.org, Nov 21 2016

Owner: magjed@chromium.org
This seems to be due to crrev.com/5cc479a2c0d7ba8de9f08948be37d8b323625865, as we now report baseline profile (=0) always. Assigning to magjed@ who is working on http://crbug/webrtc/6337.

For now, 0 or 1 should be considered as passing, as long as Media.RTCVideoEncoderInitEncodeSuccess is 1.

Comment 5 by posciak@chromium.org, Nov 21 2016

Labels: -videoshortlist

Comment 6 by magjed@chromium.org, Nov 21 2016 

I am sure this is not caused by crrev.com/5cc479a2c0d7ba8de9f08948be37d8b323625865. As I have explained in the CL, webrtc::kProfileMain has never been used ever. I have even removed that enum from the WebRTC code base and this has not caused any external compile failures. The cricket::WebRtcVideoEncoderFactory::VideoCodec you have been reporting to WebRTC from RTCVideoEncoderFactory does not contain any profile information at all. It just contains the string "H264" so this issue must have existed for H264 since it was added.

That said, maybe https://codereview.chromium.org/2499973002/ has already fixed this issue?

Comment 7 by avkodipelli@chromium.org, Nov 21 2016 

Feedback report ID from daisy : 16998740293

Comment 8 by avkodipelli@chromium.org, Nov 30 2016 

Still issue seen on 9000.11.0, 56.0.2924.11 on paine device.

Comment 9 by magjed@chromium.org, Sep 29 2017

Owner: ----
Status: Available (was: Assigned)

Comment 10 by vsu...@google.com, Sep 29 2017

Cc: -rohi...@chromium.org
Project Member

Comment 11 by sheriffbot@chromium.org, Oct 1

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.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment