WebRTC shows that H264 not supported

1,341 views
Skip to first unread message

Andriy Buchynskyy

unread,
Oct 30, 2018, 6:06:13 AM10/30/18
to discuss-webrtc
Hello. I have problem with H264 codec. I can't set remote sdp because I have failure. 
As far as I understand from logs it's not supported. But I don't understand why. 

[000:517] [5422] (webrtcvideoengine.cc:609): SetSendParameters: {codecs: [VideoCodec[97:H264]], extensions: [{uri: urn:ietf:params:rtp-hdrext:sdes:mid, id: 3}, {uri: http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time, id: 4}, {uri: urn:ietf:params:rtp-hdrext:toffset, id: 5}], max_bandwidth_bps: -1, }
[000:517] [5422] (webrtcvideoengine.cc:446): Internally supported codecs: {VideoCodec[0:VP8], VideoCodec[0:red], VideoCodec[0:ulpfec]}
[000:517] [5422] (webrtcvideoengine.cc:553): No video codecs supported.
[000:517] [5423] (channel.cc:853): Failure in SetRemoteContent with action 0

If I'm using VP8 everything works fine. Do you have any ideas how I can fix it? 
Thank you

Alexandre GOUAILLARD

unread,
Oct 30, 2018, 8:59:28 PM10/30/18
to discuss...@googlegroups.com
is it a trace from a browser, or from webrtc "standalone"?
if it's the later, you might have copied it with the default flags which do NOT include H264 support

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/64537aca-437d-45e1-8d59-e527d0ab838b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
Alex. Gouaillard, PhD, PhD, MBA
------------------------------------------------------------------------------------
President - CoSMo Software Consulting, Singapore
------------------------------------------------------------------------------------

Andriy Buchynskyy

unread,
Oct 31, 2018, 5:32:28 AM10/31/18
to discuss-webrtc
Thank you for your reply. These logs are from native webrtc code. 
I made application where browser is client side and native webrtc 
is server side. I receive logs from server side - native webrtc.  

Alexandre GOUAILLARD

unread,
Oct 31, 2018, 9:57:43 PM10/31/18
to discuss...@googlegroups.com
did you compile your native webrtc code with support for H264? it s OFF by default.


For more options, visit https://groups.google.com/d/optout.

Mohd Yusuf Siddiqui

unread,
Oct 31, 2018, 10:22:43 PM10/31/18
to discuss...@googlegroups.com
Try to enable H264 in the code,by default its VP8. IF you still face quality issue ,use VOIP engine in between.

Regards
Yusuf Siddiqui

李晓帆

unread,
Nov 1, 2018, 2:57:06 AM11/1/18
to discuss...@googlegroups.com
enable openh264 by set 'rtc_use_h264 = true ffmpeg_branding = "Chrome" ', after this you need modify  third_party/ffmpeg/chromium/config/Chrome/android/arm-neon/libavcodec/parser_list.c and third_party/ffmpeg//chromium/config/Chrome/android/arm-neon/libavcodec/codec_list.c files, add h264 parse, like:

--- a/chromium/config/Chrome/android/arm-neon/libavcodec/parser_list.c
+++ b/chromium/config/Chrome/android/arm-neon/libavcodec/parser_list.c
@@ -4,4 +4,5 @@ static const AVCodecParser * const parser_list[] = {
     &ff_mpegaudio_parser,
     &ff_opus_parser,
     &ff_vorbis_parser,
+    &ff_h264_parser,
     NULL };

--- a/chromium/config/Chrome/android/arm-neon/libavcodec/codec_list.c
+++ b/chromium/config/Chrome/android/arm-neon/libavcodec/codec_list.c
@@ -13,4 +13,5 @@ static const AVCodec * const codec_list[] = {
     &ff_pcm_s32le_decoder,
     &ff_pcm_u8_decoder,
     &ff_libopus_decoder,
+    &ff_h264_decoder,
     NULL };


This worked for me at M67 release

Mohd Yusuf Siddiqui <jose...@gmail.com> 于2018年11月1日周四 上午10:22写道:

Andriy Buchynskyy

unread,
Nov 2, 2018, 3:47:29 AM11/2/18
to discuss...@googlegroups.com

Chen Yang

unread,
Nov 27, 2018, 3:34:36 AM11/27/18
to discuss-webrtc
Hi, i want to open h264 support in M70 release. And i use the arguments like you do, 'rtc_use_h264 = true ffmpeg_branding = "Chrome" '.
But when i build my project, these error log show up.
Could you please take a look?

在 2018年11月1日星期四 UTC+8下午2:57:06,Wesley写道:
error.log

Wesley(晓帆)

unread,
May 25, 2019, 4:04:37 AM5/25/19
to discuss-webrtc
Hi
I don't known why this mail was not appeared in my inbox, maybe this reply was too late...
According your log, maybe you need pay attention to third_party/ffmpeg/ffmpeg_generated.gni file, it was not support x86 platform by default

在 2018年11月27日星期二 UTC+8下午4:34:36,Chen Yang写道:
Reply all
Reply to author
Forward
0 new messages