Bug ID 1216393
Summary Electron/Chromium can't render h264 in webrtc
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware All
OS openSUSE Tumbleweed
Status NEW
Severity Normal
Priority P5 - None
Component Other
Assignee screening-team-bugs@suse.de
Reporter bjorn.bidar@thaodan.de
QA Contact qa-bugs@suse.de
Target Milestone ---
Found By ---
Blocker ---

*  Description:

When trying to stream WebRTC with h264 in Electron/Chromium the screen stays
black even thou OpenH264 is correctly installed.

* How to reproduce:
1. Open Chromium
2. Open  https://mozilla.github.io/webrtc-landing/pc_test_no_h264.html
3. Click test

** Another option is to use:
https://mozilla.github.io/webrtc-landing/pc_test.html
1. Tick require h264
2. Start the video, wait
3. The message now should be "No H264 found in the offer!!!"  


* Background and reason for the bug:

openSUSE builds both Chromium and Electron in a way  that h264 isn't compiled
into both packages
but loaded using the Openh264 provided by openSUSE but blessed by Cisco.

However Chromium has to use some of the openh264 to build even thou it's not
used during runtime.

The gyp option `rtc_use_h264` has be set to true and third_party/openh264 has
to 
be included in the tarball (already the case in the upstream
third_party/openh264 tarball).

This is due webrtc using openh264 headers in
third_party/webrtc/modules/video_coding/codecs/h264/h264_encoder_impl.cc


You are receiving this mail because: