I’m surprised it’s going to support 4K on YouTube. Glad, though not a huge deal to me since there’s diminishing returns on high quality content, and YouTube is not exactly a lot of high quality video lol
I’m not comfortable logging in with my real google, Apple, or Microsoft accounts on most of these streaming devices as I don’t trust their security, which is one of the reasons I’m seriously considering AppleTV, if they ever update it. Apple or an Xbox, okay, my tv, a Roku, or a FireTV, not really...
[automerge]1592906236[/automerge]
Technical benefit aside, there are plenty of sites and plenty of content in VP9 and the *hardware* supports it, so they should support it.
Not supporting it just gives a far worse user experience, and apple are supposedly all about user experience...
It’s one of the ridiculous moves I expect from Apple. Makes zero sense, I have seriously no clue how it in any way benefits Apple not to support it, buuuut they like being difficult.
at least it doesn’t affect me much personally. At least not yet.
[automerge]1592906713[/automerge]
I can't see Apple bothering to implement VP9 when
a) it is inferior to HEVC from a quality perspective
I think that’s kind of dubious, plus completely irrelevant. From what I’ve seen it’s similar, maybe beats H.265 under the right settings, and who cares? Apple isn’t paying for any extra bandwidth it uses, if it uses any.
I'm not sure. YouTube uses the VP9 video codec for 4k, which Apple doesn't use, so I'm not certain what has changed.
For some reason, the blame tends to somehow be that Apple is doing something to deny YouTube or that Apple isn't supporting VP9, but YouTub is the one using the non-standard standard (not many use it).
YouTube has not bothered to support the standard YouTube uses in their own app.
Keep in mind that Plex will play VP9 on the AppleTV, so it's clearly not anything Apple is stopping YouTube from doing. YouTube has made the choice to not support 4k on ATV.
I mean it is a standard, arguably more of a literal standard than H.265 is depending on your perspective. And while they might be able to do it, it would require doing it in software if Apple doesn’t support it, which at best is inefficient.
And presumably google isn’t wanting to store content in a bunch of separate codecs just to support one device who’s manufacturer randomly and pointlessly won’t support the codec.