hholt
(Heinrich Holtmannspoetter)
April 6, 2018, 4:27pm
1
By playing with ciecam in dev-5.4-144 on win10-64 and using ‘all’ as algorythm in image adjustments the picture part of RT got black. Changing enlargement brings the picture back for a second or so. By using all other algorythms there is no problem. So I don’t know is it ok or is it a bug? Perhaps someone can test.
Many thanks
Heinrich
For me it happens with a processed image. It happens not if I start from neutral. I’m on 5.4-133-g16679296
Can you provide a raw and pp3 file to reproduce?
Thanks for the files. Still can not reproduce here using 5.4.148
I think I found the culprit. Screenshot shows the solution
We should remove the option to use the old double precision ciecam02 code…
2 Likes
hholt
(Heinrich Holtmannspoetter)
April 6, 2018, 6:24pm
9
After changing the setting there is no problem any longer. Many thanks to https://discuss.pixls.us/u/heckflosse
2 Likes
heckflosse
(Ingo Weyrich)
April 6, 2018, 10:11pm
11
I created a pr to remove the ciecam02 double precision stuff for RT 5.5
Beep6581:dev
← Beep6581:remove-doubleprecision-ciecam02-code
opened 10:28PM - 06 Apr 18 UTC
Though in past the double precision ciecam02 code was the reference ciecam02 cod… e, imho that's not the case anymore. For that reason I have removed (hopefully) all the double precision ciecam02 code and would like to push that into dev branch if there are no objections from other devs.
Especially ping @Desmis
2 Likes