Skip to main content
Known Participant
May 28, 2017
Question

Saturation is still incorrect (Pr CC 2017)

  • May 28, 2017
  • 2 replies
  • 2619 views

In the example below I have applied a similar amount of saturation in premiere and Photoshop (by taking a screenshot):

Why is the saturation slider in Premiere Pro CC 2017 (still) behaving weird?

I recently upgraded from CS6 to CC, and immediately noticed how ugly the colors became when I wanted to add some saturation to this sky.

Basically it just makes a total mess of the colors. It looks like it's been peed on...

It is not that it only yellow shifts, it does more weird things.

The only solution I could find was using one of the 'creative' film simulation presets to get more saturation without messing it up.

I found a topic by Dave Dugdale from 2015, and apparently this still has not been fixed.

What?? Am I missing something? Is there a workaround, a checkbox in the preferences or something?

The footage is a non-lut GH4 time lapse MP4.

This topic has been closed for replies.

2 replies

dangd74904783
Participant
May 30, 2017

I have been time to research this situation. I knew that in photoshop uses colour space is adobe RGB or sRGB and in premiere is YUV. So when you do many things in photoshop even make LUT After that adds them on your video in premiere. Colour video isn't always nice as you see in photoshop. 

Weddingfilm2k.

SkiesmdbAuthor
Known Participant
July 15, 2018

As nothing has changed with Lumetri color rendering the past year, I've posted an 'idea' on the feedback page here (I thought I already did that, and I can't find a similar post, but better late than never):

Lumetri shifts colors – Adobe video & audio apps

Please vote

Ann Bens
Community Expert
Community Expert
July 15, 2018

Is this about 2017?

R Neil Haugen
Legend
May 28, 2017

The issue that Dave posted about then ... and that I'd already filed a bug-report about ... was fixed shortly thereafter.

As to comparing Photoshop and Premiere for controls effects ... they are two completely different programs, built by completely different teams working in completely different facilities and 'chain of responsibility'. Not one stitch of code has anything to do with the other, nor are the 'amount' settings for anything even thought of being comparable.

If you watched the Vectorscope YUV, as you increased saturation, did it change direction or did it just expand the trace in general? For me, it's performing as expected.

Neil

Everyone's mileage always varies ...
SkiesmdbAuthor
Known Participant
May 28, 2017

Ok so I did another take at this, now including Speedgrade:

Update:

CORRECTION: Speedgrade is CC 2015 (apparently not updated so no dynamic link with Premiere which makes this even worse)

Speedgrade does a much better job.

Photoshop still has the most natural look though (with no yellow shift).

Premiere is just a joke. Doesn't look fixed to me.. How did this even past testing before release?

I don't think it matters whether Premiere is written by another team. That is not an excuse since it's all Adobe CC. True color reproduction is what matters. (That is why I always use Canon DPP for photography as it's colors are still far superior and more natural over what adobe raw creates.)

R Neil Haugen
Legend
May 28, 2017

If you can't see why a completely different software ... compiled by a different group ... without any internal connections (as there is no natural connection between a stills app and a video app) would have different responses to a particular media, I'm at a bit of a loss to explain. And don't confuse the UI for Lumetri with Lightroom ... the Lumetri UI was designed to look "familiar" to Lr users, but the actual tools and the science behind them are completely unrelated. Largely because trying to take one into the other literally cannot work properly.

I notice you're showing at apparently maxed out saturation ... which is normally a bit to the insane side in video, WAY past legal boundaries. But still haven't related your media to the Vectorscope!

It's the Vectorscope that would show us if there is something odd going on within PrPro. NOT a comparison to other non-related applications. Show us the PrPro Vectorscope at "normal" saturation and at the point that the farthest excursion of trace touches the boundary box.

Neil

Everyone's mileage always varies ...