Adobe Premiere Pro, Premiere Rush, and Audition for Apple Silicon Available in Beta
Versions of Adobe Premiere Pro, Premiere Rush, and Audition that run natively on M1 Macs are now available for public beta testers.
According to an Adobe Support Community document, spotted by The 8-Bit, Adobe will launch native M1 support for all features within Premiere Pro in phases, and many parts have not yet been ported.
The first phase, included in this public beta release of Premiere Pro, features core editing functions and workflows like color, graphics, and audio, as well as Productions and multicam. Adobe has also prioritized support for the most widely used codecs, such as H.264, HEVC, and ProRes.
Adobe says that beta testers will need to initially upgrade their project files to make them compatible with the new captions workflow, and it is advised that users create extra copies of projects to use within the beta version.
Beta testers should also be aware that Adobe has released a list of known issues in the beta. For example, tapping the Tool Selector on a MacBook Pro's Touch Bar can cause the app to crash, and estimated file sizes while exporting may show incorrect values by an "order of magnitude."
While Adobe completes its M1-native version of Premiere Pro, it urges most users to run the current release version of Premiere Pro using Rosetta 2 emulation on Macs with an M1 chip.
Even when Adobe Premiere Pro is fully updated for Apple Silicon, it should be noted that third-party integrations such as panels, plugins, effects, and drivers will need to be updated by developers to run natively on Apple Silicon and may not work reliably under Rosetta 2 emulation.
In addition to Premiere Pro, Premiere Rush and Audition have also been updated to run natively on M1 Macs for public beta testers.
In November, Adobe made the M1-native version of Photoshop available in beta. Adobe Lightroom CC was updated to run natively on Apple Silicon earlier this month. The company appears to be on track to update most of its apps to support Apple Silicon in 2021.
Top Rated Comments
As for FCPX, since it's not Windows compatible, you have to make sure that no one involved in your project will be working on Windows, ever, at any point down the line. And most video editors have long transitioned to Windows due to the lack of Mac Pro updates for years, and their love for AVID, so FCPX is not even an option. With Premiere you can just send a .prproj to literally anyone and not have to care about whether they have Mac or Windows.
That's why Premiere is industry standard and FCPX and Resolve (for editing) are not. Premiere may suck absolute balls in stability and its archaic file handling system, but you can guarantee that it does what you need, and no matter how big your project gets, no matter how many audio channels you end up adding, and no matter how many unexpected people join the project, there will be a way to figure it out. With FCPX, forget it. In a professional environment it's not the prettiness, stability, or responsiveness that decides what software or equipment you use. It's the simple question: is there a way, any way, no matter how silly, to make it work with our crazy workflow? If the answer is no, then you won't be using it. If it costs more, so what, you'll just pay more for it. If it's inefficient, so what, you'll just get a computer that's 10 times more powerful. If it takes more time, so what, you'll just hire another assistant. These are non-issues. Not being compatible with your workflow, that's an issue.
"Subscription models are just a complete ripoff."
For you, yes. For others, no. Try not to sweat what works for others. I use Lightroom CC and find it to be an excellent value for how I like to manage and edit images.
The market will ultimately dictate whether software subscriptions are the right way to go for more developers. It appears to be working very well for Adobe...while at the same time providing opportunities for the likes of Resolve, FCP, Affinity's suite, etc.
As a user, I just want them all to make enough money to continue to develop (and fix bugs).
Fast forward to today, and I understand why Apple decided to start from scratch on both FCPX and Logic X. The vast under-the-hood changes in technology allowed for the adaptation of new tech over the years faster than nearly every competitor app. They’ve been able to scale up their apps for 4K, 8K, HDR, new codecs, and new hardware - while Adobe’s antiquated video engine (Mercury) has been very slow to match Apple’s speed.
I finished grad school in 2013 having learned FCP7, but also moved to Premiere like many others in the industry during that timeframe. Watching Blackmagic’s rise in the editing sphere has been a blessing. It has many of my industry peers interested, but again - it’s hard to break workflow. (Many of them joke with me about how they wasted the pandemic by not learning Resolve.) As of 3 months ago, I finally made the switch to Resolve for my own work - despite that most of the commercial agencies I work work with still use Premiere. A few of my clients also use FCPX. I’m forced to use all apps depending on the workflow needs across the board.
While I find Resolve an intuitive editor, it’s node-based system turns many people off. FCPX’s timeline and color correction tools also turn many people off. Premiere’s video engine is the only thing inherently wrong with it, and I’ve heard from many professionals that it’s just about time that they’re going to do a complete rehaul like both Apple and Blackmagic did.
I’m all for choice, but this is a hard one because all of my workflow is typically connected to someone else’s in different software. It’s a bit of a pain in the butt, and some interchangeable industry standards are still not on the same page.
But hey, aside from all that. Can Apple just add back eGPU support in their next Pro-line of Apple Silicon Macs? The video editing application debate is hot, but what’s even more challenging is the PC vs Mac debate when talking about decoding RAW video files (RED, etc.).