Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
2

P: Premiere 25.1-color space override not sticking after relaunch

Community Beginner ,
Jan 10, 2025 Jan 10, 2025

Premiere Pro v25.1, Windows 11.

Override of Media Color Space does not play after relaunching Premiere.  The override setting is still retained, but in order for it to display properly, you need to toggle to an incorrect color space (eg Arri Log 3 instead of Arri Log 4) and back again for it to "wake up" and display correctly.

 

In this case, I have a bunch of Log footage that is ARRI LOG C4.  Premiere does not auto detect it, but I can use the Override Media Color Space to manually select ARRI LOG C4 for the color to display properly in a REC 709 sequence.   Everything works correctly until I close the program and restart the next session.  Everything appears as LOG in the sequence, despite the setting still being retained.  Toggling to an incorrect setting and back again fixes it, but this would be cumbersome on a sequence with a lot of mixed footage.
Anyone else seeing this behavior?

Bug Fixed
TOPICS
Color , Editing and Playback
888
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Apr 01, 2025 Apr 01, 2025

Updating Status to Fixed in 25.2

Status Fixed
Translate
19 Comments
LEGEND ,
Jan 10, 2025 Jan 10, 2025

No. Could you share a clip for me and others to test?

Translate
Report
Community Beginner ,
Jan 10, 2025 Jan 10, 2025
Whats the best way to share a clip?
Frame iO?

Thanks,
John
Translate
Report
Community Beginner ,
Jan 10, 2025 Jan 10, 2025

If you are able to look at it, here is a short clip

https://f.io/8L30rb4l

Translate
Report
Adobe Employee ,
Jan 10, 2025 Jan 10, 2025

Hi @John22368521k4cl - Thank you for the test media you have provided.  I see this issue as well.  I'm going to ask the team if this is a known bug if not we will file it and get it fixed.  Thank you for your report. 

Status Needs More Info
Translate
Report
Community Beginner ,
Jan 10, 2025 Jan 10, 2025

Thank you for checking and replying.  Another thing...I'm curious as to why the media file is being misidentified as REC 709.  Other software, such as DaVinci Resolve correctly reads the metadata and flags it ARRI LOG C-4.  Not sure if its just because this method of color management is a new feature for Premiere and its not yet supported or if thats also a bug.

J

Translate
Report
Adobe Employee ,
Jan 10, 2025 Jan 10, 2025

Hi @John22368521k4cl - Currently we do not auto detect Color for Prores in an MXF container.  The Color team is working hard to bring all the features to Premiere Pro.

Translate
Report
Adobe Employee ,
Jan 13, 2025 Jan 13, 2025

Hi @John22368521k4cl - Do you see this issue if you have "Selection Follows Playhead" checked in your sequence settings?

Translate
Report
Community Beginner ,
Jan 13, 2025 Jan 13, 2025
The same thing occurs regardless of the “Selection Follows Playhead” setting.

Thanks
John
Translate
Report
Community Beginner ,
Jan 22, 2025 Jan 22, 2025

Jamie,

Any update on this bug?

Translate
Report
Adobe Employee ,
Jan 22, 2025 Jan 22, 2025

Hi @John22368521k4cl - It should be fixed in Beta in a few days I'll update this post when the build is released.

Translate
Report
Adobe Employee ,
Jan 22, 2025 Jan 22, 2025

Updating Status to Acknowledged

Status Acknowledged
Translate
Report
Adobe Employee ,
Jan 23, 2025 Jan 23, 2025

Hi @John22368521k4cl -  Adobe does not provide comments on future releases at this time.  

There is a potential fix in beta 25.2.0.90

Translate
Report
New Here ,
Feb 05, 2025 Feb 05, 2025

This is happening for me as well, even after I updated to the most recent premiere beta. 

Translate
Report
Adobe Employee ,
Feb 05, 2025 Feb 05, 2025

Hi @jordanb71019445 - Please provide system specs, specific premiere pro versions with build.  You can find that information in the about Premiere Pro, and Reproducible steps.

Translate
Report
Adobe Employee ,
Apr 01, 2025 Apr 01, 2025

Updating Status to Fixed in 25.2

Status Fixed
Translate
Report
Explorer ,
Apr 16, 2025 Apr 16, 2025
  • Issue - Lumetri Color "Override Media Color Space" does not load or display properly in the program monitor when a project is closed and reopened.

  • Steps to reproduce - Under the settings tab of Lumetri Color, change the Source Clip from "Use Media Color Space" (Rec. 709 in my case) to "Override Media Color Space" (Canon Log3/Cinema Gamut in my case). Save the project and close it. Reopen the project, and the settings will be preserved, but will still appear as if I had not performed the steps above, failing to display that change and the proper colors.

    Switching back to "Use Media Color Space" and back again to "Override Media Color Space" will fix the visual issue, and will sometimes fix other clips, "reminding" them of their color settings. Sometimes this does not happen, though, and each clip will have to be set again to display properly.
  • Adobe Premiere Pro version - Version 25.1.0 (Build 73)
  • Video format - This is working with prerendered MP4 footage, not raw anymore. Shot on a Canon C70 at 4K in Clog3 originally.

    Video example: 
    [video]
Premiere Pro 25.2.3 (Build 4) | OS: macOS Sequoia 15.5 | CPU: 3.8 GHz 8-Core Intel Core i7 | GPU: AMD Radeon Pro 5500 XT 8 GB | RAM: 16 GB 2667 MHz DDR4
Translate
Report
Adobe Employee ,
Apr 16, 2025 Apr 16, 2025

Hey Brandon,

Have you tried updating Premiere Pro? Let us know if that helps.

 

Thanks,
Kevin

 

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Status Needs More Info
Translate
Report
Explorer ,
Apr 17, 2025 Apr 17, 2025

Ah, I thought I had auto-update on. That did it, thanks Kevin!

Premiere Pro 25.2.3 (Build 4) | OS: macOS Sequoia 15.5 | CPU: 3.8 GHz 8-Core Intel Core i7 | GPU: AMD Radeon Pro 5500 XT 8 GB | RAM: 16 GB 2667 MHz DDR4
Translate
Report
Community Beginner ,
Apr 17, 2025 Apr 17, 2025
LATEST
The bug appears to be fixed in v 25.2

John
This message, including any attachments, is intended for the sole use of the intended recipient(s) and contains confidential information. Any review, reliance, distribution, forwarding, copying or other use by any other persons is strictly prohibited. If you are not the intended recipient, please immediately notify the sender and delete this message, including any attachments, in its entirety.
Translate
Report