Conversation

Notices

1. Embed this notice
   ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Sunday, 22-Oct-2023 03:24:54 JST ✧✦Catherine✦✧

   in reply to

   • mcc
   • Tóth Gábor Baltazár
   • Josh Simmons

   @tthbaltazar @dotstdy @mcc ohh, that's pretty straightforward, yeah

   • Embed this notice
     Erin 💽 (erincandescent@queer.af)'s status on Sunday, 22-Oct-2023 03:24:54 JST Erin 💽

     in reply to

     • mcc
     • Tóth Gábor Baltazár
     • Josh Simmons

     @whitequark @tthbaltazar @dotstdy @mcc For fixed rate displays, you generally don't want the focused app to control this; monitors have an annoying habit of taking 5-10s to resync themselves when changing fixed refresh rates. Typically only full screen apps are allowed to change the display refresh rate.

     Also controlling a mouse on a 24hz display feels awful

     This approach probably works better on a VRR display, but probably you want to frame double/triple/etc fixed rate content to as close to the screens native rate as possible to make your UI feel nice

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Josh Simmons (dotstdy@mastodon.social)'s status on Sunday, 22-Oct-2023 03:24:56 JST Josh Simmons

     in reply to

     • mcc

     @mcc @whitequark at the very least one isn't usually multi-video-drifting, and if it's broken in that case it's not really the end of the world. Also I'm pretty sure some video players do support VRR.

   • Embed this notice
     Tóth Gábor Baltazár (tthbaltazar@chaos.social)'s status on Sunday, 22-Oct-2023 03:24:56 JST Tóth Gábor Baltazár

     in reply to

     • mcc
     • Josh Simmons

     @dotstdy @mcc @whitequark
     yeah, having the active/focused window be the one in control and everything else just do frame doubling or skipping

     android does this already

   • Embed this notice
     ✧✦Catherine✦✧ (whitequark@mastodon.social)'s status on Sunday, 22-Oct-2023 03:24:57 JST ✧✦Catherine✦✧

     in reply to

     • mcc

     @mcc one issue is that every application on your desktop can potentially want a different refresh rate. this already happens with audio but even with audio resampling can take a lot of power; with video it's less feasible

   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Sunday, 22-Oct-2023 03:24:57 JST mcc

     in reply to

     @whitequark It's true, but with video I am often watching it in a full screen context (either just selecting full screen, or watching in the plex/appletv ecosystem)

   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Sunday, 22-Oct-2023 03:24:58 JST mcc

     in reply to

     - Some modern monitors/TVs support variable refresh rates. I've been told most HDTVs can tolerate a *little* wobble, like on the order of 1 hz, in the incoming framerate away from 60 fps.
     - Can a modern HDTV, given a 50fps/PAL-like signal, simply play that, or will it be time-resampling?
     - Does that capability change if I stream the video from Plex, on a smart device like an Apple TV?
     - What if I play such a video file on a modern PC with VLC (windows? linux? fullscreen? not fullscreen?)

   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Sunday, 22-Oct-2023 03:24:58 JST mcc

     in reply to

     In general, now that we are standardizing on a display tech (LCD/LED flatscreens) which in principle is capable of varying its framerate freely, why do we put up with frustrations like pulldown and horrors like algorithmic/"AI" "smooth" resampling/"judder correction", when we could just teach the signal chain to know what the correct framerate is and preserve it?

     Our HDTVs could just show 24fps video at 24fps (or 48fps doubled, if that's easier). Nothing really prevents it.

   • Embed this notice
     mcc (mcc@mastodon.social)'s status on Sunday, 22-Oct-2023 03:24:59 JST mcc

     It frustrates me that all digital video tech is so nonchalant about framerates.

     I've got here some PAL format DVDs I'd like to digitize. I'd like to place them on our Plex and watch them later.

     Things I can't figure out:
     - Is it better to digitize them at 25 fps and hope the playback device can do something with that, or 30 fps so it more natively matches the probable playback device?
     - Come to think of it, do native devices run at a multiple of 30 fps or a multiple of 29.97 fps?