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

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

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Thu, 19 May 2022 14:41:28 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.closed-1116393558-1652971283-sysbot+gh@w3.org>

alvestrand closed this issue. See https://github.com/w3c/webrtc-encoded-transform/issues/128

-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 19 May 2022 14:41:30 UTC

This message: [ Message body ]
Next message: youennf via GitHub: "[webrtc-encoded-transform] Change generateKeyFrame return value from unsigned long long to unsigned long (#133)"
Previous message: Elad Alon via GitHub: "Re: [mediacapture-region] Why expose produceCropTarget at MediaDevices level? (#11)"
In reply to: [ message archived in another list or period ]

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

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