Hey everyone! With the release of Apple's new hardware, we wanted to provide some information on the performance of our beta versions on these new machines.
This does not impact installing the official release of Premiere Rush.app on the new M1 computers running the Rosetta 2 Emulation. These notes apply specifically to running the beta of Premiere Rush (Beta).app on the new Apple Silicon M1 computers released November 2020 – MacBook Air M1, MacBook Pro M1, MacMini M1
Here's the information on which features are supported on the new Apple Silicon M1 hardware when using the Premiere Rush Beta.
Now for the exports!
And everything else
We expect the majority of these features to become available in the upcoming beta releases, so check for updates in your Creative Cloud Desktop App regularly! If you have feedback or encounter issues, please share it directly with the product team on the Rush UserVoice Forum.
Hope this helps shed some light on the topic!
Me, as an actually very, very unsatisfied customer, esp. w/ Adobe Rush/its sync fuction/stability, want to ask you:
Dont you think Adode should take more care for existing customers AND the reliability/stability of its software products?
Usindg Rush is a mess, actually!
It does not stable sync, so very often projects are only able to be opened/synced from another device, which is very time consuming. It has to bee synced again from this oterh device to get it opened again on the first device and to expect the same error/behaviour again and again.
I cannot suggest Adobe at the moment; more a pitty is to be depending on this messy software.
I'm also facing challenge after challenge on this software and its support for M1 Apple Silicon. Every project that I import video to in the past two weeks imports the video with a green/pink/red block on the video. It's unusable! When I look up solutions to my problems everything is for Intel based systems and the recommendation is to check for updates and get the latest driver...but what if I'm on the latest of everything and still have this issue?
One way was to rename the file extension but even that hasn't been an effective workaround. Looking forward to a fix.