- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Feb 2021 10:53:09 +0000
- To: public-webrtc-logs@w3.org
Correct, the audio RED encoder is wrapping the opus one, stores a packet (or two, three, four, ...) and then essentially concatenates them. Since audio typically isn't split into multiple packets that could create a problem with insertable streams but I think we have a lot of margin here. The audio encoder does know the transport overhead which is calculated from RTP header size or RTP header extensions currently (see [here for details](https://source.chromium.org/chromium/chromium/src/+/master:third_party/webrtc/api/audio_codecs/audio_encoder.h;l=231;drc=8ffe0a431f557f8f0b99820374fd9cfddab4af53;bpv=1;bpt=1)) -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-insertable-streams/issues/50#issuecomment-772418034 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 February 2021 10:53:12 UTC