Re: [webrtc-insertable-streams] How to handle transforms largely changing frame size (#50)

One good example there might be RED (https://tools.ietf.org/html/rfc2198).
IIUIC, it is integrated as a codec similarly to Opus, the transform being applied on the result of the RED encoder. 

RED encoder is using an underlying encoder (say Opus) to compress data.
It will then generate content by taking this compressed data and by appending previously encoded data to it until a byte limit is reached. Ideally, the content will be serialised as one packet.

If the transform increases the size of the content by too much, things might actually break.

-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/webrtc-insertable-streams/issues/50#issuecomment-771649542 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 2 February 2021 13:53:37 UTC