Skip to main content
MOGRT Yogurt
Participant
Oct 12, 2023 1:46 AM UTC
Not Prioritized

Bring Back Rosetta Support

Adobe have scrapped support for Rosetta moving from the Adobe Premiere Pro CC 2024 update.

 

As per consultation with an Adobe support agent, I was told that while the CCDA (Creative Cloud Desktop Application) still shows the ability to open using Intel, this still runs in M1 (MAC ARM) mode only.

 

This is confirmed in the Known issues in Premiere Pro Knowledgebase article here:

https://helpx.adobe.com/premiere-pro/kb/known-issues.html#sa_src=web-messaging

 

This means that plugins that were developed prior to the relatively recent release of M1/M2 systems, can no longer be used with Adobe Premiere Pro. This is a huge loss.

 

While I understand that this was probably done in order to make performance improvements, please reconsider or find a different way to allow Premiere Pro to be booted in Rosetta mode, if a Premiere Pro user would like to boot with that option and have it remembered with the "Open using Rosetta" checkbox on macOS.

 

Cheers!

 

    This topic is closed to new replies. Start a new post to keep the conversation going.

    13 replies

    Community Manager
    Kevin-MonahanCommunity Manager
    Community Manager
    Oct 26, 2026 8:54 PM UTC
    Updated idea statusOpen for Voting→Not Prioritized
    Translate
    Community Manager
    Kevin-MonahanCommunity Manager
    Community Manager
    Oct 26, 2026 8:19 PM UTC

    Premiere will no longer run on Intel-based CPU machines. Therefore, this feature request is closed.

    Translate
    burtonm14765516
    burtonm14765516
    Participant
    Feb 21, 2024 11:24 PM UTC

    I haven't updated. I'm still using 2023. But the Wrator DCP encoding doesn't work very well. Using Rosetta and the rendering will freeze. Has anyone else had this issue? I'm using a MAC Mini with M2. 

    Translate
    Warren Heaton
    Community Expert
    Warren HeatonCommunity Expert
    Community Expert
    Dec 29, 2023 7:22 PM UTC

    @Jose33521536xxd4 

     

    For Wraptor DCP Lite, you would want to export a ProRes file from your 2024 Timeline and add that to Media Encoder 2022 using Rosetta.  It doesn't need to be ProRes, any mezzanine CODEC is fine.

    Media Encoder 2024 and 2023 can be installed at the same time.

    Hopefully, we'll see an Apple Silicon native version of Wraptor DCP Lite soon.

     

    Another option is to rent Wratpor 4.2 for one month from QuVIS ($100 US dollars).  It's Apple Silicon native.

    Translate
    alppu
    Participant
    Nov 10, 2023 4:53 PM UTC

    How I noticed this? I was on location and did first versions for a client with my updated i7 macbook. Came back to my office and tried to open a project on studio ultra, "you need to upgrade 2023 -> 2024" and *kaboom*..

    Translate
    alppu
    Participant
    Nov 10, 2023 4:41 PM UTC

    This really sucks, my old i7 macbook pro 2019 works ok with old plugins but my m1 studio ultra doesn´t.

    Translate
      Jose33521536xxd4
      Participant
      Nov 10, 2023 8:00 AM UTC

      Hi.  After updating to Premiere and encoder 2024, has anyone have had the same issue of the wraptor DCP option missing when exporting? I still have 2023 versions on my system which still has the wraptor DCP option. but just annoying. Ticking rosetta was the usual fix for this issue.

      Translate
      R Neil Haugen
      R Neil Haugen
      Legend
      Oct 17, 2023 5:42 AM UTC

      I'm totally PC, but dropping Rosetta on the Macs has to hurt ...

      Translate
      Everyone's mileage always varies ...
        MOGRT YogurtAuthor
        Participant
        Oct 17, 2023 5:03 AM UTC

        You make some good points Neil! Although, I must say, I didn't get the memo that Adobe was going to drop Rosetta support this time around.

        Although I believe this has happened in a previous update, and it was brought back. Perhaps that was a sign of things to come. But everything is easy to see in retrospect.

        Translate
        R Neil Haugen
        R Neil Haugen
        Legend
        Oct 16, 2023 2:10 AM UTC

        No software maker is responsible for every third party plugin that may be used by some users working with their system. They give out the 'calls', which Adobe is pretty generous about, compared to other apps I use. But they can't hold back the app because some plugin doesn't work well with the new version.

         

        And yea, I use some spendy ones. Maxon/Red giant full suite, some Autokroma, several others. So I understand wanting the plugins to work. But that is the job of the plugin maker.

         

        Just reality.

        Translate
        Everyone's mileage always varies ...
          Show more replies
          Terms & ConditionsAccessibility statement
          Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices