Black screen with Mediacodec H264

If the first packet sent by a stream using Mediacodec H264 (Acceleration Android) is not received, the stream is corrupted

log

changed milestone to %Iteration 19

changed the description

added media label

changed milestone to %Itération 20

changed milestone to %Itération 21

changed title from HW Acceleration cuda doesn't work properly when attaching a participant to a conference to Black screen with Mediacodec H264

changed the description

assigned to @mchibani1

The issue seems to be caused by the fact that the SPS/PPS NALs are generated and sent only once on Android H264 MediaCodec is used. So, if the SPS/PPS NALs are lost, or the decoder is not up and running when the SPS/PPS NALs are received, the decoder will never be able to decode the H264 stream. The chromium project has addressed this issue and a patch was provided here: https://chromium-review.googlesource.com/c/chromium/src/+/710454

MediaCodec integration was patched in order to send SPS/PPS with each key-frame (IDR).

While testing this patch, it was observed that if the vide demuxer fails to find the codec data at the beginning of the stream, the decoding session will not be correctly set up even if the codec data are later received in the stream. Fixing the bug requires modification of the video decoding call flow, thus it will not be addressed in this issue.

The patch can be found here: https://review.jami.net/c/ring-client-android/+/15292

added SprintIn progress label

added SprintTo review label and removed SprintIn progress label

changed milestone to %Itération 21

closed

removed SprintTo review label