- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Dec 2023 18:00:40 +0000
- To: public-webrtc-logs@w3.org
> I am not sure of the existing API shape, reusing RTCRtpEncodedVideoFrame might be too much (setting PT for instance could be tedious to web developers for instance). It is not always necessary to set PT. For the forwarding use case, you start with a received frame that already has full metadata, including PT. You just need to update some of the metadata for the output frame. For forwarding updating frame ID, dependencies, and rtpTimestamp should probably be enough. I'm fine with producing the output frame with a constructor that takes the original frame and a metadata object with the fields to update. We can iterate on the surface. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/211#issuecomment-1843399684 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 December 2023 18:00:42 UTC