Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Confused-User

macrumors 6502a
Oct 14, 2014
852
988
Many thanks for your thorough reply, you worded it very well.

I very much agree with your reasoning, especially knowing a Apple for decades and how they behave. But also because, as you said, there’s not a lot of use for AV1 encoding, and there are a lot of applications for AV1 decoding. 1) low priority for it when it comes to die space management, 2) Apple is not after the “Handbrake diehards” that compress big files of high resolution video, and 3) It’s always an Apple policy to leave new features to make future chips more appealing. I think you call it “breadcrumbing” in English but I’m not a native speaker so I’m not sure.
I don't agree with your characterization of Apple, but that aside, I haven't heard the term "breadcrumbing" used in this way. Usually it refers to the manipulation of a friend, lover, or ex-lover.
Now I’m curious about h.266. Is it really around the corner? From what I see, most people keep using h.264 and the tests I’ve done with h.265 doesn’t provide a big improvement. I find it a bit disappointing, that’s why all my hopes were in a standard just like the AV1.
It is, because it's being used in some broadcast standards. But as for whether it will be widely adopted outside that domain... I have no idea.

h.266 may have some specific use for the AVP, as it supports things like 360-degree video, and other features useful for VR. I don't know how AV1 stacks up compared to that.
 

vigilant

macrumors 6502a
Aug 7, 2007
715
288
Nashville, TN
You probably meant this to be M3?

Actually, I would think M3 would be 4P + 6E/8E, if they managed (which I think they will) to improve the E-core's IPC. Base level Mx SoC need more power efficiency rather than performance. 4P for base Mx should be more than enough for most basic users' needs.

From various threads I've read, N3 process is not friendly to SRAM/cache designs, as it doesn't give the same space saving as logics. More cores means more cache required to feed them, so I don't think M3 SoCs will grow much in core counts for CPU. GPU and NPU probably will grow more.
I’m inclined to agree with you. 4P + 6E/8E maybe the best bet. Those chips are expected to be in the Air and iPad Pros, and one has to wonder how much further you can push that thermal envelope without a cooling solution?

3NM may mitigate any cooling issues that could exist, but we also have to think about GPU, and the new encoder decoder features, as well as people wanting to be able to run 2 monitors at once on the entry level M series.

The last thing to that about is one of the hallmarks of the iPad Pro and MacBook Air is the long battery life. Can we quantify in real numbers what the performance per watt is of 4P + 6E/8E versus 6P + 4E? Most of the time the chip is using the E cores at least from my testing unless something has changed. More E cores should help the “Race to Sleep” tremendously. It would also free up enough room for IO going out to be enhanced if needed (IE Dual Display and GPU Cores).

Who knows, they may do 5x5 on the P + E, but having an odd number for each may be more problems then it’s worth because of NUMA (does it apply to ARM?).
 
  • Like
Reactions: quarkysg

vigilant

macrumors 6502a
Aug 7, 2007
715
288
Nashville, TN
I don't agree with your characterization of Apple, but that aside, I haven't heard the term "breadcrumbing" used in this way. Usually it refers to the manipulation of a friend, lover, or ex-lover.

It is, because it's being used in some broadcast standards. But as for whether it will be widely adopted outside that domain... I have no idea.

h.266 may have some specific use for the AVP, as it supports things like 360-degree video, and other features useful for VR. I don't know how AV1 stacks up compared to that.
From the limited I know about the current environment, I don’t believe Apple does any kind of “breadcrumbing”. At least it’s my understanding is theres a Plan A, and fallback Plan B. If Plan A didn’t reach the benchmarks for what they are trying to do, they’ll fall back on Plan B. Like the A series chip from last year. Apple is a deeply paranoid company, and is fully aware that if they were to announce something that doesn’t work as expected there would be backlash.
 

Populus

macrumors 603
Aug 24, 2012
5,941
8,411
Spain, Europe
I don't agree with your characterization of Apple, but that aside, I haven't heard the term "breadcrumbing" used in this way. Usually it refers to the manipulation of a friend, lover, or ex-lover.

Okay, I thought it could be used to depict someone giving little good things (or features, in this case) keeping part of the good stuff in order to make future versions more appealing. But if that word is weird on this context, thanks for letting me know, as I’m not a native speaker.

It is, because it's being used in some broadcast standards. But as for whether it will be widely adopted outside that domain... I have no idea.

h.266 may have some specific use for the AVP, as it supports things like 360-degree video, and other features useful for VR. I don't know how AV1 stacks up compared to that.
Okay, then it might be more niche for the moment. But anyway, it’s good to have it on the radar.
 

Populus

macrumors 603
Aug 24, 2012
5,941
8,411
Spain, Europe
From the limited I know about the current environment, I don’t believe Apple does any kind of “breadcrumbing”. At least it’s my understanding is theres a Plan A, and fallback Plan B. If Plan A didn’t reach the benchmarks for what they are trying to do, they’ll fall back on Plan B. Like the A series chip from last year. Apple is a deeply paranoid company, and is fully aware that if they were to announce something that doesn’t work as expected there would be backlash.
Actually, I agree that, at least with the case of the A17 GPU, they had to pull it back from the A16 because of the high temperatures. At least according to the leaks. So yes, in this case they had the fallback plan of splitting the A16 gen into the A16 and the A17 with a more efficient manufacturing process. However, I personally don’t think this is the case for all the features, hardware or software ones.
 

deconstruct60

macrumors G5
Mar 10, 2009
12,493
4,053
There may well be some truth to that, but also possibly not. ProRes and AV1 are for very different target markets.

For decode (use of the files) yes. For encode not as much, but yes there is a large non-intersection.

Apple would not be sad at all if more AV1 file creation logistics trains for major distributors took ProRes as an 'input'.


Until recently, nobody had hardware encode for AV1 in their CPU chips.

Matters less when the CPU can interoperate with a dGPU that does have hardware encode. Video (i.e., graphical) Media en/de coders are more naturally paired with GPUs than CPUs. That what the 'G' is for a GPU.



For encode it is recent, but for decode it isn't. Back in 2020

" ... As the first CPU out with AV1 decode support, we wanted to see just how much of a difference Tiger Lake would make in common video tasks. ..."

Some of this is a chicken and egg thing where there needs to be a high number of deployed decoders out there to push encoding into a task that isn't being centralized/consolidated on a relatively few number of 'back end' servers.



I haven't been playing close attention to this, so I may be mistaken, but I think only the most recent AMDs with integrated GPUs have that.

It doesn't have to be integrated.

https://www.tomshardware.com/news/intel-av1-encoder-for-cpus

but yes the backstop that Apple has been leaning on for a long while has been to just do it in non-specific hardware. (software encoder).

I don't think Apple skipping AV1 encoding is going to be a major issue for most people. (That said, with an Intel or AMD chip, you can always add a dGPU that supports it, and with Apple you don't have that option, so it's not entirely unimportant.)

It is important if Apple is going to deliberately take anyway any discrete accelerator option. They can choose to block other people's stuff , but that just means it is a their job to follow through.


I'm also not sure now long-lived AV1 is going to be. It's still not that common, and h.266 is around the corner.

H.266 still comes with license fee overhead. AV1 doesn't. Big time streamers are all dealing with trying to be profitable; more overhead costs is not what any of them are largely looking for right now.

By some reports H.266 gets to 'better' compression via 'bigger' implementation footprint. That doesn't really bode well for rapid displacement of AV1 either. More GPUs are in big race for higher frame rates , more RT , more AI , etc. All 'hungry' to eat up transistor budgets. And even bigger media encoder that adds to base unit working die costs.

AV1 is common across all modern contemporary GPUs ( AMD, Intel, Nvidia , Qualcomm , and now even Apple.)
[ Qualcomm arring late also.
] Given that AV1 is present in most phones going forward and phones are the highest deployed end user devices (more so than classic PC form factors), the inertia is pretty high at this point.

The legacy bulk of the older phones with just H.264 is just as much a hurdle for H.266 as it is for AV1. H.266 doesn't really have any huge advantage there at all.
 

deconstruct60

macrumors G5
Mar 10, 2009
12,493
4,053
h.266 may have some specific use for the AVP, as it supports things like 360-degree video, and other features useful for VR. I don't know how AV1 stacks up compared to that.

H.266 and virtual reality isn't going to take over the smartphone market. That is where the end user volume is. Hence what is going to have the largest deployment/distribution inertia in the interim future.

H.266 having deeper traction into a relatively very narrow niche is not going to do much to displace AV1 in the general market.
 
  • Like
Reactions: Populus

name99

macrumors 68020
Jun 21, 2004
2,410
2,320
Now I’m curious about h.266. Is it really around the corner? From what I see, most people keep using h.264 and the tests I’ve done with h.265 doesn’t provide a big improvement. I find it a bit disappointing, that’s why all my hopes were in a standard just like the AV1.
h.265 is generally considered to take about 40..45% less data at the same quality level. OF COURSE whether you will see this or not depends on many things, like quality of the encoder and what you define as "same quality level".
h.266 is generally considered to take about 30% less data than h.265

h.265 is widely (for some definition of widely...) used in broadcast, in the US as part of ATSC3 (ie 4K broadcast TV). The quality improvement, relative to ATSC (ATSC2 never launched), is obvious, but doesn't really answer the question since ATSC is based on MPEG2, so really behind the game.

h.266 is not widely used for anything. It was only finalized in 2020.
There are plenty of reasons to believe it's superior to AV1, and no reason not to believe this.
Unfortunately there are also plenty of reasons to believe that adopting it will result in (at some point) some sort of messy legal fight. The current situation seems to be that
- two patent pools exist (always a promising sign, compared to just one patent pool...)
- everybody involved in the Access Advance patent pool seems to be living in an alternate reality where Cable TV actually matters, and defining a standard for Cable TV is the path to riches and dominating the tech industry. They seem to be unaware that what actually matters is internet streaming, phones, and the costs/terms of licensing to the tech industry.

My guess is this will play out pretty much the same as h.265, with one difference.
Same as h.265 in that Apple will pay for licenses and given the Apple ecosystem an easy-to-use high quality coded. Everyone else will refuse to pay.
Difference is that this time round, AV1 is available as a DECODE codec (AV1 sucks even more than the alternatives as an encode codec for recording your home video...) AV1 is good enough for the purposes of watching Netflix, which is why Apple supports it, and where, I suspect, Apple expects it to be used.
In the past, as the sheer incompetence behind h.265 licensing became apparent, eventually (after too many wasted years) things cleared up and it became viable for everyone who isn't Apple. You'd like to think this would happen faster with h.266, especially given AV1. But since these people all seem to think cable TV is where it's at, their connection to reality appears tenuous at best.
Honestly when I read the legal wranglings around creating these patent pools, they read to me like lawyer authors rolling their eyes and thinking "OMFG, I cannot believe these morons have STILL learned nothing from their successive disasters with every previous licensing regime" even as they very politely write things like "the licensing environment remains challenging, and license administrators continue to consider new models".

My PERSONAL beliefs are
- h.266 already exists on Apple chips, certainly as decode for two or three generations, probably as encode from at least A16 onward
- it will be announced (and visible ecosystem wide, like h.265) when two conditions are met
+ there has to be a large enough fraction of ecosystem support. This MAY be a problem with Intel macs, but I suspect overall we're at that point already
+ the licenses have to be settled; and my guess is this is still, ridiculously, being negotiated.

- right now I suspect AV1 decode support, as I said, exists only so that iPhones and MBA's can play Netflix at low power. BUT if the licensees of h.266 really cannot get their act together, I could see Apple also providing AV1 encode (a less desirable option because it's just not as good a codec – but not being allowed to use it is the single worst feature in any codec...)
 

Confused-User

macrumors 6502a
Oct 14, 2014
852
988
H.266 and virtual reality isn't going to take over the smartphone market. That is where the end user volume is. Hence what is going to have the largest deployment/distribution inertia in the interim future.

H.266 having deeper traction into a relatively very narrow niche is not going to do much to displace AV1 in the general market.
Agreed, I was talking about what Apple might choose to do though. If H.266 has significant advantages for A/VR, that could be a significant factor in Apple's decisions about what to support and implement.
 

vigilant

macrumors 6502a
Aug 7, 2007
715
288
Nashville, TN
Actually, I agree that, at least with the case of the A17 GPU, they had to pull it back from the A16 because of the high temperatures. At least according to the leaks. So yes, in this case they had the fallback plan of splitting the A16 gen into the A16 and the A17 with a more efficient manufacturing process. However, I personally don’t think this is the case for all the features, hardware or software ones.
I was talking to someone about this back when the Fire tablets were all the rage because they had slightly more high resolution screens than the iPads. Just because something is hardware “ready” doesn’t mean it’s ready at Apple level of “scale”. On Software, I think it’s the same way. Stage Manager for instance, in it’s first public release was buggy, and everyone on Podcasts say they’ll never use Stage Manager. I’ve been using Stage Manager on my iPads and Macs, and while yes the first release was buggy, just about all of the issues are gone. The stuff that I’m not so happy about is minor things that probably no one else would notice.

Thats the big thing I’m saying. I don’t think Tim Cook wants a first impression of any first iteration of any of their features or products to question the overall quality. Do things slip through the cracks? Of course they do! But I think the disciplined approach of not showing anything until it’s “mostly ready” is a good move. If you’re in the Beta group, you obviously know it isn’t going to be perfect.
 
  • Like
Reactions: Populus

Populus

macrumors 603
Aug 24, 2012
5,941
8,411
Spain, Europe
h.265 is generally considered to take about 40..45% less data at the same quality level. OF COURSE whether you will see this or not depends on many things, like quality of the encoder and what you define as "same quality level".
h.266 is generally considered to take about 30% less data than h.265

h.265 is widely (for some definition of widely...) used in broadcast, in the US as part of ATSC3 (ie 4K broadcast TV). The quality improvement, relative to ATSC (ATSC2 never launched), is obvious, but doesn't really answer the question since ATSC is based on MPEG2, so really behind the game.

h.266 is not widely used for anything. It was only finalized in 2020.
There are plenty of reasons to believe it's superior to AV1, and no reason not to believe this.
Unfortunately there are also plenty of reasons to believe that adopting it will result in (at some point) some sort of messy legal fight. The current situation seems to be that
- two patent pools exist (always a promising sign, compared to just one patent pool...)
- everybody involved in the Access Advance patent pool seems to be living in an alternate reality where Cable TV actually matters, and defining a standard for Cable TV is the path to riches and dominating the tech industry. They seem to be unaware that what actually matters is internet streaming, phones, and the costs/terms of licensing to the tech industry.

My guess is this will play out pretty much the same as h.265, with one difference.
Same as h.265 in that Apple will pay for licenses and given the Apple ecosystem an easy-to-use high quality coded. Everyone else will refuse to pay.
Difference is that this time round, AV1 is available as a DECODE codec (AV1 sucks even more than the alternatives as an encode codec for recording your home video...) AV1 is good enough for the purposes of watching Netflix, which is why Apple supports it, and where, I suspect, Apple expects it to be used.
In the past, as the sheer incompetence behind h.265 licensing became apparent, eventually (after too many wasted years) things cleared up and it became viable for everyone who isn't Apple. You'd like to think this would happen faster with h.266, especially given AV1. But since these people all seem to think cable TV is where it's at, their connection to reality appears tenuous at best.
Honestly when I read the legal wranglings around creating these patent pools, they read to me like lawyer authors rolling their eyes and thinking "OMFG, I cannot believe these morons have STILL learned nothing from their successive disasters with every previous licensing regime" even as they very politely write things like "the licensing environment remains challenging, and license administrators continue to consider new models".

My PERSONAL beliefs are
- h.266 already exists on Apple chips, certainly as decode for two or three generations, probably as encode from at least A16 onward
- it will be announced (and visible ecosystem wide, like h.265) when two conditions are met
+ there has to be a large enough fraction of ecosystem support. This MAY be a problem with Intel macs, but I suspect overall we're at that point already
+ the licenses have to be settled; and my guess is this is still, ridiculously, being negotiated.

- right now I suspect AV1 decode support, as I said, exists only so that iPhones and MBA's can play Netflix at low power. BUT if the licensees of h.266 really cannot get their act together, I could see Apple also providing AV1 encode (a less desirable option because it's just not as good a codec – but not being allowed to use it is the single worst feature in any codec...)
Many thanks for this extensive explanation. I end up learning a lot reading this forum.

Keep in mind that when I show interest in codecs and hardware encoding or decoding, aside from streaming services, I’m mainly interested in Handbrake being fast and efficient. If you say AV1 is not that great as a codec for encoding vídeo, then I don’t have as much interest as I used to have in it.
 
  • Like
Reactions: caribbeanblue

vigilant

macrumors 6502a
Aug 7, 2007
715
288
Nashville, TN
Many thanks for this extensive explanation. I end up learning a lot reading this forum.

Keep in mind that when I show interest in codecs and hardware encoding or decoding, aside from streaming services, I’m mainly interested in Handbrake being fast and efficient. If you say AV1 is not that great as a codec for encoding vídeo, then I don’t have as much interest as I used to have in it.
AV1 to me at least always think was inevitable.

Apple is a key patent holder with h.264, and h.265 so they benefit every time someone distributes their tech (I’m sure there are very specific patent, legal, and technical ways to get past this, but I’m not that guy). The funny thing with both 264 and 265 Microsoft used to charge extra to use these codecs because of the patent royalty that goes to the consortium.

Believe me, I’m going off of memory, so I’m going to get some of these details wrong. There was a codec that I think Google acquired the company behind a codec called VP9 or VP8 (at that time). Their big reason, at least from what I understand (not a lawyer or patent attorney) was they wanted YouTube to use a royalty free codec so they wouldn’t have to pay for the content storage.

The thing that I still don’t understand, is while I understand wanting to not pay a patent, it wasn’t like the MPEG (consortium behind H.264/H.265) wasn’t really that bad. If memory serves me correctly, the licensing fee maxes out at $1 million per year.

AV1 is a more open version that started from the VP line. I believe it’s 100% open source? I stopped following this stuff that closely when I got married.
 

name99

macrumors 68020
Jun 21, 2004
2,410
2,320
AV1 to me at least always think was inevitable.

Apple is a key patent holder with h.264, and h.265 so they benefit every time someone distributes their tech (I’m sure there are very specific patent, legal, and technical ways to get past this, but I’m not that guy). The funny thing with both 264 and 265 Microsoft used to charge extra to use these codecs because of the patent royalty that goes to the consortium.

Believe me, I’m going off of memory, so I’m going to get some of these details wrong. There was a codec that I think Google acquired the company behind a codec called VP9 or VP8 (at that time). Their big reason, at least from what I understand (not a lawyer or patent attorney) was they wanted YouTube to use a royalty free codec so they wouldn’t have to pay for the content storage.

The thing that I still don’t understand, is while I understand wanting to not pay a patent, it wasn’t like the MPEG (consortium behind H.264/H.265) wasn’t really that bad. If memory serves me correctly, the licensing fee maxes out at $1 million per year.

AV1 is a more open version that started from the VP line. I believe it’s 100% open source? I stopped following this stuff that closely when I got married.
Yeah, when I look at the licensing numbers they don't seem that high to me.

Maybe it's more a nibbled to death situation? Every tech company is worried that if they make licensing of this sort "easy", they will land up being compelled to buy five hundred "small (only 50c, only $1)" licenses for every damn thing. License for the idea of voice assistance. License for the idea of using a language in a web browser. License for the idea of showing weather on a phone screen. etc etc etc. The only way to avoid this is to make every fight so painful that only the most determined opponents persist?

I do think the codec patents incorporate real value, at a cost that is justified (unlike many MANY patents). But it seems that so many business, and especially legal, situations are as much about signaling as they are about the real numbers. And to some extent I can't blame businesses. I've been horrified at the crap that juries have been willing to certify as valuable patents worth a fortune; and if juries are going to behave that way, I can see why companies simply don't care whether the patent is "good value for money" or not; there's a larger principle at stake in each of these battles.
 

vigilant

macrumors 6502a
Aug 7, 2007
715
288
Nashville, TN
Yeah, when I look at the licensing numbers they don't seem that high to me.

Maybe it's more a nibbled to death situation? Every tech company is worried that if they make licensing of this sort "easy", they will land up being compelled to buy five hundred "small (only 50c, only $1)" licenses for every damn thing. License for the idea of voice assistance. License for the idea of using a language in a web browser. License for the idea of showing weather on a phone screen. etc etc etc. The only way to avoid this is to make every fight so painful that only the most determined opponents persist?

I do think the codec patents incorporate real value, at a cost that is justified (unlike many MANY patents). But it seems that so many business, and especially legal, situations are as much about signaling as they are about the real numbers. And to some extent I can't blame businesses. I've been horrified at the crap that juries have been willing to certify as valuable patents worth a fortune; and if juries are going to behave that way, I can see why companies simply don't care whether the patent is "good value for money" or not; there's a larger principle at stake in each of these battles.
Thats honestly the thing that I still to this day can’t understand.

Unless theres another tier for large companies $1 million max is much cheaper than hiring 50 engineers to work on developing a new codec, getting partner relations to convince SOC vendors to have dedicated encode and decode blocks, and the like.

Heck, it’s arguable that Apple could give Google a $1 million discount on their profit sharing deal for search if they just standardized on H.265.

Developers need to be paid. It’s really hard developing from a tent town under the bridge with no WiFi. The licensing rate seemed so reasonable (unless there was another tier) that it’s literally cheaper than hiring a team to build something up and do the maintenance on it’s code base every year.
 

Confused-User

macrumors 6502a
Oct 14, 2014
852
988
I do think the codec patents incorporate real value, at a cost that is justified (unlike many MANY patents). But it seems that so many business, and especially legal, situations are as much about signaling as they are about the real numbers. And to some extent I can't blame businesses. I've been horrified at the crap that juries have been willing to certify as valuable patents worth a fortune; and if juries are going to behave that way, I can see why companies simply don't care whether the patent is "good value for money" or not; there's a larger principle at stake in each of these battles.
I don't think that's the issue. My guess is that this is about building a rich ecosystem. Google doesn't give a damn about the $1M to license h.266 (or whatever it is). Their priority is to reduce creator friction, and anything else that increases use of their product.

Thing is, they can't do that on their own. They can build plenty of tools, but what they really need is a whole ecosystem. Lots of little devs and even part-time shareware authors, all filling tiny little niches too small for google to serve (or even notice). Pioneers willing to gamble on creating whole new categories of products, using Google for their infrastructure.

You won't see an ecosystem nearly as rich for a standard that requires payments, like h.265 (and now h.266), as you will for a free one, at least in the short term, and unless someone puts an elephant's thumb on the scale, likely not ever.

Edit to add: The other reason I doubt your reasoning on this is that just because a standard is declared patent-free doesn't mean it is. While there's a legal defense fund for AV1, that's still going to be a consideration that weighs into decisions about where to focus R&D for some, maybe many, companies. After all, this is why EVC exists. (Though, hm, I never hear anyone talk about that.)
 
Last edited:

Xiao_Xi

macrumors 68000
Oct 27, 2021
1,627
1,101
If memory serves me correctly, the licensing fee maxes out at $1 million per year.
The fees seem much higher and very confusing, as there seems to be more than one patent pool.

StandardAVCHEVC
Licensing groupMPEG LAMPEG LAHEVC AdvanceVelos estimateTotal estimate
Number of WW Patents3,7044,4173,3213,20010,938
Handset royalty ($) – highest rate$0.20$0.20$0.65$0.75$1.60
$ per 1,000 patents for handset$0.05$0.05$0.20$0.23$0.27
Handset cap$10 million$25 million$30 millionUnknown$55 million plus
Sample total royalty for 10 million units$1.5 million$2.0 million$6.5 million$7.5 million$16.0 million
 

deconstruct60

macrumors G5
Mar 10, 2009
12,493
4,053
The fees seem much higher and very confusing, as there seems to be more than one patent pool.

That is just the end users "headset" side. I think the 'broadcasters' has fees to pay also.

" ...

H.265 (HEVC)

.... Subscription-based royalties cost $0.025/subscriber. Despite these high licensing costs, HEVC is the second most popular codecs around.
..."


So you are Youtube and your average subscriber is directly paying $0.00 and you have 1B subscribers. Kind of adds up. If presumably a yearly cost if based on "per subscriber" (since subscribers change over time) over 5-10 years that also adds up.

Why is H.266 focused on 'Cable TV'. because that is where the bigger pot of money is. It isn't about selling 'one-off' pieces of individual hardware.
 

MayaUser

macrumors 68040
Nov 22, 2021
3,177
7,196
So, no longer until we find more about M3...Monday
I hope its not an event called that way just for some kind of M2 macs
 

name99

macrumors 68020
Jun 21, 2004
2,410
2,320
That is just the end users "headset" side. I think the 'broadcasters' has fees to pay also.

" ...

H.265 (HEVC)

.... Subscription-based royalties cost $0.025/subscriber. Despite these high licensing costs, HEVC is the second most popular codecs around.
..."


So you are Youtube and your average subscriber is directly paying $0.00 and you have 1B subscribers. Kind of adds up. If presumably a yearly cost if based on "per subscriber" (since subscribers change over time) over 5-10 years that also adds up.

Why is H.266 focused on 'Cable TV'. because that is where the bigger pot of money is. It isn't about selling 'one-off' pieces of individual hardware.
Except there just isn't that pot of money in Cable TV any more...
They seem well aware that their subscribers are mostly over 60 and dying off, and that the most sensible way to run the business is to extract every last dollar they can from it, but not bother to improve anything.
As far as I can tell (from my limited interaction with Spectrum about a year ago) they were still using MPEG2 for their codec (so no need to buy new encoder hardware or provide new decoder boxes), and they seemed throughly uninterested in such modern features as 4K or HDR.

I'd have though the sensible business play is
(a) get companies like Netflix on board with the win being "yes you pay us 25c one time, but then look at how your bandwidth savings add up over time" (and the bandwidth savings for 266 relative to either 265 or AV1 are real). This is even true for YouTube.

(b) with Netflix et al on board, get the hardware manufacturers (TV, phone etc) on board with something like "this is going to be Netflix' preferred codec going forward, so it's going to provide the best quality for your customers".

Going to cable TV seems crazy to me. They're going to laugh and you and tell you "we haven't invested a dime in this business since 2017, and we don't intend to start doing so now"!
 

MayaUser

macrumors 68040
Nov 22, 2021
3,177
7,196
So people speculating that Monday we will get not just M3 but also at least M3 Pro, but also M3 Max is not out of the question
 

Attachments

  • Screenshot 2023-10-24 at 19.48.27.png
    Screenshot 2023-10-24 at 19.48.27.png
    1 MB · Views: 69

MayaUser

macrumors 68040
Nov 22, 2021
3,177
7,196
M3 24" iMac
M3 MacBook Pro (w Touch Bar)
M3 Pro/Max - MacBook Pro 14" and 16"

Probably 50% chances to see
M3 and M3 Pro - Mac Mini ***
M3 13" and 15" Macbook Air ***
 

MayaUser

macrumors 68040
Nov 22, 2021
3,177
7,196
It is possible that the event will focus on prosumer chips. At this point I wouldn’t be surprised if M3 ships in spring.
Gurman said imac....so, either we will get M3 imac or M2 iMac but that would be a prank from tech savy point of view
 
  • Like
Reactions: Chuckeee
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.