- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Jul 2022 13:45:48 +0000
- To: public-webrtc@w3.org
fippo has just created a new issue for https://github.com/w3c/webrtc-encoded-transform: == width/height metadata on incoming streams == The video frame metadata come with width and height: https://w3c.github.io/webrtc-encoded-transform/#dom-rtcencodedvideoframemetadata-width For outgoing streams this makes some sense since it is easily known (but it isn't clear to me what the use-case is), for incoming streams this requires pre-parsing the VPx payload descriptor, the H264 SPS (or PPS?) and the AV1 sequence header OBU. Is anyone relying on this behavior? Note that it already doesn't work for AV1 so the values are 0/0 and I heard a "we would like to move away from parsing bitstreams" [here](https://bugs.chromium.org/p/webrtc/issues/detail?id=14251) that I agree with. While I don't think we can change this to be optional depending on the direction, we can at least consistently set width/height to 0 on incoming streams. Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/138 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 18 July 2022 13:45:50 UTC