I've been having a major problem with Premiere when moving the final edit of my film to another computer. All of the footage is oversaturated now and it is because they have all been interpreted in the wrong colour space by my computer, I hope this makes sense.
I want to change the footage to Rec 709 but the Colour Management Section under the Interpret Footage tab is greyed out for most of the video files, not all of them though. I have heard that removing the clip from the timeline would do it but even this doesn't work.
I hope the problem I have described makes sense, its a very niche and specific issue.
Sorry to hear about this. Let us know the exact version of Premiere Pro that you are using & the specifications of the media files (format/codec, frame rate & frame size) that needs to be color-managed.
Having the same issue. Seems to mostly be affecting my 444 .mxf and DNxHR .mov files, whether from the camera or from After Effects. As a sidebar, AE is correctly handling the files and allowing me to apply color management.
Just updated to PPro 22.2.0 (Build 128) and having the same problems. It should be noted that these files were unafected in November 2021 when I started work on this project, whichever version I was on then. (I almost always update to the most recent versions before starting a new project.)
Here's a copy/paste from two of the affected file types I've got:
These are the file properties from the source files:
Type: SonyRAW Format
File Size: 11.73 GB
Image Size: 4096 x 2160
Frame Rate: 24.00
Total Duration: 00:01:46:00
Pixel Aspect Ratio: 1.0
Creation Date: 2021/04/19, 23:12:50 UTC
SonyRAW File Importer plug-in version: 22.2.0
Decoder mode: CPU (Using: Internal SonyRaw device)
Source Video Format: F55 SQ
White Balance: 3200
Auto White Balance Mode: Preset
Exposure Index: 500
ISO Sensitivity: 500
Raw Black Code Value: Not found in file. Using: 512
Raw White Code Value: Not found in file. Using: 5472
Camera Attributes: "MPC-3610 0012279 Version5.00"
These are the file specs from the rendered VFX shots returned from AE2022 using the built-in renderer and DNxHR encoder:
Type: QuickTime Movie
File Size: 1.65 GB
Image Size: 4096 x 2160
Frame Rate: 24.00
Total Duration: 00:00:09:12
Pixel Aspect Ratio: 1.0 (1.0)
Movie contains 1 video track(s), 0 audio track(s), 0 closed caption track(s), and 1 timecode track(s).
There are 228 frames with a duration of 1/24th.
Video track 1:
Duration is 0:00:09:12
Average frame rate is 24.00 fps
Video track 1 contains 1 type(s) of video data:
Video data block #1:
Frame Size = 4096 x 2160
Compressor = DNxHR RGB 444 12-bit
Quality = Most (5.00)
Timecode track 1 contains 1 type(s) of data:
Timecode data block #1:
Start Time = 16:13:10:01
Reel name =
Hopefully that info helps. In the mean time, I'll experiment with re-encoding them as some other format. So far, 422 ProRes files seem fine, so I'll see if 16 bit 444 ProRes HQX files will work in place of the 444 12 bit DNxHR files I originally encoded.
Quick update, the files are also affected in PPro 15.0.0 (Build 41), so perhaps there is something else going on, such as a Windows update that messed things up...
Okay, facepalm, for at least one of my file types. Sony. Freakin. Raw. Forgot that those have their own color management settings hidden away in the Effects panel.
As for the other file type (the return render from After Effects), I went with what I'd hoped was as close as possible to the "Sony RAW" .mxf files I had for the originals, which is a DNxHR RGB 12 Bit w/o Alpha in a .mov container. Just looking at those settings now combined with past experience, I'm starting to think it is the RGB part of the program that might be throwing things off. I've used RGB instead of YUV a few times for high quality archive files, but I do seem to recall Premiere not always playing nice with them. I can get MediaInfo set up to start sending more detailed info.
When I re-encoded a sample file to ProRes 444 HQX, I was able to access the Color Management in the Interpret Footage settings. However, instead of having the list I expected (I need to interpret the files as S-Gamut3.Cine/S-Log3), there is a much shorter list that only shows the more general Rec based color spaces including 601,709, 2020, and 2021, including HLG & PQ variants as available. So, new question... is that normal? I could have SWORN when I started this project that there was a MUCH longer list there that included various Sony color spaces as well.
Yea, stick with the YUV variants, not the full RGB 12-bit DNx.
The Sony S-log3.cine is available if Premiere sees the files as a Sony file, so if they've been transcoded that wouldn't be available. Very confusing at the moment.
Noted. I bounce back and forth so much between Premiere and AE that I think I take certain functionalities for granted.
As I mentioned, when I first started conforming this project for AE in November, I remember seeing S-log3 etc. on the list of color management options... But perhaps that wasn't actually in Premiere, but was actually in AE. My thought was, since the non-VFX shots in the edit were all SRAW and seemed to look the most "right" interpreted as S-Gamut3.Cine/S-Log3, I would work in Rec709 in AE and render back to that "native" color space to make life easier for the colorist, with all shots having the same color process. But if you can't manually tell Premiere to interpret the colors that way, that's clearly not going to work.
In any case, it was plenty easy to take my RGB DNxHR renders back into AE and interpret as S-Gamut3.Cine/S-Log3 with the project set as Rec709, and just re-render as ProRes HQ 16 bit as Rec709. That got them to where they needed to visually be for reconform and delivery.
Thanks for getting back to me Sumeet. I'm afraid I'm not very skilled with Premiere, or even experienced with editing at all, so I'm not too familiar with the formats and info that you need. What I can say is that I am using the most up to date version of premiere and all of the clips with the colour management disabled are in the MXF format, and have linked audio that has been used in other projects. An adobe technican discovered this but was unable to convert them to the right colour space.
What we need are the file types, and what created them ... if a camera, which one. So that they're mxf is useful partly ... but what created them?
Also, we regulars here use the free utility, MediaInfo a lot. You can download and install it. After the icon for it appears on your desktop, you can simply drag/drop a video file onto that app's icon. MediaInfo will open ... from among the viewing options, select the Tree view, and make a screen grab of the top couple sections.
Drag/drop that screengrab onto your text reply area.
What camera created this file? Sony?
I'm really not sure where to find that info, it was filmed almost 6 months ago with rented equipment and I'm not sure what it was. Will the file properties say that somewhere?
Copy link to clipboard
LIke Sumeet says, we need to know the files, and what camera created them also. Which can make a huge difference.
Will the video file say anywhere the name of the camera that filmed it?
Going back and looking through the MediaInfo stuff ... that is probably from a Sony. And is probably the reason for the trouble you're having. Some "flavors" of Sony files in Rec.709 Premiere recognizes as Rec.709, and turns off the CM options. But it still mis-displays the media on a sequence.
Worst of both worlds. ain't that special?
A screen grab of both the image in the Program monitor with the Vectorscope YUV showing would be very helpful to get an idea of how to help you.
Where can I find the vectorscope YUV? Sorry these are all new phrases to me.
In the Lumetri scopes panel. When doing any color work, one should always have the scopes visisble. Computer monitors are not a (normally) precision tool, and the human eyeball is a marvelous relative judge but horrid at absolute things.
So blacks, whites, saturation levels are best set with a good look at the scopes.
Vectorscope shows overall saturation levels by hue ... the outer circle is the Hue color wheel, essentially. Dead center is no color ... white/gray/black. The farther out the signal shows, the more saturated it is.
Is this the kind of screenshot you wanted?
I should also add, I don't think premiere actually does recognise the footage as rec 709 as you suggested. It says in the properties of one of the affected clips that the colour space is Sony S-Log, and seems to display it as such. It says that colour override is off but that's only because it won't allow me to use the colour management option as I said before.
Well ... that's the Waveform scope in RGB mode, but yea, between the scope, the image, and the new properties shot, I can see what's going on.
Understand ... all HDR is log-encoded, and expected to be in the Rec.2100 sort of color space. Some log-encoded media is actually intended to be SDR, and worked with in the Rec.709 "normal" view. And some log-encoded media doesn't have a 'native' color space, and can be worked in any.
Premiere is seeing some of the Sony & Panny log-encoded media as HLG (an HDR form) and displaying it as such. But not allowing the user any option in the color management settings. And this Sony S-log3.cine type of media is the most difficult one for Premiere to get right at the current time.
You can pull that back within viewable bounds with the Color workspace, the Lumetri panel. Typically that works ok, but for some, at export it ignores the Lumetri work.
So test bringing this back with the controls of Lumetri, lowering the Whites, adjusting contrast and saturation. And then export, to see if that works.
If not, I can give some further assistance.
I'll attempt to work on the lumetri panel like you said, it's just a hassle since I assume it would mean that I would need to adjust each clip one by one. I'll get back tomorrow with how it went.
Thank you very much for your help Neil, you've come a lot closer to figuring this out than most people I've asked.
I found something new that might be useful when I was working on the project today.
As I said before, there are a few (very few) clips in the timeline that I actually can use the colour space override option on. I was looking to see if there was anything different about these clips and I noticed that there is something different about the blue symbols that appear on the bottom corner of each clip in the project bin.
The clip on the left is one of the few that I can use the colour space override on and the clip on the right is one of the many that I can't. All of the editable clips have the audio symbol greyed out, whereas all of the uneditable clips have two blue symbols. I'm not sure what this means.
Now knowing you've got probably Sony footage, and seeing how PPro is interpreting it (extremely punchy, with extremely "hot" highlights), I can say that this is practically identical to the footage I've been working with.
I haven't seen this mentioned yet on this thread, so I thought it was worth bringing up to you that you might have Sony color space controls like I had which are hidden in the "Source Effects Controls". I'm not sure if that's the right terminology for this, but essentially, if you make a clip active (either selected in the timeline, or active in the source monitor) and then open the Effects Controls panel, you'll notice two tabs at the top of that panel. Selecting the left tab will allow you to add effects to the source rather than just the timeline instance... and this is also where SRAW settings live, which gives you a drop-down menu to select which favor of S-Gamut/Log to interpret as. It's bizarre that those settings are in such a hidden away, unintuitive place... But worth checking to see if that's what's going on in your situation.
Thanks for noting this, Jake ... I hadn't seen any Sony settings in the Source tab of the Effects Control Panel ... (ECP) ... so wonder when that came in?
They've had controls for Arri, Red, BlackMagic's BRAW ... but not Sony or Panny.
I'm not best pleased to get surprises like this, ya know?
I DO know! Lol. Sounds like I need to get more involved in these forums. I've literally used PPro and AE regularly for over 20 years now and could probably provide another perspective of experience to help users with obscure issues, but I don't share the vernacular and shorthand you guys have to communicate about it in an efficient way.
"ECP"--I love it. Shorthand noted.