Old Bruce Posted July 2, 2019 Share Posted July 2, 2019 Noticed something odd with the White Balance in the Develop Persona while processing a CR2 Raw file. The degrees Kelvin for the colour temperature is replaced by a percentage value if you use an overlay. The use of percentage instead of degrees Kelvin happens when you use the Develop Persona on a non RAW file or image. That just seems somehow wrong. And also the Photo Persona has the percentage for the Adjustment Layer. I have to ask percent of what? Mac Pro (Late 2013) Mac OS 12.7.4 Affinity Designer 2.4.1 | Affinity Photo 2.4.1 | Affinity Publisher 2.4.1 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
fde101 Posted July 5, 2019 Share Posted July 5, 2019 Off the cuff guess - percentage of the original value perhaps? This would make sense if the white balance at the time of capture could not be determined from the original file (as would be the case with artwork created digitally rather than being captured with a camera). If the white balance is identifiable from the metadata, I would expect it to display a value in kelvins same as with a raw file. Andy Somerfield 1 Link to comment Share on other sites More sharing options...
Old Bruce Posted July 5, 2019 Author Share Posted July 5, 2019 4 hours ago, fde101 said: Off the cuff guess - percentage of the original value perhaps? This would make sense if the white balance at the time of capture could not be determined from the original file (as would be the case with artwork created digitally rather than being captured with a camera). If the white balance is identifiable from the metadata, I would expect it to display a value in kelvins same as with a raw file. % of what value? and the scale goes from -100% to +100%. Does that translated to 0 (zero) K to 9000 K. It is just broken, badly broken. Mac Pro (Late 2013) Mac OS 12.7.4 Affinity Designer 2.4.1 | Affinity Photo 2.4.1 | Affinity Publisher 2.4.1 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
fde101 Posted July 5, 2019 Share Posted July 5, 2019 1 minute ago, Old Bruce said: % of what value? and the scale goes from -100% to +100% ok, so zero then would probably be the white balance as "baked in" to the image stored in the file - as non-RAW files do have a white balance that is baked into the image - and other values would probably be some range of adjustment, with 100% being the most it can adjust it in one direction, and -100% being the most it can adjust it in the other? There would be no way to display a value in "K" and no direct correspondence to a "K" value if the "baked in" value is not known to the software. Link to comment Share on other sites More sharing options...
Old Bruce Posted July 5, 2019 Author Share Posted July 5, 2019 2000° K to 25000° K is the range when opening a raw file, put that value somewhere in the file and then give me the same range of numbers when I wish to alter the white balance later. And don't change to % (of what?) when I use one of the overlays. ronnyb 1 Mac Pro (Late 2013) Mac OS 12.7.4 Affinity Designer 2.4.1 | Affinity Photo 2.4.1 | Affinity Publisher 2.4.1 | Beta versions as they appear. I have never mastered color management, period, so I cannot help with that. Link to comment Share on other sites More sharing options...
fde101 Posted July 22, 2019 Share Posted July 22, 2019 On 7/5/2019 at 2:06 PM, Old Bruce said: put that value somewhere in the file This is very likely the problem. If the value is not recognizable within the file it has no basis on which to present it accurately afterward. Not all file formats support storage of this value, and even if they do, it may not always be there. What is the white balance of a computer-generated image which is completely filled with a solid color? With nothing to go on, how do you present this in a meaningful way? Link to comment Share on other sites More sharing options...
Staff Patrick Connor Posted April 17, 2020 Staff Share Posted April 17, 2020 Sorry. Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum. Report a Bug in Affinity Designer Report a Bug in Affinity Photo Report a Bug in Affinity Publisher Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem. This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build. Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon Link to comment Share on other sites More sharing options...
Recommended Posts