Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Decoding Netflix's AV1 Streams

singhkays.com

Post reply on HN
Print view View original

51–60 of 80 posts

Re: Decoding Netflix's AV1 Streams

#51

Post by inquirerGeneral »

isatty wrote: post #41
CharlesW wrote: post #15

Earlier quoted context omitted.

The credible rumors beyond AV1 decode include: Wi-Fi 7 via Apple's home-grown N1 chip, a CPU fast enough to support the next-gen Siri release on-device, a RAM bump, improved pass-through for high-end audio formats, potentially a camera (the new square selfie sensor would be perfect for this) for easier group/family FaceTiming, and more aggressive pricing.

The appletv is such a good device that I’m paying it whatever the price may be. TVs have horrible UIs and are generally ad ridden garbage. Not using anything android based because of the same reason and slow.

Google TV UI is fine, only one I accept other than Apple TV

Re: Decoding Netflix's AV1 Streams

#52

Post by pkroll »

zamadatix wrote: post #20
alfalfasprout wrote: post #3

Earlier quoted context omitted.

What benefit would a new appleTV have other than reduced bandwidth usage?

I wouldn't mind if they enabled the 120 Hz support with the new chipset. I like my TV but the framerate matching feature causes a few seconds of black screen each time I switch between and also drops the UI to 24 FPS. Would be nice if everything just ran at 120 FPS all the time, and since 24/30/60 are perfect frame multiples that's nice to. NTSTC content at 23.976 I'd hope the player would just speed up at that point…

"NTSTC content at 23.976 I'd hope the player would just speed up at that point, but even if not... judder at 120 Hz is better than at 60 Hz."

I'd bet money when TVs are advertised at 120 FPS, they're really 119.88 FPS, so no judder showing 23.976 FPS and the other NTSC-off display rates.

Re: Decoding Netflix's AV1 Streams

#53

Post by porridgeraisin »

wonnage wrote: post #49
vanviegen wrote: post #45

Earlier quoted context omitted.

Well, journalists often write like that. I presume that's where the LLMs learned. I always find that style annoying, but especially so in a technical post like this.

Probably the only overlap between AI slop and actual journalistic writing is the obsession with em-dashes

And hallucinations.

Re: Decoding Netflix's AV1 Streams

#54

Post by kllrnohj »

galaxy_gas wrote: post #38
kllrnohj wrote: post #25

Interesting charts, but this is all completely meaningless without image quality comparisons. I can easily use 50% less bandwidth than Netflix's H264 streams as well, with H264 even, by just cranking up the compression & dropping the bitrate. Presumably nothing jumped out at the author as being worse, but come on how can you have a whole section on why AV1's regression on Bojack is actually a good thing because the q…

Taking screenshot of netflix on my device results in black square, I dont know if this applies on lower levels of Widevine but if it doesn't then the quality will be much lower as Netflix do not serve 720+ video unless there is protected DRM path

It'd have to be the good ol' "take a picture of the screen" route without getting into the more gray areas.

Re: Decoding Netflix's AV1 Streams

#55

Post by bcraven »

adzm wrote: post #5
CharlesW wrote: post #2

Fascinating, thank you for this analysis! Currently pining for release of an updated Apple TV, which will have an SoC capable of hardware AV1 decode. It'd be great to hear from someone at Netflix about the unexpected Bojack Horseman results. I'd bet that Netflix just isn't yet taking advantage of AV1 features designed especially for this kind of animation and synthetic content.

> the unexpected Bojack Horseman results. I'd bet that Netflix just isn't yet taking advantage of AV1 features designed especially for this kind of animation and synthetic content. While the percentages look scary, it's only a slight difference (60kbps!) and still around 1mbps average, but with a significant quality boost (very crisp lines and near perfect quality). I bet Netflix could encode at nearly half that bitr…

Some of the torrent releases out of MVGroup are done as h266.

I think as technical tests as much as anything, but they're interesting to see.

Re: Decoding Netflix's AV1 Streams

#56

Post by Wowfunhappy »

vanviegen wrote: post #45
delta_p_delta_x wrote: post #32

Earlier quoted context omitted.

LLMs tend to produce ridiculous similes, idioms, euphemisms, and analogues that fall apart upon the slightest scrutiny, as though they are genuine English constructions. I despise it. No one in reality writes like that. Who the hell thinks 'bytes and pixels' are a battleground? if you want to talk about licensing problems, just say they are licensing problems , don't accept shitty similes from LLMs that humanise deci…

Well, journalists often write like that. I presume that's where the LLMs learned. I always find that style annoying, but especially so in a technical post like this.

I don't know which publications you're reading, but the ones I read do not write like this!

Re: Decoding Netflix's AV1 Streams

#57

Post by mijkal »

encom wrote: post #17

Okay, so AV1 has lower bitrate. I can encode any video format at arbitrary bitrates, but that metric is not useful on its own. An article about how AV1 requires less bits for the same or improved perceptual quality would have been far more interesting.

This article is a good primer on how AV1 works (and compares with VP8 and VP9): https://www.red5.net/blog/av1-vs-vp9-vs-vp8-comparison-for-l...

Re: Decoding Netflix's AV1 Streams

#58

Post by zamadatix »

pkroll wrote: post #52
zamadatix wrote: post #20

Earlier quoted context omitted.

I wouldn't mind if they enabled the 120 Hz support with the new chipset. I like my TV but the framerate matching feature causes a few seconds of black screen each time I switch between and also drops the UI to 24 FPS. Would be nice if everything just ran at 120 FPS all the time, and since 24/30/60 are perfect frame multiples that's nice to. NTSTC content at 23.976 I'd hope the player would just speed up at that point…

"NTSTC content at 23.976 I'd hope the player would just speed up at that point, but even if not... judder at 120 Hz is better than at 60 Hz." I'd bet money when TVs are advertised at 120 FPS, they're really 119.88 FPS, so no judder showing 23.976 FPS and the other NTSC-off display rates.

Some content is truly exactly 24 FPS or 30 FPS though, so whichever path the TV goes (i.e. NTSC rate or integer rate) the same problem will exist. I suppose some TVs might have extremely fancy film mode detection which catches the occasional frame difference, but I doubt mine does :D

Re: Decoding Netflix's AV1 Streams

#59

Post by ac29 »

z0r wrote: post #16
jpalawaga wrote: post #4

I feel like this was copy edited by ChatGPT and it really grates me. I couldn’t help but lose focus after I started seeing telltale signs of AI. While the topic matter is interesting, I feel like obviously synthetic content falls into the “that which was not worth writing, is not worth reading either” trap. If the authors tone is extremely ChatGPT-esque, I apologize in advance.

This didn't trip my AI detector; I instinctively skimmed to look at the numbers and conclusions. Your comment made me go back up to the top and read the opening paragraphs and I see what you are saying. It is always painful to realize you are reading AI product. I think it is less of a problem with this blog post because it is just presenting a handful of tables of numbers and a few graphs, but it seems I am already…

> This didn't trip my AI detector

LLMs seem to love putting stuff in bold, thats an immediate red flag for me.

Re: Decoding Netflix's AV1 Streams

#60

Post by whycome »

jpalawaga wrote: post #4

I feel like this was copy edited by ChatGPT and it really grates me. I couldn’t help but lose focus after I started seeing telltale signs of AI. While the topic matter is interesting, I feel like obviously synthetic content falls into the “that which was not worth writing, is not worth reading either” trap. If the authors tone is extremely ChatGPT-esque, I apologize in advance.

Well, use the chatgpt-based compression system for this articl about compression. By that I mean they might have used ChatGPT to expand this article from simple bullet points and now you can use ChatGPT to summarize this article into succint bullet points for quick digestion.
Post reply on HN