[H264] Apprtc peer2peer call with H264 is falling back to VP9 on CrOS |
|||||||||||||||
Issue descriptionChrome Version: 52.0.2743.0 / 8350.2.0 dev Device: Wolf What steps will reproduce the problem? (1) Join a two-way apprtc call from device Wolf and desktop(Linux) using https://appr.tc/r/roomname?vsc=h264 (2) After joining the call, press "i" and observe that video sending codec is VP9 ("Video Tx": VP9) Expected result: Apprtc call should be connected with h264 support ("Video Tx": H264) Actual result: Apprtc call is connected with VP9 ("Video Tx": VP9) Notes: 1.All values in chrome://flags are set to default and flag "WebRTC H.264 software video encoder/decoder" is set to default 2. Feedback submitted for this issue: https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=user:srcv&lReport=9278291920 3. Chrome://histograms/Media.RTc shows no entries after apprtc calls
,
May 27 2016
I think you have to use "vrc" rather than "vsc", or "vsc" on the ChromeOS side and "vsr" on the linux side.
,
May 27 2016
-> srcv@ per #2 to try again.
,
May 27 2016
jansson@: Started apprtc calls as suggested: a)Test results with "vrc" on Chrome OS and no parameters on Linux - Sending video codec = VP9 - Receiving video codec = VP8 b) Test results for "vsc" on Chrome OS and "vsr" on linux - Sending video codec = VP9 - Receiving video codec = VP9 https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/615265/
,
May 27 2016
What did you set vsc and vrc to?
,
May 27 2016
I have set vsc and vrc to h264 on CrOS. a) CrOS: https://appr.tc/r/roomname?vrc=h264 Linux: https://appr.tc/r/roomname Sending video codec = VP9 Receiving video codec = VP8 b) CrOS: https://appr.tc/r/roomname?vsc=h264 Linux: https://appr.tc/r/roomname?vsr=h264 on Linux Sending video codec = VP9 Receiving video codec = VP9
,
May 30 2016
I just tried setting VP8 using only the vsc parameter and it works fine which means this should work with H264 as well. On CrOS, is H264 enabled by default in Chrome? I ask because AppRTC modifies the SDP but only if the codec is found, so unless H264 is present in the localDescription SDP it won't work.
,
May 31 2016
> On CrOS, is H264 enabled by default in Chrome? With M52, H.264 should be available by default in ChromeOS.
,
May 31 2016
jansson@: vsc=vp8 is working on all chrome devices but vsc=h264 is working on only some of the devices. This issue is so far seen on devices Wolf, Paine, Samus and Swanky
,
Jun 1 2016
Could you compare the localDescription on the CrOS devices that work and do not work? Then also copy the localDescription in this bug.
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 1 2016
Apprtc peer2peer call with H264 is falling back to VP9 on all the following chrome devices : Peppy, Daisy, Candy, Kip, Pit, Wolf, Paine, Samus , Swanky and Big Tested apprtc peer2peer calls with : CrOS: https://appr.tc/r/roomname/?vsc=h264 Linux: https://appr.tc/r/roomname?vsr=h264 Note: I will update this bug if I find any chrome device that works with H264 for Apprtc Peer2peer calls (no such chrome device has been found so far)
,
Jun 1 2016
srcv@, you have been testing H264 from the munge SDP app for earlier releases, right? Is this a regression for that case?
,
Jun 2 2016
,
Jun 2 2016
,
Jun 2 2016
srcv@ could you copy the localDescription of a device where h264 works and also from a device it does not work and paste it in this bug?
,
Jun 2 2016
You can do this from webrtc-internals.
,
Jun 3 2016
In comment #13, Linux: https://appr.tc/r/roomname?vsr=h264 should be Linux: https://appr.tc/r/roomname?vsc=h264. (vsc = send codec, vrc = receive codec).
,
Jun 3 2016
jansson@: None of the chrome devices have worked on M52 with H264 in Apprtc Peer2peer calls. I was mistaken initially that it worked on few devices but later retested them and confirmed that apprtc peer2peer calls with H264 are falling back to VP9 on all the chrome devices. Retested with : CrOS: https://appr.tc/r/roomname/?vsc=h264 Linux: https://appr.tc/r/roomname?vsc=h264
,
Jun 8 2016
[triage]: Ok, do we have agreement this is a bug? What's the next step?
,
Jun 8 2016
I want to see the localDescription on said devices and see if H264 is present on said devices. I've requested this in #17 and in a separate email.
,
Jun 8 2016
jansson@: Please find attached localDescription from device Jerry where H264 in AppRTC peer2peer call is falling back to VP9. As mentioned in comment#20, all the devices tested so far for M52 have this issue.
,
Jun 10 2016
It looks like H264 is filtered out in the answer for some reason. Not sure why this is. Will take a deeper look.
,
Jun 10 2016
,
Jun 20 2016
Re-tested AppRTC peer2peer calls with H264 between two Chrome devices having M52 builds. AppRTC peer2peer call is established via H264 video codec. URLs used: https://appr.tc/r/roomname?vsc=h264 (CrOS) https://appr.tc/r/roomname (Linux) (Verified that sending video codec on chrome device is H264 and receiving video codec is VP9 ) WebRTC internal dump from AppRTC peer2peer between Chrome devices Big and Peppy with M52 builds: https://pantheon.corp.google.com/storage/browser/chromiumos-test-logs/bugfiles/cr/615265/2way_apprtc_working_on_H264_CrOS/?pli=1 Note: This issue was initially filed based on the test results from AppRTC peer2peer calls between Chrome device having M52 build and Linux desktop having M51 stable build. H264 is supported only between devices having M52 or greater builds. Closing this issue as "wont Fix" |
|||||||||||||||
►
Sign in to add a comment |
|||||||||||||||
Comment 1 by srcv@chromium.org
, May 26 2016