- From: Philipel-WebRTC via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Oct 2023 14:12:42 +0000
- To: public-webrtc-logs@w3.org
It could be that I fundamentally misunderstand the goal of this proposal, but AFAICT the goal is to enable custom codecs to be negotiated via SDP, or am I wrong? As soon as we negotiate a non-standardized codec name then we don't have any standardized packetizer to rely on, and I get that the proposed API would allow the sender and receiver to map the payload type of a custom codec to some other know (de)packetizer, but to me that seems very limiting and complex. The way it is proposed right now, would we expect anyone to every use a packetizer other than VP9 (the only one that separates descriptor and bitstream data cleanly in the payload) for a custom codec? Again, this to me looks a bit more than the abuse side of things than a general solution (again, assuming I understand the goal of this PR). -- GitHub Notification of comment by Philipel-WebRTC Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/186#issuecomment-1755511887 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 October 2023 14:12:44 UTC