mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-11-16 13:51:19 +01:00
Windows Graphics Capture holds a capture to 60 frames a second unless it is given a minimum update interval, so a 120 Hz display was recorded at half its rate and a one-refresh flash could fall between two frames. ScreenCaptureKit was asked for at most 30 (the default --fps), so macOS lost frames the same way. --fps now means the most frames a second, and 0, the new default, means no cap: Windows sets the session's minimum update interval to a millisecond (or a frame at --fps), and macOS sets a zero minimum frame interval. The encoder is told 60 fps when there is no cap. On Windows each sample was also stamped to last 1/fps whatever the gap to the next frame. A frame is now held until the next arrives and given the real time between them; the last one still gets a frame at the nominal rate. macOS passes ScreenCaptureKit's own sample timing through, so needs no change. Checked on a Mac with a 120 Hz display and komorebi for Mac running: with no cap a display is recorded a frame every 8.3 ms, and --fps 30 holds it to about 30 a second. The video holds as many frames as the frame log has rows, and the state komorebi was recorded in matches what the frames show. The macOS encoder never reads fps, so CaptureConfig::fps now says it reaches only the Windows one.