Red Giant and Premiere Pro 14.1

Apr 23, 2020 2807 18 Share
Red Giant Team
Red Giant Team

Hey folks – Adobe just released Premiere Pro 14.1, and while we know you want to jump into that update, if you are a customer using either Magic Bullet Colorista or Universe, we are advising you not to update at this time. If you have already updated your version of Premiere Pro, we recommend that you roll back to the previous version, 14.0.4.


Unfortunately, there is an issue with the Adobe Premiere Pro 14.1 update that causes our Colorista Panel and Universe Dashboard not to function. We are sorry for any trouble this causes you. We know how important your Red Giant tools are to your workflow.


Here’s some good news though – Red Giant has a close relationship with Adobe and we are working with them to ensure there is a fix for this problem as soon as possible. In the meantime we’re also looking into possible workarounds and hope to release a Universe update very soon.

Unfortunately, for Magic Bullet Colorista, we are unable to work around the issue directly, but we are working on an update that will automatically disable the panel if you are on Premiere Pro 14.1. You can always use the standard effects panel until a fix is available.

We’ll keep you posted. Stay tuned.

As always, if you have any questions, our support team is here for you.

Post a Comment

Sign In to Post a Comment


  1. A good rule of thumb: Never update an Adobe product in the middle of a project. Thank you for the heads up.

  2. So… considering you have not updated the program/suite in 3 years (MAGIC BULLET SUITE 13) … Is there a NEW version coming soon? 14 or 13.5 or something that will run better? LONG TIME… PAID USER…

    1. We have been working very hard on a lot of new things for this year. Although I do not have dates available, I strongly urge to keep up to date with our newsletter for any new releases, tutorials and inspiration.
      We appreciate your patience.


  3. Does this also affect AE?

    1. As far as we are aware, it is only PPro.
      If you are having any issues within AE, please contact our support team.


  4. Cédric Billemont April 23, 2020 at 8:08 pm

    Yep, i’m asking a lot here but why did this not come-up in test before 14.1 released?
    So far i’m good and the bug=fixes in 14.1 where the reason to move 1 version up.
    I had font issue and was not related to the bug-fix but Adobe is not transparent with its decommissioned fonts and failure to render them in Media Encoder.
    Hope you could do tests before release or in the following hours, not the following days.
    Thanks for the update, hope this will help most of us 🙂

    1. Unfortunately it looks like the framework had been adjusted between the plugin and the host in a way that went undetected until Premiere’s release, sorry for the understandable frustration.
      Keep an eye on your Creative Cloud app for a Premiere update that’ll fix the problem between the two.
      We appreciate your patience.


  5. Hey I’ve left two comments here and they’ve been entirely ignore.
    What gives?

    1. John,

      I forwarded your comments to our support team so they can help you with rolling back and any additional questions.
      We appreciate your understanding.


  6. Hope you’re able to solve it. Rolling back was easy. In the Creative Cloud app, click the 3-dot pull-down next to Premiere Pro and choose Other Versions.

  7. Gretchen Williams May 6, 2020 at 5:55 pm

    Is this still true? Will you update the Blog or send out an email when fixed? Thanks!

    1. We will let everyone know once Adobe has released a fix with a blog post and a newsletter.
      We are hoping for sooner rather then later.


    2. We just released an update:

      Hope this helps!

  8. Hey,

    Any traction on this? When can we expect an update?


    1. Once Adobe has released a fix for this issue, we will let everyone know.
      We are just as anxious as everyone else and hoping for a speedy turnaround.


  9. Hello,
    I think there is a possible “turnover” for this incompatibility problem between Red Giant plugin and Adobe 2020 (14.1) …
    Indeed, Adobe activated by default during this update its new JAVA engine and deactivated the old one which is still still present in the application!

    If you go to the debug console (CTRL + F12) and enter the DEBUG DATABSE VIEW tab, you then do a search on SCRIPT and deactivate ScriptLayerPProEnableNewWorld (it must then be in FALSE) … You then restart Adobe Premiere and everything should probably work as before.

    Try it, it’s safe … and probably works while waiting for a future update.

  10. Any word if the Premiere 14.2 update fixes this issue?