W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2022

[webrtc-encoded-transform] Is "empty" value of RTCEncodedVideoFrameType useful? (#156)

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Mon, 03 Oct 2022 08:10:32 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-1394322526-1664784631-sysbot+gh@w3.org>
youennf has just created a new issue for https://github.com/w3c/webrtc-encoded-transform:

== Is "empty" value of RTCEncodedVideoFrameType useful? ==
"empty" is part of RTCEncodedVideoFrameType but not part of EncodedVideoChunkType.
As spotted in https://github.com/w3c/webrtc-encoded-transform/pull/155#discussion_r985478345, it is in use by Chrome to indicate the frame was enqueued. This is not in use by Safari AFAIK.
I can see two options:
1. Remove "empty", make RTCEncodedVideoFrame.type immutable. Replace RTCEncodedVideoFrameType by EncodedVideoChunkType.
2. Describe that RTCEncodedVideoFrame.type changes to "empty" when being enqueued (like we are adding the transfer rules for data).

Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/156 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 3 October 2022 08:10:34 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:59 UTC