- From: Tony Herre via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Jan 2024 10:39:17 +0000
- To: public-webrtc@w3.org
tonyherre has just created a new issue for https://github.com/w3c/webrtc-encoded-transform: == Is RTCEncodedVideoFrameMetadata.frame_id actually an unsigned long long of does it wrap at 16 bits? == [frame_id](https://w3c.github.io/webrtc-encoded-transform/#RTCEncodedVideoFrameMetadata) is defined as a `unsigned long long`, but currently doesn't have any textual definition in the [members](https://w3c.github.io/webrtc-encoded-transform/#RTCEncodedVideoFrameMetadata-members) section beneath. Same for dependencies. My rough understanding is that it corresponds to the [Dependency Descriptor Header Extension](https://aomediacodec.github.io/av1-rtp-spec/#dependency-descriptor-rtp-header-extension)'s frame_number field as a codec-agnostic frame numbering method, but that field is only 16 bits, so is the UA assumed to be handling the 16 bit wrapping and converting up to a 64 bit `unsigned long long`? That's the current Chromium implementation at least. I'm unsure of other browsers. Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/220 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 5 January 2024 10:39:19 UTC