Nigh hijacked the
"image easing" thread with peripheral issue, so trying to pull it separate:
"TheEndless" wrote:
"EnTerr" wrote:
"TheEndless" wrote:
The output refresh rate is always 60Hz (in the US), regardless of how long it takes you to draw a single roScreen frame.
How do you know that? You say it with conviction, is there a spec (radical idea) i can find? My censored Sony TV shows resolution but not Hz.
Primarily because the video framerate isn't affected when drawing overlays to the roScreen. If you break into the debugger, for instance, video continues to play, while the last frame of your roScreen is also displayed. But also because the monitor I use for development does display the refresh rate, and it's always 60Hz, with or without video playing, even for the SD resolutions.
I'd have sworn they listed that online in the detailed specs on the comparison chart at one time, but I can't find it now.
Drawing overlays has no reason to affect refresh rate, SwapBuffers() only changes (conceptually) the pointer that video output generator uses at its own pace (be it 24, 50, 60Hz). Shan't doubt the monitor though. Frequency does not change if playing one of the "
Example Short 23.976 fps" clips on Netflix either?
It seams likely Roku player
always outputs at 60Hz. RokuCo probably forgot the spec info when re-designing the
http://www.roku.com/products/compare page with big checkboxes + small fonts, though conspiracy theorists can go with "trying to hide lack of native support for 1080p24 BD video and 50fps UK/EU content". Now I see AppleTV supports both 50Hz and 60Hz - and Chromecast dongle seems to be 60Hz only - but can't find streamers doing native 24fps.
That would mean for 24fps video player pulls a
3:2 pull-down by making up every 5th frame as "dirty" (by combining two neighbors, A A (A+B) B B) - or maybe just by showing movie frames in AAABB pattern. 24/60=2/5, so pattern is ends up synced after every 2nd input and 5th output frame. There would be "judder", wonder if noticeable.