Strange Colorshift after discard history (or import)

Hi all! I am relatively new to the new scene-referred workflow and I have been reading up on it, but it still goes over my head at times :slight_smile: I am mostly happy with the results, but sometimes run into problems.
I have recently tried to re-work an older photo that I had still processed with the older screen-referred dt version. After “discard history” I noticed a severe hue-shift that renders the fire in the image in a strange unnatural salmon-like orange.
I’ll add three images below:
Old Version

After “discard history”

related data to the second version

Can anyone explain what’s going on?

Hi Daniel.

I think what you’re experiencing is actually a hue-shift correction in filmic RGB.

In general, you have three options:

  1. Go to opitons tab in Filmic RGB and select color science: v5 (2021) and preserve chrominance: no
  2. Disable filmic and use Sigmoid instead, dragging the “preserve hue” slider down.
  3. Don’t use Filmic or Sigmoid. I never do it like this, it’s quite challenging for me to get the tones right

I’m not sure why it happens now, but not before. Perhaps you used v5/no before?

2 Likes

Thanks, yes it’s caused by filmic RGB. If I turn it off the shift disappears. Both options work. So that’s a relief :slight_smile: But should that happen at all?

Thanks for the help! This solves the problem. It’s a bit annoying workflow related, though.

I used a super old version, don’t even no from which year.

Yes, it’s normal.

When I first learned that the yellow you see in the flame is actually a hue shift introduced by e.g. JPEG processing, I almost didn’t believe it :laughing: What Filmic and Sigmoid do is hue shift correction which, in my opinion at least, doesn’t look natural at all. In my book most bright orange objects (sunsets, fire, sodium vapor street lamps) follow this sort of gradient: (not exactly, but you get my point)

So I often set the “preserve hue” in Sigmoid to around 40-60%, depending on the scene.

1 Like

Wait, this exact problem was the first ever post I made on this forum 2 years ago :grin:

@priort and @kofa were the first people that I ever interacted with here :slight_smile: …
nostalgia
I still remember the day I learned how to combat this hue problem and was so excited, thanks again, Todd, for help :laughing:

EDIT: Kofa, when I first tried Sigmoid, I think I didn’t know about the hue slider, so I didn’t pay too much attention to your answer :sweat_smile:

5 Likes

No way! So you are saying that we are used to a “wrong” representation of fire and that filmic is actually getting it closer to right?

1 Like

Great, I am glad you found my question right away. Expert!

1 Like

Technically speaking, that should be true.

As I said, in my opinion, the “correct” look is something in between, but that’s just my perception of colors and how I prefer to render oranges.

The problem also happens for blues too (or other colors), where bright blue sky turns cyan.

Yes.

I recently did a little experiment outside at a birthday party.

We had this fire bowl and 5-6 people were standing around it. I asked the people present to describe to me exactly what colors they saw in the flames. I was particularly interested in the difference between the lighter and darker parts of the flame.

No one (including me) saw yellow color in lighter flames. At most they were yellowish-orange with less saturation than the darker ones.

I remembered the color and edited this photo the same evening as I perceived the colors of the flame:

7 Likes

I agree, this indeed looks very natural.

Would you share the photo under full and no hue correction too?

1 Like

fascinating!

1 Like

So do you have hue preservation then disabled by default?

I actually have it enabled, I only change it when I need it. Sometimes the picture is good enough by default.

1 Like

Sure:

DSC_4971.NEF (25,2 MB)

This file is licensed Creative Commons, By-Attribution, Share-Alike.

2 Likes

Hi @Daniel2 you have some great answers here already. I am going to make an alternative suggestion. Turn off filmic and turn on Sigmoid. Decide for yourself which rendition you prefer. However, be warned that the colors in Sigmoid are more colorful straight out of the box while filmic generally expects you to play with saturation later. I personally use Sigmoid as my default tone mapper because I like the results that I get straight out of the box without any user input for most images that I shoot. Good luck.

2 Likes

Thanks! I will give it a try!

Exactly the reason why I use Sigmoid like 99% of the time, it sometimes almost feels like cheating haha.
Occasionally, there’s a photo where I need detailed and saturated highlights, like clouds on a sunset sky of an overall high contrast scene, and so far I have never been able to pull that off with Sigmoid. In those cases I use Filmic v5/no and skew hight/shadow balance one way (idk which one)

Yes, although Filmic is arguably going too far in preserving the hues in many cases (try searching for salmon sunset). To control it you have the highlights saturation mix slider in v7 and the preserve chrominance option in v6 and older.

This video by the Filmic developer goes into more detail:

1 Like

Haha! So my Salmon comparison in the OP wasn’t all that unique :))

1 Like