Webrtc library does not support HiSilicon codec

460 views
Skip to first unread message

test test

unread,
Mar 18, 2019, 11:08:12 PM3/18/19
to discuss-webrtc

PHONE

- Version of Android: Android p:

- Phone used and Build: Huawei Mate10/P20/Mate20(Android P)

- Chipset: Kirin970/Kirin980

 

Issue Description

Instagram to join the interactive live button is grayed out and can't click to join and the anchor can't invite viewers to join the interactive live video.

 

STEPS TO REPRODUCE: (please be specific)

1. The auxiliary machine opens the instagram and opens the interactive live video.

2. The test machine enters the live video

3. Observe the interactive live button change

 

REPRODUCE RATE:

10 times out of 10 tries

 

EXPECTED RESULTS:

Join the interactive live button will always be on, you can enter the interactive live video at any time.

 

OBSERVED RESULTS:

After entering the live room, the button will be automatically grayed out after three seconds, click to enter the interactive live video

 

PIXEL: normal

 

ANALYSIS:

Facebook reply is as follows:

This was caused by the lack of support for OMX.hisi hardware codec in MediaCodecVideoDecoder,which is a open source lib mainly supported by Google Chrome team.I have been reached out by the Huawei team who are working on OMX.hisi hardware codec.And I have told them to reach out to WebRTC team to add the support of OMX.hisi. After that we will merge the change to our apps.But we need your support on test at that time.Closing this task here.Will continue the conversation with Huawei hardware codec team.

 


contact info:

wud...@huawei.com

njut...@gmail.com

unread,
Mar 25, 2019, 2:46:40 AM3/25/19
to discuss-webrtc
I also encountered this problem。

log:
03-25 11:30:45.686 22145-22323 I/MediaCodecVideoEncoder: Java initEncode: VIDEO_CODEC_H264. Profile: 0 : 320 x 240. @ 30 kbps. Fps: 60. Encode from texture : true
03-25 11:30:45.705 22145-22323 I/MediaCodecVideoEncoder: Found target encoder for mime video/avc : OMX.hisi.video.encoder.avc. Color: 0x7f000789. Bitrate adjustment: NO_ADJUSTMENT
03-25 11:30:45.705 22145-22323 I/MediaCodecVideoEncoder: Color format: 2130708361. Bitrate adjustment: NO_ADJUSTMENT. Key frame interval: 0 . Initial fps: 30
03-25 11:30:45.705 22145-22323 I/MediaCodecVideoEncoder:   Format: {frame-rate=30, bitrate-mode=2, height=240, color-format=2130708361, width=320, bitrate=30000, mime=video/avc, i-frame-interval=20}
03-25 11:30:45.729 22145-22323 E/MediaCodecVideoEncoder: initEncode failed
03-25 11:30:45.729 22145-22323 E/MediaCodecVideoEncoder: java.lang.IllegalStateException: start failed
03-25 11:30:45.730 22145-22323 E/MediaCodecVideoEncoder: java.lang.IllegalStateException: start failed
        at android.media.MediaCodec.start(Native Method)
        at org.webrtc.MediaCodecVideoEncoder.initEncode(MediaCodecVideoEncoder.java:672)
        at dalvik.system.NativeStart.run(Native Method)
        at dalvik.system.NativeStart.run(Native Method)
03-25 11:30:45.730 22145-22323 I/MediaCodecVideoEncoder: Java releaseEncoder
03-25 11:30:45.732 22145-25151 I/MediaCodecVideoEncoder: Java releaseEncoder on release thread
03-25 11:30:45.742 22145-25151 I/MediaCodecVideoEncoder: Java releaseEncoder on release thread done


I found that  some resolution like "640*480, 320*240" will crash,and they aspect ratio are "4:3"。


在 2019年3月19日星期二 UTC+8上午11:08:12,test test写道:
Reply all
Reply to author
Forward
0 new messages