- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Oct 2023 20:49:59 +0000
- To: public-webrtc-logs@w3.org
Trying to piece together Jan-Ivar's suggested changes one at a time:
Jan-Ivar said:
>I disagree with this conclusion. I think transforms become entangled with a sender or receiver on assignment and >aren't really reusable or agnostic https://github.com/w3c/webrtc-encoded-transform/issues/209.
>
>I think we can leverage this to simplify the API. Pardon my ignorance if I miss something, but given a codec:
>
>const codec = {
> mimeType: "video/vp8-encrypted",
> clockRate: 90000,
> fmtp: "encapsulated-codec=vp8",
>};
I don't think we can reuse the "fmtp" parameter - that's stuff that has external meaning.
So we'd have to go back to my previous proposal of adding a "packetizer" attribute (or some other parameter with other meaning), which was agreed to be dropped in Seville.
But I'm not clear about what semantics you would want to attach to this extra parameter.
--
GitHub Notification of comment by alvestrand
Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/186#issuecomment-1767156979 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 17 October 2023 20:50:01 UTC