Copy link to clipboard
Copied
Hi,
I'd like some help on an issue I've been facins since Premiere Pro 22. Whenever I impost my footage, apply a rec709 LUT and go to make any curve or vignette adjustments my image seems to imediatley brighten up or over expose itself. Here's a before and after, all I did was add a marker on the S-Curve.
Any help is appreciated thanks!
Hi @Craig32644878j5ko ,
I tried to reproduce the issue on Premiere Pro 24.0 and failed to reproduce it there.
Please help to try the latest version once to check if it is still causing the issue.
If it is still reprodcuible for you in latest version then if possible please provide following information:
- System information - OS, GPU (device and driver version)
- Sample media, and LUT being used.
- Sample project reproducing the problem.
Thanks,
Copy link to clipboard
Copied
Images here
Copy link to clipboard
Copied
Looks like a bug. Does it happen regardless? Without any LUT enabled? What happens if you just load a Lumetri Color effect onto the clip without using the Lumetri Color panel and then adding a point to the curves from the Effect Controls window?
Not sure if still possible on Macs but what if you set the playback engine to Software Only?
Could you also share a grab of the clip properties (rightclick the clip->properties) and the sequence settings?
Copy link to clipboard
Copied
Rergardless of clip or settings. Happens primarily with sony's own Slog3-709 lut but has happened with others too
Copy link to clipboard
Copied
Where are you loading the LUT? On the clip? On lumetri basic section? creative section?
Perhaps try putting 1 lumetri instance on an adjustment layer above the clip. Then another adjustment layer above or below it depending on where you want to apply the grading before or after LUT. And use curves there. Does that exhibit the same issue?
Copy link to clipboard
Copied
I load the lut on an adjustment layer above the clip on the lumetric basic section. I usually get around the issue by making an instance change on a different AL but I tend to end up with 6 or 7 layers on top of each clip. I had never seen an issue like this before so I wanted to find a solution becuase it's been happening consistently even throughout upgrading Macs
Copy link to clipboard
Copied
I feel your pain. Back in my early color grading days I primarily used Premiere because I liked the idea of having all online processes consolidated as much as possible within one software. It's not uncommon for a layerbased grading workflow to have multiple layers, this is similar to how you grade in Baselight which is industry leading grading software. This is one of my older projects pulled up real quick.
I would always have the LUT layer as it's own so whenever it would break I could simply reload the LUT on that layer. I renamed the layer to the name of the LUT since the LUT name would also change to "Custom..." sometimes.
But since we had to deal with so many deliverables, transferring grades accross them would require tons of extra work and masks also don't play nice when the adjustment layer resolution needs to change, we've moved completely to grading in Resolve. I was just done with all the headaches and limitations Lumetri Color has (like massive slowdowns with multiple layers/instances or high resolutions). It's okay for simple tweaks on already Rec.709 normalized footage, but using it professionally just breaks too easily.
Sorry, not really any help for a solution but perhaps you can find a similar workflow with Resolve roundtripping suitable for your needs. It takes a bit getting used to but gives so much more control and freedom.
Copy link to clipboard
Copied
Hi @Craig32644878j5ko ,
I tried to reproduce the issue on Premiere Pro 24.0 and failed to reproduce it there.
Please help to try the latest version once to check if it is still causing the issue.
If it is still reprodcuible for you in latest version then if possible please provide following information:
- System information - OS, GPU (device and driver version)
- Sample media, and LUT being used.
- Sample project reproducing the problem.
Thanks,