Copy link to clipboard
Copied
Hey folks,
I'm experiencing two bits of strange behavior and would like to understand what's causing them and if they are related. First things first. I'm on:
Premiere Version 24.2.1 (Build 2)
2023 MacBook Pro with Apple M2 Max Chip
Sonoma 14.2.1
I'm cutting a project shot on a Sony camera (some verison of the Venice). All video are attached to proxies.
The proxies were created on ingest into Premiere, using an ingest setting. Proxies have a preferred LUT burned in.
The raw footage, on the other hand, has a LUT applied that (originally), could be turned on, or off, by going into the Effects Control tab, then into the Source tab, and activating or deactivating a camera specific Source Settings effect.
Here's the first issue: I've been away from this project for a bit, and recently when opening it up, I received an error message that says,
"The ingest settings saved with this project contain the following invalid selections:
Missing Preset: /Applications/Adobe Premiere Pro 2024/Adobe Premiere Pro 2024/ Contents/Settings/IngestPresets/Proxy/01_1024x540 Apple ProRes 422 Proxy.epr
Click OK to reset them to defaults and turn off ingest. Click Settings to make new selections."
See attached "Issue 1" screengrab.
I THINK this missing preset is what I created/used to make the project's proxies. But I have no idea where it went or why it went missing. I wonder if clearing media cache (which I did several days ago) might've dumped it? I'm not sure. That's issue 1.
The second issue is that when I want to turn off the LUT for the raw video, I can no longer do it as I used to. I used to be able to just go into the Effects Control tab for a shot, go into the Source tab, and then I was able to deactivate a camera specific Source Settings effect that exists there - this killed the LUT. Now when I do that, the LUT remains on.
See attached "Issue 2" screen grab.
Two work arounds for Issue 2 that I've found are to:
•As mentioned above, if I go to the Effects Control tab, and then to the Source tab, there is a camera specific Source Settings Effect there. And if I switch the effect from Rec709 to S-Gamut3.Cine/S-Log3, I get video that looks raw (not sure if it is though).
•I can also select a shot in the project panel, right click it, and select Source Settings. From there, I get a similar menu where I can choose Rec709 and sevearal other color spaces, including S-Gamut3.Cine/S-Log3. If I select S-Gamut3.Cine/S-Log3, THEN my Effects tab seems to work as before: Meaning going into the Effects tab, then the Source tab, and toggling the camera specific Source Settings Effect off will produce "raw looking" video.
Does anyone know if the video that I'm getting with these workarounds is actually "raw" with regard to color? And does anyone know why either issue is happening, and if they might be related?
Thanks either way.
As to the second issue ... if you select the log state of that clip, in the Source effect to modify that specific media, yes, you are dealing with the original pixel data. With the changes they've made to the program in this version, that is the current workflow.
You can access all color management controls in one place now ... color workspace, Lumetri panel, SETTINGS tab. That shows all CM, from project with, through clip, sequence, and viewer gamma. And you can use that panel to set individual
...Copy link to clipboard
Copied
As to the second issue ... if you select the log state of that clip, in the Source effect to modify that specific media, yes, you are dealing with the original pixel data. With the changes they've made to the program in this version, that is the current workflow.
You can access all color management controls in one place now ... color workspace, Lumetri panel, SETTINGS tab. That shows all CM, from project with, through clip, sequence, and viewer gamma. And you can use that panel to set individual clips as needed.
For setting clip CM, you do need to have the clip selected in either the project panel/bin or the sequence.
For the first question ... did you start this in the 23.x series? As if so, maybe the preset you made is in that version's files. Um ... you do have 'remove prior versions' de-selected in the CC app prefs, so all previous versions stay installed, right? Hopefully?
Copy link to clipboard
Copied
Hey!
Thank you very much for taking the time to respond. This is helpful.
One thing that was throwing me off regarding the second issue is that there are multiple log states listed as options:
-S-Gamut/S-Log2
-S-Gamut3/S-Log3
-S-Gamut3.Cine/S-Log3
I've since spoken to the DP and he confirmed that we shot in S-Gamut3.Cine/S-Log3.
Regarding the first question - thank you. "Remove prior versions" is indeed de-selected. And while I'm not sure exactly what version of Premiere I started in - on your suggestion I did go look at the 2023 version's files and I did find an epr file that shared the name of the ingest setting that was noted as being missing.
Is it safe to assume that Premiere just upgraded itself, left the ingest preset behind in the prior version's files, and then gave me an alert that the preset is missing?
And can I just simply "add" that ingest preset (epr) again within the ingest settings interface of this newest version of Premiere?
Either way, thank you again for your time and thoughts.
Copy link to clipboard
Copied
I would try adding that ingest preset 'twere it me. But then, I'm pretty willing to poke the box. 😉
And don't you just love all the various s-log/et-al options? Keeping track of that is a royal pain ...
Copy link to clipboard
Copied
Yeah. Always learning! 🙂
Thank you again!
Find more inspiration, events, and resources on the new Adobe Community
Explore Now