Netflix is now doing per-shot encoding for UHD content

Re:Netflix is now doing per-shot encoding for UHD content by AnssiH on Saturday August 29, 2020 @05:55AM (#24314989)

I believe most people just don't notice the judder, and many of the rest don't care. E.g. it took a lot of convincing to get Google to add "use 50p output" to Chromecast settings years ago (and that didn't fix 24p of course, just European 25p/50p which is more severely affected).

Also, most high-end TVs are able to recover the original 24p (or other) frame rate and thus remove the judder by using specific settings: https://www.rtings.com/tv/reviews/lg/c9-oled/settings#judder

I tested with a high-speed camera that with correct settings my old Samsung UE75H6475 was able to recover the original frame rate perfectly from quite a few framerate mangling combinations. Haven't done similar testing with my current C9, though.

[ Parent | on HN ]

Re:Netflix is now doing per-shot encoding for UHD content by hn_check on Saturday August 29, 2020 @11:37AM (#24316821)

"I believe most people just don't notice the judder, and many of the rest don't care"

This is probably the case. DAZN took over NFL streaming in Canada and for the first two years seemed to use their existing European soccer processing chain (they might still --- I gave it a try to years straight and then gave up). So the 60/30 NFL stream was re-encoded to 25/50, and then on playback on my set would be displayed at 30/60. It was brutal, and even if displayed at 25 or 50 FPS was still brutal because they were seriously corrupting the NFL stream.

I tried it across a number of devices -- AppleTV, Chromecast, different TVs, pads, laptops -- and it was just unbelievably intolerable to me. Every panning pass was the horrendous juddering mess. Yet somehow no one seemed to have a problem with this! In discussions it seemed to be a non-issue.

[ Parent | on HN ]