News for hackers. Stuff that matters.
Re:Current state of AV1 codec playback support – Oct '22 by MBCook on Thursday October 20, 2022 @08:25PM (#33282661)
Apple supports standards they don’t own like h264 and h265. Why should they be forced to support this particular standard?

Do we want the government dictating which video encoding standards we have to use?

It’s not Apple is only allowing QuickTime, their fully owned protocol that others must license from them, and nothing else.

What is Apple doing on this issue that would be an anti-trust issue?

Re:Current state of AV1 codec playback support – Oct '22 by ZeroGravitas on Thursday October 20, 2022 @08:39PM (#33282752)
Apple do literally own necessary parts of those standards, and recieve royalties for them.
Re:Current state of AV1 codec playback support – Oct '22 by bagels on Thursday October 20, 2022 @08:31PM (#33282696)
Av1 helps google and other competitors. It doesn't help apple much.
Re:Current state of AV1 codec playback support – Oct '22 by MBCook on Thursday October 20, 2022 @08:43PM (#33282768)
I mean it may save them bandwidth on Apple TV+ or iTunes TV/movie purchases. But it seems they’ve chosen not to bother.

Maybe all the re-encoding would negate the benefits for them?

Maybe they didn’t think it was enough of an improvement over h264. Maybe they bet on h265 and it worked out well enough (for them) or it didn’t but they figure by the time they got everything set for VP1 something better will be ready.

Who knows.

Re:Current state of AV1 codec playback support – Oct '22 by FireGrey on Thursday October 20, 2022 @09:37PM (#33283234)
I believe their main reasoning for not supporting AV1 would be the lack of hardware decoding on their chips.

A minor improvement in network bandwidth and storage costs wouldn't be as high a priority as "up to 16 hours video playback (streamed)" on the iPhone 14.

Sure they could optionally support it in Safari without hardware decoding, but a service like YouTube will want to negotiate the lower bandwidth protocol over one that will make the device's battery last longer.

Maybe the licensing cost of h265 works out better for them than rushing out AV1 decode support on their chips or lowering the average battery life of their devices.

Re:Current state of AV1 codec playback support – Oct '22 by MBCook on Thursday October 20, 2022 @11:12PM (#33284043)
That would certainly have been the argument at first. Battery life is EVERYTHING.

But Netflix announced they would be using it in 2016. YouTube started using in 2018, the year the standard hit 1.0.

Apple had plenty of warning and time to get the necessary hardware acceleration blocks available by now. Chips have multi-year timelines but it’s been 4+ years.

Now on the other side, Netflix actually started using it in early 2020/late 2021, depending on device. YouTube rolled it out wide in 2020. Twitch is working on it.

So Apple is at most 2 years behind the content. It’s not like it’s been 5+. And if they decided to wait to see how those early rollouts went due to hardware timelines it might make sense support only appears to be coming now (based on someone pointing out AV1 shows up now in the AVPlayer framework documentation).

Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Thursday October 20, 2022 @11:54PM (#33284330)
I believe their main reasoning for not supporting AV1 would be the lack of hardware decoding on their chips.

I doubt it.

Apple Silicon is more than fast enough to decode AV1 in software. Sure, the battery life won’t be as good but there are other trade-offs that can be made.

Their latest chips were developed before AV1 had gained enough traction to be concerned about. I suspect that future M2 and M3 and A-series SoCs will have hardware decoding for AV1 built-in.

In the meanwhile, a future version of macOS Ventura and iOS 16 will have AV1 support; it’s just going to take a little longer. They probably want to roll it out simultaneously on iOS, macOS, tvOS, and iPadOS.

Re:Current state of AV1 codec playback support – Oct '22 by vetinari on Friday October 21, 2022 @04:46AM (#33285971)
When AMD/Nvidia/Intel and Samsung/Mediatek/Rockchip/etc were able to put AV1 blocks into their chips, I'm sure Apple would be capable of doing the same -- if they wanted. Now it looks that they do not want.
Re:Current state of AV1 codec playback support – Oct '22 by fyzix on Thursday October 20, 2022 @08:45PM (#33282777)
Your argument is a straw man, he's saying that apple should be force to allow competing browser engines on iOS so other vendors can support what they don't want to...
Re:Current state of AV1 codec playback support – Oct '22 by tambourine_man on Thursday October 20, 2022 @08:53PM (#33282832)
So you are saying there are no advantages to a closed platform, no place in the world for it and it shouldn't be allowed by the government to exist.

Because it's not like there are no alternatives.

If there was no Android, I'd say yeah, regulate away.

Re:Current state of AV1 codec playback support – Oct '22 by Gigachad on Thursday October 20, 2022 @10:29PM (#33283749)
Any time a statement starts with “so you are saying …” the answer is no. It’s a phrase entirely used for building strawmen.
Re:Current state of AV1 codec playback support – Oct '22 by tambourine_man on Thursday October 20, 2022 @10:34PM (#33283777)
Which is what the grandparent is being accused of. I guess it’s strawmen all the way down.
Re:Current state of AV1 codec playback support – Oct '22 by girvo on Thursday October 20, 2022 @11:30PM (#33284172)
If we all accuse each other of building strawmen, we don’t have to interact with each others actual arguments. Kind of neat, in a sad way.
Re:Current state of AV1 codec playback support – Oct '22 by throwup on Thursday October 20, 2022 @08:49PM (#33282806)
The issue raised is not about video codecs, but about browsers. Apple is using their market position to artificially prevent Safari from being competed against by other vendors—that is classic antitrust behavior.

For comparison, imagine Microsoft banned all browser engines other than EdgeHTML from running on Windows. Would you find that acceptable?

Re:Current state of AV1 codec playback support – Oct '22 by MBCook on Thursday October 20, 2022 @08:53PM (#33282829)
This is an article about video codecs. I interpreted the above comments as complaining Safari was a problem for not supporting this video codec.

So my comment was about their video codec policy.

Re:Current state of AV1 codec playback support – Oct '22 by MobiusHorizons on Thursday October 20, 2022 @09:26PM (#33283112)
You may not be aware, but chrome does exist on iOS, but even so, it is actually running the safari rendering engine because apple prevents other browser engines from running. This effectively prevents chrome or Firefox from offering a browser with av1 support (as far as I am aware) so the browser engine is relevant to the codec policy discussion.
Re:Current state of AV1 codec playback support – Oct '22 by threeseed on Friday October 21, 2022 @12:08AM (#33284395)
I don't believe Apple has banned alternative engines.

It's just that they don't allow JIT code execution for security reasons which is needed for a comparatively performant engine.

Re:Current state of AV1 codec playback support – Oct '22 by Jasper_ on Friday October 21, 2022 @12:45AM (#33284607)
Yes, they have banned alternative engines.

https://developer.apple.com/app-store/review/guidelines/#2.5...

> Apps that browse the web must use the appropriate WebKit framework and WebKit Javascript.

Re:Current state of AV1 codec playback support – Oct '22 by enkrs on Friday October 21, 2022 @03:06AM (#33285336)
Which is the reason why I choose iOS: I trust Apple to implement the integrations in the WebView for best battery life. To get new OS features in the browser right away. Would Google Chrome implement picture-in-picture on the iPhone if they were running their own engine?

I use Firefox on iOS for the password and tab sync integration, and am supper happy that it’s using the WebKit framework. I care about the iOS experience more than some video codec support.

Re:Current state of AV1 codec playback support – Oct '22 by vetinari on Friday October 21, 2022 @04:04AM (#33285680)
If the other browsers could implement their engines, you would still have the option not to install them.

Since they can not do it, you don't have that option.

Re:Current state of AV1 codec playback support – Oct '22 by alwillis on Friday October 21, 2022 @04:29PM (#33292690)
If the other browsers could implement their engines, you would still have the option not to install them.

So it’s okay for user who (in theory) installed a 3rd party browser on iOS to have a worse experience and potentially make themselves vulnerable to malware? That’s exactly what Apple doesn’t want.

Re:Current state of AV1 codec playback support – Oct '22 by paulryanrogers on Friday October 21, 2022 @09:11PM (#33294696)
Or potentially offer a more secure browser than Safari
Re:Current state of AV1 codec playback support – Oct '22 by dmitriid on Friday October 21, 2022 @03:32AM (#33285491)
Given that Chrome abuses its market position to ram through and continuously release hundreds of Chrome-only non-standards I view this as a net positive.
Re:Current state of AV1 codec playback support – Oct '22 by kersplody on Thursday October 20, 2022 @08:57PM (#33282858)
Apple might have made a deal with one or more major h.265 patent holders that discourages them from fully supporting av-1, similar to how Google pays apple nine digits a year to keep Google search default in the Apple ecosystem.

Court action could compel any deal like this to be made public.

Re:Current state of AV1 codec playback support – Oct '22 by MBCook on Thursday October 20, 2022 @09:24PM (#33283082)
Honestly, being Apple, it could 100% be a “screw Google, it doesn’t hurt us” move without any direct financial incentive.

They’ve done it many times before (though usually in the Steve Jobs era).

Re:Current state of AV1 codec playback support – Oct '22 by hatware on Friday October 21, 2022 @02:16AM (#33285083)
> similar to how Google pays apple nine digits a year

I couldn't believe this and looked it up. It's $9 billion. Which is ten digits.

Good god.