Earlier quoted context omitted.
Can you dumb this down to ELI16 for me? I'm intrigued but am not following.
Imagine you’re trying to encode the topography of a hilly landscape faithfully. If you use 8 bits to represent the height you can have 256 distinct levels, which is reasonably smooth — like a Minecraft map. If you tried to cut this down to just half - 4 bits - then now you would have only 16 levels! This is very ugly, with big blocky staircases instead of nice smooth hills. So what to do to compress this data better?…
Technical Overview of AV1 Spec
21–22 of 22 posts
[deleted]
Re: Technical Overview of AV1 Spec
#22Earlier quoted context omitted.
That may be why videos tend to stall when in the movie is raining
Yeah. And that's why TV stores really like slow-motion shots or static landscapes to show off the TV. Any motion will cause "HDTV blur" as the encoder struggles to describe complex motion with the limited number of bits it's allowed to use. Stuff like static, film grain, particles like snow or rain, those all suck up bits from the same encoding budget. "Why Snow and Confetti Ruin YouTube Video Quality" by Tom Scott p…
I think there are certain presets that work slightly better depending on what you're encoding. x264 has a "touhou" preset that should work slightly better for confetti and things like it.
Many streaming services sidestep this by generating grain on the client device rather than encoding it in the video though, but that may just be to make screen recording more annoying.