Inspiring

Question

Premiere Color Managed Workflow - BorisFx clip colour

Forum|Forum|1 year ago
January 25, 2025
2 replies
1606 views

I am working in a colour managed workflow in Premiere. I am using a Sony Fx3 and shooting in Slog3/Gamut3.Cine. I apply this colour space to my source clips so they get converted to Rec709 in the timeline. This works fine but as soon as I add a BCC effect like Licence Plate ML or DeNoise ML the highlights are totally blown out and you can see in the vectorscope that they are clipped at 80%. Why? Is there any solution?

Fergus H

Community Manager

Hi Peter!

When you apply the effects to the clips on the timeline, does the render bar go red? Can you duplicate the problem using the Rolling Shutter Repair effect that comes with Premiere Pro?

There is a bug in the current version of Premiere Pro that cause clamping when certain types of effects are applied to clips. This will be fixed in the next version and you can test the fix by using the Premiere Pro beta.

Let me know if this helped!

Regards,

Fergus

P

Peter ReefAuthor

Inspiring

Thanks Fergus!

Yes the render bar always goes red. As far as I know this applies to all BCC effects. Will playback performance of the BCC effects be improved in Premiere beta as well? I thought a Mac M2 Max with 32 gigs of ram should play back the licence plate blur in realtime for example, but in a lot of cases its unplayable. And denoise renders for ages. Do you know when the next final version will be released? I am in a lot of productions and cannot test a beta version right now unfortunately..

Fergus H

Community Manager

Hi Peter,

The root cause of this issue is that some effects run on the CPU instead of the GPU. Rolling Shutter Repair is one of the handful of Adobe ones that do and the Boris effects you're using are too. This means that they are processed in 8 bit (and process very slowly, which won't change in the beta) and a bug in the current version of Premiere Pro clamps the image.

Probably the best workaround for now is to split your workflow into two separate steps:

1. Make the color changes you want to the clips you'll be applying the effects to but do not apply the Boris effects to the clips. Export those clips with the color changes baked in.

2. Re-import those clips into Premiere Pro and use them to replace your original FX3 clips. Apply the Boris effects to the clips, then export your final sequence.

I hope that makes sense. If it doesn't, send me a private message and I'd be happy to jump on a video call. I'm heading home from Sundance today but will be in the office tomorrow.

Regards,

Fergus

R Neil Haugen

Legend

So to check ... you have:

Display color management
auto detect log
auto tonemapping
Premiere's option for Slog3.cine
Sequence set to Rec.709

Is that correct?

And then applying the Boris effects, it goes off the rails?

At that point, I would suggest contacting Boris. The set you have may not be updated to work with Premiere's massively changed internal color management.

Everyone's mileage always varies ...

P

Peter ReefAuthor

Inspiring

Thanks Neil! I have those exact settings and already contacted Boris.
When Boris is not active colour management works flawlessly.

A

AidanEdits

Inspiring

BCC DeNoise also gave me this issue like this when working with Premiere's new Color Management. Have you applied any other effects to the clip you're adding the DeNoise to?

You can try nesting the footage and applying the effect to the nest, or applying the effect to the source clip in the Source Monitor, though this will apply the effect to the entire shot and may cause some playback issues.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded