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

Re: [webrtc-encoded-transform] Should we expose the precise timestamp of the frame that was triggered by a generateKeyFrame call? (#128)

From: youennf via GitHub <sysbot+gh@w3.org>
Date: Wed, 02 Feb 2022 10:39:28 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1027801319-1643798366-sysbot+gh@w3.org> 
Proposal:
- Make generateKeyFrame take an optional rid instead of a sequence. If none is provided, the first rid is used if any.
- Keep resolving the promise as we do on the first key frame matching the generateKeyFrame rid.
- Make generateKeyFrame promise value be the timestamp (or the frameId if it less ambiguous with regards to rids) of the frame that triggered the promise resolution.

-- 
GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/128#issuecomment-1027801319 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 February 2022 10:39:30 UTC

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