- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Jun 2022 16:12:19 +0000
- To: public-webrtc-logs@w3.org
To sketch this API, we need to identify many use cases, especially if we go with setMetadata. Going with a dedicated csrc/ssrc mutator might be easier to sell if the specific use case is convincing. As of sync vs. async, if we have to hop to threads, we usually go async. But I think we should first look at the actual model. It seems to me the natural model is that the metadata is only used after the frame is enqueued: at the time of enqueueing the frame, we clone the metadata and this gets used down the pipe. This seems to call for a sync API. The question of bad metadata is something to take into account. We should also learn from WebCodec decoders and metadata approach. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/135#issuecomment-1161966310 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 June 2022 16:12:20 UTC