You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many animations are not highly sensitive to timing, and would look better if the sequence was subtly adjusted to match the display device. We should add functions to coalesce and stretch sequences. e.g. an animation with a fixed 24fps time base, rendering to a display device at 119.880 Hz (1000/1001 × 120 Hz) should actually be rendered at the equivalent 23.976 rate; or an animation with a fixed 29.97 fps (1000/1001 × 30 Hz) time base rendered to a 90Hz display device should be played 1‰ faster.
The text was updated successfully, but these errors were encountered:
This is applicable to environments with managed time (e.g. a broadcast compositor like OBS) in its basic form; but yes, we would need more functionality to do adjustment for unstable/variable/uncertain output devices like we tend to have on desktop (to correctly adjust partial sequences).
Many animations are not highly sensitive to timing, and would look better if the sequence was subtly adjusted to match the display device. We should add functions to coalesce and stretch sequences. e.g. an animation with a fixed 24fps time base, rendering to a display device at 119.880 Hz (1000/1001 × 120 Hz) should actually be rendered at the equivalent 23.976 rate; or an animation with a fixed 29.97 fps (1000/1001 × 30 Hz) time base rendered to a 90Hz display device should be played 1‰ faster.
The text was updated successfully, but these errors were encountered: