Skip to main content
C
camfink
Participant
December 2, 2021
Question

Filter Offline (RGB Curves) - Error since updating to v22.0.0 (Build 169)

  • December 2, 2021
  • 3 replies
  • 3979 views

I recently updated Premiere Pro to version v22.0.0 (Build 169)

 

When I load existing projects, any instance of the RGB Curves filter is now listed as Filter Offline (RGB Curves) in the effects panel, and the filter is non-functioning.

 

This means that a lot of color correction in existing projects no longer works. This is obviously VERY inconvenient! I tend to use the RBG curves filter for quick adjustments because it renders much faster than Lumetri. I can on longer make tweaks to existing edits without checking and fixing every clip that had the filter applied.

 

It seems odd to me that a filter would be disabled/offline. In other updates I've seen an "obsolete" label added, but the filter is still functional.

 

Is there a problem with how my update has treated the filters? I haven't had an "offline" error with any other filters.

 

    This topic has been closed for replies.

    3 replies

    M
    Mel Matsuoka
    Known Participant
    July 19, 2023

    Following up with a solution to this issue on Apple Silicon Macs, the solution that works for me is to launch Premiere in Rosetta 2 mode, then open the project.

     

    https://www.postproductive.tv/2023/07/12/premiere-pro-video-filter-missing-workaround-for-apple-silicon-m1-m2-macs/ 

      F
      FilmTraveler
      Participating Frequently
      May 20, 2023

      For anyone who's searching for a solution to this, installing version 22 (from the Creative Cloud apps area, click the dots and pick "Other Versions") can fix it temporarily. Obviously installing an older version will allow you to use the effects again which were present in that version... but I also made an amazing discovery:

       

      After installing the older version, the deprecated obsolete effects were also available again in the latest version of Premiere Pro! (At least in the Windows environment.)

       

      It must install these effects to some common location. I couldn't find it in any obvious place (like inside AppData) so clearly this trick will only work until I uninstall the old version. But it could be a handy band-aid for others while you transition to newer versions of effects.

      R Neil Haugen
      R Neil Haugen
      Legend
      December 2, 2021

      Are you on an M1 Mac? I know on those, some of the "obsolete" effects are gone.

       

      Actually, anymore you should be able to get the same performance if you just use the Lumetri Curves tab as you did with the RGB Curves effect. I can't tell any difference whatever in playback.

       

      Neil

      Everyone's mileage always varies ...
      C
      camfinkAuthor
      Participant
      December 9, 2021

      Whilst that's fine going forward, it is EXTREMELY frustrating to edit old projects where I've used that filter.

      Kevin J. Monahan Jr.
      Community Manager
      Kevin J. Monahan Jr.Community Manager
      Community Manager
      December 9, 2021

      As politely as I can manage, that's a pretty filmsy explanation. How hard is it to include a legacy filter? Especially as the functionality exists in a different filter in the current version. Or create an import patch that replaces that filter with an equivalent lumetri filter? 

       

      Anyway, thanks for indulging me!


      Hi Camfink,

      I think what is widely not very well understood is that maintaining every effect takes engineering cycles to do so. Since engineers are finite in number at Adobe, duplicating work is one thing that engineering managers try to avoid. Since all work on color is oriented towards Lumetri Color, the previous effects related to color no longer have these specialists available to work on them. Their managers would rather they focus efforts on the current feature set requiring their expertise. When this happens, the product team places certain effects in the Obsolete category in order to warn editors. When that happens, that is a red flag for editors to discontinue using those effects and to replace the effect with the newer version of that effect (or be prepared to do so when restoring older projects on demand). In other words, there is a point in time when an editor can no longer revive an old project without some interaction with swapping out obsolete effects, changing up workflows to meet the needs of the newer software, etc. It's a hard pill to swallow, but should be of no suprise to editors restoring old projects containing legacy effects. In my career as an editor, this doesn't happen very often as I have heeded the warning of using legacy effects, using them mainly to restore older projects and are never added anew. To reiterate, maintaining obsolete effects simply takes up too much bandwidth on the engineering side. Engineering, like any other commodity, has limits in its capacity to do work on a day to day basis.

       

      Hope my explanation makes more sense. 

       

      Regards,
      Kevin

      Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
        Terms & ConditionsAccessibility statement
        Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices