Re: [webrtc-extensions] Suggest API for generating a Stream rather than a MediaStreamTrack from incoming media (#85)

In this mode, Stream object Reader should be responsible initial and subsequent for codec re-negotiation. So, Reader should get the offer description from the Stream and provide the answer. The Reader should also have an interface to handle re-negotiation.

Also, how would this deal with lip-sync across multiple tracks? You need a way to specify that several decoders are grouped. This can be a decoder implementation detail, but the Stream object should reference other related streams.

Finally, would it be possible to only use the new interface on some of the tracks, such as custom decoder for audio and browser decoder for video? Would we need to expose browser-level decoders so that it would be possible to implement the lip sync?

-- 
GitHub Notification of comment by rshpount
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/85#issuecomment-942550190 using your GitHub account


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

Received on Wednesday, 13 October 2021 17:27:37 UTC