Case in point, consider Wikipedia.
It is a complete non starter for Apple or any mobile device maker to build in support for a non hardware optimized codec on a mobile device.
How does that benefit users besides the ones who bemoan not being able to run Linux on the Apple Pencil?
There's a specific reason why Theora was last used a decade ago... Apple. Apple is the reason. There was some other opposition, but in 2009, Apple drove the hardest against Theora being included in the HTML5 spec, and they ultimately won, leaving us with no standard codec everyone could actually agree on. Because the web is supposed to be open, and h264 is not.
It being excluded from the spec, you could not rely on Theora support in the browser.
> It is a complete non starter for Apple or any mobile device maker to build in support for a non hardware optimized codec on a mobile device.
Given that a RPi 5 takes less than a full core to decode h264, I'm not even sure this is a real concern. In my tests, ogv.js is able to decode VP9 at modern resolutions on an iPad without even really making the device warm; it's undoutedly inefficient, but the fact that it can even be done using WebAssembly gives me a feeling that this isn't really the huge problem it's made out to be.
For Theora... I mean. It's just not an issue. You can just do it in software. Maybe not in 2009, but certainly today, right now, on any hardware made in the past few years, on one core, without even driving the clocks up.
For AV1, yes, sure, this is a real issue; but Apple has been a part of the AOM for years, so I have no idea why they are building machines without hardware AV1 acceleration today. That's a question that only Apple can answer, given that it has real adoption already.
> How does that benefit users besides the ones who bemoan not being able to run Linux on the Apple Pencil?
Yes sure, let's take a random unrelated detour to make fun of tinkerers who like to be able to reads notes run their own software on hardware they purchased. I'm disappointed, although unfortunately not surprised at all.
The last stable release was in 2009. The iPhone was still a bit player then, only available via a few carriers and still behind RIM in market share. No one cared about Apple’s opinion in 2009.
> For AV1, yes, sure, this is a real issue; but Apple has been a part of the AOM for years, so I have no idea why they are building machines without hardware AV1 acceleration today. That's a question that only Apple can answer, given that it has real adoption already.
https://bitmovin.com/av1-playback-support
> Yes sure, let's take a random unrelated detour to make fun of tinkerers who like to be able to reads notes run their own software on hardware they purchased. I'm disappointed, although unfortunately not surprised at all.
How is not supporting an “open standard” stopping anyone from “tinkering”? There are open source implementations of the encoders and they will be decoded in hardware once you install whatever you are tinkering with on your phone.
https://www.forbesindia.com/amp/article/explainers/top-10-la...
And “Words Mean Things”. There is a huge difference between “open source implementations” and “patent unencumbered” codecs
And I don't care. I'll care when Wikipedia gets sued for using Opus, or AV1, or when Mozilla gets sued for shipping it in their browser, or something. Until then, as far as I'm concerned, it's empty threats from dog shit liars.
But this aside, I don't understand why you can't just say what you mean right out the gates since I know you know what I am talking about, I know you knew from reply 1, and I'm sure you've already played through this conversation before. I could've said Theora, Quite OK Audio or perhaps even MPEG Layer 3 just to fuck around, but I really would like to have an honest conversation, and not just mess around with technicalities.
I'm not interested in debating the legal system, or how AOM's license agreement works, or any of that crap. In practice, almost everyone can use "open", patent-unencumbered codecs without fear of lawsuits. The companies big enough to have to worry about patent lawsuits virtually no matter what have basically been using patent agreements as a weapon against the traditional patent cartels. This is of course, deeply unfortunate, since it just perpetuates the terribly broken U.S. patent system and the situation it has with video codecs.
I understand that you have Opinions:tm: regarding this, I already caught on. But what you have to understand is that to most people, including plenty of lawyers, these opinions are essentially fringe. If they weren't, AV1 wouldn't be shipping in Firefox and Wikipedia wouldn't be using them. And not only that, it has nothing to do with the concept of patent-unencumbered codecs. There's always going to be codecs where the known patents have simply expired. At least in the U.S., I'm pretty sure that even includes MPEG2, but it'd suck if open source software was limited to just MPEG2. (And of course, if we do find new patents not covered under previous patent pools, that happen to apply, you have to realize that this liability existed for everyone already, including people who paid royalties anyways.)
On the other hand, if I use H.264 as a large business and I choose to modify the open source implementation and pay the royalties, I’m mostly covered.
Theora was last updated over a decade ago and currently no processor has built in support for it making it a non startee on mobile devices where battery life is at a premium.
And if AV1 meets your definition of “open” why are you complaining about Apple not supporting an “open codec” since Safari supports AV1?
While you may not be interested in talking about the legal system, I can guarantee you that every major company is before they re-encode their library using a codec or add die to the chip to optimize decoding.
Big companies can’t use their patents against small patent trolls who are just holding companies built just to sue large companies.
In other words, it is financially dumb for any large company to support an “open” protocol based on 20 year old technology (when patents expire) or newer supposed “open” codecs that are just as patent encumbered.
Anyway, if it's good enough for Mozilla and Wikipedia and thousands of smaller companies, it's good enough for me. You do you.
https://bitmovin.com/apple-av1-support/
> The WebKit blog provided more information about Safari 17.0, confirming support for the AV1 video codec was added on devices with hardware decoding support
And if you don’t believe the blog, maybe you believe the caniuse site.
- Only iPhone 15 Pro? not even an iPhone 15? This means almost nothing. You can't just be like, "Oh my site only works on every device except iPhones except iPhone 15 Pro.
- Still no Opus...
I will fully admit that I am out of date on this, by like a couple months. But the reason why I say it like this is because people have been making this claim for years even though it has apparently been true for like two months. Apple is half-assing this every step of the way. It will be like, 2025 before a site can just use AV1 without needing multiple encodings, and at that point you probably still won't be able to use Opus.
Thanks, Apple?
And let’s not pretend it’s been available for Android forever. Chrome for Android just received support for AV1 last month as did Firefox for Android.
And Opus support has been around since iOS 11
Web developers are so self-centered. You are developers, not users, don't speak like you are doing good things for users. You are just doing things for yourselves so you can extract money/data from your users.
Most web developers nowadays are just enemy of web users.
It's categorically not good for the consumer. It's good for the small enterprise companies/upstarts that don't have the budget to keep iterating their software, which would otherwise be left in the dust quiet quickly. With apple holding it back, they've got a bigger timeframe in which their software doesn't behave as a legacy application, as everyone Else is forced to use subpar features too.
From the users perspective it is - just as they said - worse, as things like codec support improve battery life and playback quality for example.
However web developers go one side: the google side. Reason? They can do half the work and get twice the money. What a gain! They sell the web to google for their dirty money.