From c7b175d8cbc7831d25a083b7eb7916c89b52b9e1 Mon Sep 17 00:00:00 2001 From: Derek Foreman Date: Fri, 13 Oct 2023 16:41:55 -0500 Subject: [PATCH] presentation-time: Only use CLOCK_MONOTONIC from now on More protocols are under discussion that require the use of timestamps in the domain of the presentation clock. It's easier to just force everyone to use the same clock, CLOCK_MONOTONIC, so we don't have to have multiple protocols all sending events to communicate the same information. Signed-off-by: Derek Foreman --- stable/presentation-time/presentation-time.xml | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/stable/presentation-time/presentation-time.xml b/stable/presentation-time/presentation-time.xml index 04301ff..62bd2c8 100644 --- a/stable/presentation-time/presentation-time.xml +++ b/stable/presentation-time/presentation-time.xml @@ -25,7 +25,7 @@ DEALINGS IN THE SOFTWARE. - + @@ -33,8 +33,10 @@ The main feature of this interface is accurate presentation timing feedback to ensure smooth video playback while maintaining audio/video synchronization. Some features use the concept of a - presentation clock, which is defined in the - presentation.clock_id event. + presentation clock, which was defined in the + presentation.clock_id event. As of version 2 of this protocol, + presentation.clock_id is no longer sent, and the presentation + clock is always CLOCK_MONOTONIC. A content update for a wl_surface is submitted by a wl_surface.commit request. Request 'feedback' associates with @@ -118,6 +120,9 @@ irrelevant. Precision of one millisecond or better is recommended. Clients must be able to query the current clock value directly, not by asking the compositor. + + NOTE: As of version 2, this event is no longer sent, and + the presentation clock is always CLOCK_MONOTONIC.