This bug has 2 behaviors according to the modified adjustment:
- Temperature: not modified value
- Tint: modified value but not taken into account
I think it’s something as a wrong initializing of the routine. Like showing the 5400K at first. After you have first changed the values everything behaves well.
The slider doesn’t follow the value, but the value follows the slider.
George
1 Like
This article sheds some light on what PhotoLab is actually doing at the start:
what it has to do with DxO not offering Camera Auto option ( because as noted it is already available in raw files for modern cameras, so DxO does not need to bother work out their own Auto if they can’t for whatever reason ) just like the offer “As Shot” ?
Interesting indeed. But my issue has more to do with changing the color temperature. I can live with the values DxO derives, I just need to change them a lot of times.
1 Like
@miloman Out of interest, is this the behaviour you’re experiencing?
Post 27 (with a video) in this thread - posted by myself
1 Like
No, sorry… Most likely it is related though. In my situation (windows btw) previously when I type a value into the temp box, it applied the value immediately, and also changed the setting to custom.
Now when I do this, first time when I type a value, it is ignored (value is not changed when moving away from the temp field), but the setting is changed from as shot to custom. Only with this setting it accepts the new temp value…
1 Like
On my laptop PC I’m still in V6.5 and the value changes immediately.
On my desktop PC I’m in v6.6.1 and I have this bug.
1 Like
I noticed this issue with 6.6.1.
I often manually change the white balance by typing in a value. However now when I type the value and hit enter white balance go from As Shot to custom but my value resets to the As Shot value.
I have to type the custom value in twice. Very annoying. I’ll report this bug to DxO next week.
1 Like
I wonder if this problem is related to the issue to not being able to copy the white balance settings?
Both issues seem to have appeared with the newest updates to PL 5 and 6.
1 Like
I created a request to revert back to the previous way of changing the color temp (#419603)
Bonjour,
avec une valeur original de 5400 K, et si je tape par exemple 10000, je passe très bien à 10000K teinte 0, pour revenir as shoot, je double clic sur le curseur et tout revient parfaitement.
Merci
1 Like
Bonsoir,
Quel est votre OS ?
Windows 11 pro, 22H2. Bonsoir!
Bonjour,
Windows 10 Famille 22H2.
Bonne journée
Bonjour,
Merci.
Donc pour vous cela fonctionne sous Win, à partir de la température “Originale”, le changement de la valeur est prise en compte ?
J’ai aussi ce problème sur mes 2 PC sous Win10 et Win11, la valeur tapée n’est pas prise en compte malgré le changement de statut qui passe de “Original” à “manuel ou personnalisé”.
1 Like
Works perfectly here. Win10 pro N 22H2 + mediapack. Photolab 6.3.1.
1 Like
I don’t experience this with my config (see above) but it looks like there’s a new version fixing this (6.6.1.199).
1 Like
I think it happened with the V6.6.1.199
The problem would be solved with the V6.7 released today.
1 Like