Ben, you are correct, its a flag issue. I compiled CEF (based on Chromium), branch 3359 (Chrome 66) and I used: rtc_use_h264 = true and I have h264 support. Without that, using the regular: GN_DEFINES=is_official_build=true ffmpeg_branding=Chrome proprietary_codecs=true It did not work.
Maybe the check for is_chrome_branded is bad and it always return false... or maybe the above GN defines are not properly setting it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1763662 Title: H264 missing from WebRTC (regression) Status in chromium-browser package in Ubuntu: Confirmed Bug description: H264 is missing from WebRTC in Chromium 65.0.3325.181. This is a regression. It worked in Chromium 64.0.3282.167. According to the webrtc team it might be because of a missing flag . Steps to reproduce: 1. Install Chromium on Ubuntu 16.04: sudo apt-get install -y chromium-browser chromium-codecs-ffmpeg-extra 2. open a tab with chrome://webrtc-internals 3. Create a room in https://appr.tc and join the room. 3. Check the SDP offer in webrtc-internals. Select the https://appr.tc/r/<room-id> tab and click on the createOfferOnSuccess event. We should have H264 in the SDP offer but it's missing: a=rtpmap:100 H264/90000  https://bugs.chromium.org/p/webrtc/issues/detail?id=9096 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1763662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : firstname.lastname@example.org Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp