Issue metadata
Sign in to add a comment
|
Choosing video codec does not work between Chrome and Firefox on apprtc |
||||||||||||||||||||||
Issue descriptionAt apprtc.appspot.com, using the ?vsc=X&vrc=X parameters when joining a room - where X is a codec (VP8, VP9, H264) - does not seem to be working between Chrome and Firefox, but it works between two Chrome tabs or ?debug=loopback. When not working it uses the default codec VP8 as if it was ignoring the parameters. I've tested both manually and with this interop test: https://codereview.chromium.org/2013803002/. AppRTC works by modifying the SDP so that the desired codec is first in the list of codecs in the m=video line. We should see the same problem at https://webrtc.github.io/samples/src/content/peerconnection/munge-sdp/ if we modify the SDP manually, but I haven't tried that. I believe interop with Firefox and choosing codec was working earlier when I and hta was working on this weeks ago.
,
May 27 2016
,
May 27 2016
Semi-aggressively tagging this with the M52 label because this may be a recently introduced regression. Feel free to adjust if I'm misinterpreting this line in the original report: "I believe interop with Firefox and choosing codec was working earlier when I and hta was working on this weeks ago."
,
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 3 2016
I just tried Chrome 52.0.2743.17 and Firefox 46.0.1 and H264 works fine. Used url: https://appr.tc/vsc=H264
,
Jun 3 2016
I also enabled chrome://flags/#enable-webrtc-h264-with-openh264-ffmpeg
,
Jun 3 2016
pbos@ pointed out that I do not need to enable a flag on M52, I just retested and it is indeed so, it works fine without the flag explicitly enabled. Closing as not reproducible.
,
Jun 3 2016
Not sure why it wasn't working before (or if I did something wrong), but I've confirmed that it does indeed work now. It does not matter if Chrome or Firefox is the one to join the room first, both works. The interop test CL though is not working, but that's a separate issue.
,
Jun 10 2016
Update: Testing manually, Chrome-Firefox interop works with VP8 and (if compiled and enabled in Chrome) H264, but *not* VP9. Chrome-Chrome works with all three codecs. (My confusion with thinking it worked or didn't work at different times must have been due to testing with VP9 or H264, not realizing VP9 wasn't working.) Separate related issue: In the browser_tests CL (https://codereview.chromium.org/2013803002/) something is causing nothing but VP8 to work.
,
Jun 10 2016
If we want to test Chrome-Firefox interoperability with VP9 we could do that separately, but I believe VP9 might not be supported in Firefox and that is why this doesn't work? I filed a separate issue for Chrome-Firefox H264 interop browser_tests: https://bugs.chromium.org/p/chromium/issues/detail?id=618965. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by hbos@chromium.org
, May 27 2016