Hacker News new | past | comments | ask | show | jobs | submit
>My minipc has no issue outputting at 24 or 23.976 or 30 or 29.97 or 59.94 Hz either

I don't think you've understood the problem I'm describing. A TV with a 60hz panel literally can't smoothly display a 24fps incoming signal. Even though 60 is more than 24 modern TVs can't [0] drop the panel rate to match the incoming 24 fps signal. Instead they keep the panel at 60hz and fuck with the timing of every 2nd frame to compensate for 60 not being divisible by 24 - judder.

To get a smooth picture everything has to be either same or a clean multiple of the source material. (roughly - fractions like 23.976 aren't noticable but 60/24=2.5 is right in the middle....worst case scenario).

Best way around this mess is 120hz end to end - which means no N100. Or just accept the judder.

>not smart TV apps.

I'm not advocating for them, just saying I understand why less tech inclined use them.

[0] https://en.wikipedia.org/wiki/Flicker_fusion_threshold

Okay, but if you have a 120Hz panel, as you said, you can just hold your 24Hz signal for 5 frames. And a minipc and TV can happily negotiate a 24Hz HDMI signal. Flicker fusion also has nothing to do with this unless you have like BFI or something.

If your source is 24Hz, it will never be 120Hz end-to-end. It's already 24Hz. You can just send that to the display. If your panel can't cleanly display that, it's not going to be able to with a built in app either. The app is also getting a 24Hz source video.