Except Apple's PPC to Intel transition had agreements with Intel where Apple's CPU patents (AltiVec) we then opened to Intel and Apple probably got access to Intel's portfolio. It's why an AMD Mac was never an option.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Rosetta May Be Removed From M1 Macs in Some Regions on macOS 11.3
- Thread starter MacRumors
- Start date
- Sort by reaction score
Not that intellectual property likely has anything to do with this issue, but even Intel needs AMD’s license. To the extent that apple needed Intel’s blessing for Rosetta II (which is not at all clear - the law is mixed on the issue of whether op codes are subject to copyright protection, and I’m not aware of whether there are any relevant patents), it would also need AMD’s - after all, the entire 64-bit instruction set is AMD64, not Intel64 (and rosetta doesn’t support 32-bit, 16-bit, or 8-bit code, which would be Intel’s bailiwick).
Except he was upper management at Apple during the PPC to Intel Transition
Thanks. I'm pretty sure I didn't miss it, just that it never happened. Maybe the Migration Assistant did it's thing.
This is where Apple made a *major* mistake in the whole M1 chip transition. The whole purpose behind using the Intel processor was Boot Camp and the ability to run Windows OS and software on the same computer -- to hopefully increase their market share and presence in the Office/Work Environment.
Parallels and other VM apps took it even further -- you can run Windows and multiple Mac OS installations without having to reboot the computer.
Parallels and other VM apps took it even further -- you can run Windows and multiple Mac OS installations without having to reboot the computer.
Or maybe Apple soon applied this to all region basically, instead of "certain region". Apple literacy is always vague at it best, e.g affected some users, certain region, etc.
Well at some point eventually Rosseta2 would stopped by Apple, but I didn’t expect to come so early (few months?) with excuse of region restrictions.
Well at some point eventually Rosseta2 would stopped by Apple, but I didn’t expect to come so early (few months?) with excuse of region restrictions.
I'm laughing. I got "back into Mac" ("Bye-bye Apple PC's; don't let the door hit you on the way out!"), with the pure desire to be 100% M1-native. I've had to use, I think, 1 Intel app since getting my M1 Mac Mini. Not gonna miss Rosetta 2. I've deliberately made sure I'm only running M1-native apps this entire time... and loving every minute of it!
This is just a placeholder in case of disputes and sanctions 👈
it’s not being activated 👍
For the 100th time this year you all fighting over nothing burger 😛
You could use the same time and energy to eat a real burger 🙌 🍔 🙌
it’s not being activated 👍
For the 100th time this year you all fighting over nothing burger 😛
You could use the same time and energy to eat a real burger 🙌 🍔 🙌
Open up System Information, Scroll down to Software then Applications. There you will see a list of all apps and those that are Intel only.
I can only imagine one scenario where this makes sense: that Rosetta 2 is using some underlying 3rd party technology that involves patent royalties that is subjected to expiry, and probably have different licensing rights territories. If Rosetta 2 is 100% in-house tech I have a hard time thinking how this would benefit Apple itself.
(IIRC, The PPC to Intel transition where we had Rosetta 1, also was cut short by only getting something like 2 more OS X point release until I think 10.7 Lion. This upset people who rely on PPC apps that saw no chance of being ported to x86, but Apple had a legit reason in that Rosetta 1 included tech licensed through a company that was later acquired by IBM after the Mac x86 transition. Apple decided not to renew license for further OS X deployment probably due to change of terms)
(IIRC, The PPC to Intel transition where we had Rosetta 1, also was cut short by only getting something like 2 more OS X point release until I think 10.7 Lion. This upset people who rely on PPC apps that saw no chance of being ported to x86, but Apple had a legit reason in that Rosetta 1 included tech licensed through a company that was later acquired by IBM after the Mac x86 transition. Apple decided not to renew license for further OS X deployment probably due to change of terms)
If Apple does do this, people must be able to return their unit for a full refund, with absolutely no hassle, no matter when they bought it.
OneDrive as well, despite the rest of MS Office being Apple Silicon native.
It's no coincidence that Rosetta came out not supporting AVX. It's highly unlikely there isn't enough smarts in Apple to translate such instructions. More like it's some of the more obvious ones that patent lawyers say it won't clear litigation — and little used in macOS apps (notably since Accelerate framework provides good equivalents).
Did anyone actually experience Rosetta being disabled after tis update? Or are these 7 pages of angry comments literally based on someone literally discovering a string in some memory dump? Are you folks sure you are not massively overreacting over a knee-jerk?
It's not about the most popular ones, but those apps millions of people use daily that aren't M1 native. Duh..
Pretty much all of our studio software -- Pro Tools, Ableton, last I checked Notion didn't, and Finale doesn't even launch. I think maybe two of the VSTs we use have been converted, which only leaves a couple dozen to go. We don't even have audio interface drivers yet; thankfully AVB works, other than a kernel panic every time the computer tries to sleep.
It's gonna be a while...
The story is a nothing burger for any developer who knows the score.
When developers have any problem then Apple sends engineers to help them update their tools and apps.
Always been like this.
Major current example: Apple is directly helping the Blender community right now and version 2.93 final will be Apple Silicon ready.
It's probably already said a few times around here but that message has been popping up for some people before and is resolved by restarting your mac. Stupid they didn't patch it yet but they probably will now it's all over the internet. See: https://discussions.apple.com/thread/252157153