BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//CERN//INDICO//EN
BEGIN:VEVENT
SUMMARY:Introducing the Wayland Content Frame Rate Protocol
DTSTART;VALUE=DATE-TIME:20260930T203000Z
DTEND;VALUE=DATE-TIME:20260930T203500Z
DTSTAMP;VALUE=DATE-TIME:20260904T200422Z
UID:indico-contribution-550@indico.freedesktop.org
DESCRIPTION:Speakers: Naveen Kumar (Intel Corporation)\n**Problem Statemen
 t**\nCompositors are unaware of the media content frame rate and therefore
  present frames using the display's default refresh cadence. This mismatch
  leads to irregular frame timing\, causing judder during low-frame-rate vi
 deo playback (e.g.\, 24/30 fps) on both fixed-refresh and VRR displays. A 
 familiar example is 3:2 pulldown\, where 24 fps content is displayed on a 
 60 Hz panel with alternating 3- and 2-refresh frame durations\, resulting 
 in uneven motion. Figure 1 illustrates a similar issue\, showing how 30 fp
 s content is presented with irregular frame timing on a 40–60 Hz VRR dis
 play.\n\nFigure 1\nhttps://github.com/k2naveen/xdc-2026/blob/main/media-pl
 ayback-frame-judder.png\n\n**Solution**\nTo address this\, we propose the 
 wp-content-frame-rate-v1 [1] Wayland protocol\, enabling media players to 
 communicate the content frame rate to the compositor. The compositor [2] u
 ses this information to apply Low Frame Rate Compensation (LFC) on VRR dis
 plays by selecting the lowest stable refresh-rate multiple of the content 
 frame rate\, or to switch to a matching supported display mode on fixed-re
 fresh displays\, delivering smooth\, judder-free playback.\n\n[1] https://
 gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/518\n[2]
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/5091\n\nhttps://in
 dico.freedesktop.org/event/12/contributions/550/
LOCATION:
URL:https://indico.freedesktop.org/event/12/contributions/550/
END:VEVENT
END:VCALENDAR