I don't use any plugins. I think video editing is one of the areas likely to benefit most from Apple Silicon due to the hardware video encoders and decoders, so high performance would not surprise me.
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.
Universal and Native Apple Silicon Apps
- Thread starter arn
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I think the real challenge for apps to be compatible with arm is the dependent 3rd party components. For example, I can figure out how to compile my main app to work with arm, but my app uses a bunch of third party components that's based on Intel, that will stop my app from running as native.
I didn't see anything about x64 emulation in that VMWare announcement. Perhaps I am missing something?Well I read the announcement that way (that they emulate an x86/x64). Because announcing that existing VMWare ARM VMs would run on AppleSilicon would not really be exciting to anyone - unless you are very easily excited.
Apple already showed ARM linux in Parallels on Apple Silicon at their first presentation.
I wouldn't say years. Apple has somewhat committed themselves to a two-year transition. So pro and non-pro applications will have to push out an update sooner or later. And I think we shouldn't underestimate (nor overestimate) Rosetta 2.
Out of curiosity, will this thread also document iOS/iPadOS apps that will be known to run on an M1 Mac or would that be a separate list?
From Serif,
https://affinity.serif.com/en-us/apple-m1-chip-support/
Photo, Designer and Publisher are native M1, Big Sur apps.
https://affinity.serif.com/en-us/apple-m1-chip-support/
Photo, Designer and Publisher are native M1, Big Sur apps.
Last edited:
Plus a decent number of apps require use of the specialized device hardware (like motion sensors) or multitouch input; the latter would take some rework to code in workarounds.
Office will be running natively, not under emulation. Microsoft already had it running natively at WWDC, and they released the first builds to Beta/Insider today. All of the Apple apps have already been recompiled for the M1, so FCP, Compressor, Motion, etc. will be available as native apps on day one.
If the developer wants their app in there, the app will show up in the Mac App Store if you’re on ARM. However, many devs have opted out (at least for now), like Facebook.
No, you won’t be able to install iOS on an ARM Mac. Not sure why you’d want to, since the Mac isn’t optimized for a touch interface.
Mathematica
Matlab
Maple
Not yet available for 10.16; no mention of Apple Silicon (https://www.maplesoft.com/products/system_requirements.aspx)
Matlab
Maple
Not yet available for 10.16; no mention of Apple Silicon (https://www.maplesoft.com/products/system_requirements.aspx)
"Years" plural? Nah, I'm feeling majority within the first year.
i) STATA 16 for MAC is compatible with Apple Silicon https://www.stata.com/products/mac/
ii) R & R Studio will probably work but not entirely clear https://developer.r-project.org/Blog/public/2020/11/02/will-r-work-on-apple-silicon/index.html
ii) R & R Studio will probably work but not entirely clear https://developer.r-project.org/Blog/public/2020/11/02/will-r-work-on-apple-silicon/index.html
I consider porting existing apps to M1 using the native XCode for ARM to be an example of being highly productive doing very relevant work!
Interesting - that would be really annoying if a lot do. My primary hope as an iPP 12.9 2018 owner who doesn't want to keep buying all the iPP accessories, and wants a real multi-tasking O/S that doesn't close every app in the background every time I switch to YouTube, is that the MBA can do this, and I would have access to all my purchased iPad games, like Civ VI and Company of Heroes (I like them strategy titles).
Dumb question time again. For most Mac apps, how hard would it really be to produce a universal or M1-native binary? I get that fully optimizing to the new platform and taking advantage of all of its features will take time, but unless you've got code that's really working down at the machine instruction set level, isn't this just re-compile, test, and upload to the App Store? (Or however else you choose to distribute.)
Get it done, get it out there, and by actually compiling for the platform instead having to have Rosetta translate, you'll almost certainly be more efficient than if you just stayed x86 and let Rosetta handle it. Boom, you're native, and you can improve over time through normal updates as you optimize for the M1.
Get it done, get it out there, and by actually compiling for the platform instead having to have Rosetta translate, you'll almost certainly be more efficient than if you just stayed x86 and let Rosetta handle it. Boom, you're native, and you can improve over time through normal updates as you optimize for the M1.
Final Cut Pro X, Motion, Logic Pro, Compressor (all the Apple consumer and Pro apps, for that matter) are already available on the M1, and Microsoft dropped their Office beta this week. Adobe has stated that Lightroom will drop next month and Photoshop in early 2021. You also have apps such as DaVinci Resolve, the Affinity apps, and numerous others that are making their way over to the M1 in the next few months. So the options for "anything productive" are already out there. Plugin issues (as always) would have to be addressed by the plugin authors, not the software developers. Keep in mind that a lot of these developers have been waiting on the new hardware to actually release, especially since there are some limitations to the DTK which prevent certain types of software from being developed since the DTK does not support features such as virtualization. With production hardware in hand, these developers can actually start working on porting those types of apps to Apple Silicon.
yes I understand all that. But obviously any person who rely on their computer to work with specific softwares would wait at least a few months for the major kinks to be ironed out; and make thorough research about what works and what doesn't. As for the plug-ins; it could take very long for them to be adapted; and I don't see an ecosystem with a mix and match of native/emulated plug-ins/apps working well if at all. Personnaly I use max/msp and ableton live in conjonction; plus multiple third-party plugin; and all of those have to be updated to work together; and I know for a fact at least one I rely heavily on will never be. I don't even know about the drivers of the many pieces of hardware I use. I don't even know about firewire compatibility if there is any. I suspect many people are in the same cases. Your mileage may vary but for me it won't even be an option for a very long time.
optimized yes, but runs like a champ without touch, with mouse support. And as far as wanting this? Heck yes! ?
why not? But you’re going to have the naysay no doubt.
Well iPadOS already runs with mouse and keyboard like a champ, so there’s that. But I think the overall goal should be “let’s get those apps over to MacOS, and use them back and forth, seamlessly”.