In this special case I don’t agree about the likelihood, because it was my intention the steal it from art 
1 Like
It’s not always evident that the input and output profiles both meet the floating point requirement to tell LittleCMS to do the transform unbounded. Any V4 profile will work, but not all (not many, IMHO) V2 profiles will work.
Looks good here. A Happy Christmas to all and a big thanks to @agriggio and everybody who has shared their skills and time to make such a great piece of software.
1 Like
ART_master_1.7-1-gf7b47b103_W64 builds for haswell, skylake, zver2 and icelake architectures are available at
3 Likes
Thanks for 1.7.1 Alberto!
A thumbnail display bug re cropping jpgs has been fixed, but there’s a bit of glitch here on 2 CR2s in both the film strip and then file browser, where the crop preview on the thumbnail is not quite right:
. CR2 and ARP here: IMG_2453.CR2 (28.1 MB) IMG_2453.CR2.arp (11.2 KB)
Many thanks for all your hard work.
Happy Christmas to all from Derbyshire, UK.
Hi,
Try clearing your cache and see if that helps
1 Like
Yup, that did it, thank you 
I’ve been using ART for the last several versions and it’s great. I just installed ART v1.7 and found something strange. I edited a photo and exported to a JPEG by adding to the processing queue like I normally do. Then I made other edits and exported the new version to a JPEG. When I compared the JPEG images, there appeared to be the same. I went back into ART and turned the exposure down -3 so the image was very dark and exported to a JPEG. But the JPEG isn’t dark, it looks like the first two files. I compared the JPEG images using Beyond Compare and the files are slightly different, but they are all look the same. I closed ART and started it again. It remembered my -3 exposure adjustment. I exported as a JPEG again and the new exported image still looks like the first JPEG I exported. I’m not sure if this is a bug or a setting that is incorrect.
Hi,
I’m not sure either, hard to say without data… So, could you attach the jpg and the arp? Thanks!
20201227_02.dng.arp (47.7 KB)
Here’s the arp and the first and last jpeg. The second jpeg should be very dark. Let me know if you need the original raw file. These have the processing profiles embedded in the jpeg. As another test I imported the processing profiles from each of these jpeg files and they both created the same settings in the editor.
I forgot to mention I’m running Windows 7.
Thanks,
David
Hi,
I just tried applying your arp, and it works as expected here…
maybe you can try recording a short video/screencast that shows what steps you are doing exactly?
Alberto,
Well that’s embarrassing. I had created a new resize profile and checked the box on the Queue page to apply on export. I have a few different resize profiles and I use this feature all the time. But this time I forgot to use Ctrl-Click to save only the resize parameters when I saved the profile. So it was applying all the parameters from my original profile. No wonder they all looked the same. I wish I had figured that out before asking for help. I’m sorry I took your time. I appreciate your work on this great editor.
David
No problem, glad you sorted this out 
Hello, Happy New Year!
Something that I have noticed in more recent developments of ART for Windows 10 is that the option for CA correction in profiled lens corrections is greyed out.
I don’t think this was always the case and CA corrections are available from Lensfun for my camera, because they are there in RawTherapee 5.8.
Is this behaviour intended? I know that the Raw CA corrections are more effective at removing CA, but sometimes it generates colour shifts (sometimes purple haze around twigs of trees, especially when avoid colour shift is turned on), so it would be good to have the alternative of using the profiled lens corrections.
Coventry City Centre 7.RW2 (14.7 MB) Coventry City Centre 7.RW2.arp (11.3 KB)
Raw file and arp attached for reference. Many thanks…
The idea is to have it greyed out if the profile doesn’t support it. Perhaps there’s a bug in the logic that checks that – I’ll have a look
Thanks Alberto…
- I see that lcms2.12 is approaching with a RC1 already issued. There are also some new pdf doc.
So I was wondering if you could make some progress with the fast plugin? - on the ART french forum, a user showed a .RWL photo from a “LEICA CAMERA AG D-Lux 7” that presented a magenta cast with discoloration. That seems to be due to black point. The identical Lumix LX100 II has a +15 compensation in the 3 channels. So I tried that and it seems ok.
Thanks to have a look.
L1000085.7z (13.8 MB)
Hi,
I tried, but it still behaves as in 2.11. Namely, if you want to see some performance benefits, you have to not use cmsFLAGS_NOOPTIMIZE, but this will clip the values to [0,1]. If you use cmsFLAGS_NOOPTIMIZE, nothing gets clipped, but using fast float gives no benefit at all… 
Thanks, I’ll take a look
Hi,
preparing for a 1.8 release, here are the highlights:
- slightly improved “colour propagation” highlight recovery (trying to mitigate artifacts that might sometimes occur)
- added Spanish and Catalan translations
- changed the UI of the color/tone correction tool in “HSL factors” mode, from sliders to color wheels
- added “luminance mode” for color correction with “separate RGB channels”
- improved RCD demosaicing code, taken from RT
- added a new “Glow” mode to the smoothing filter, inspired by recent discussions here
- simplified and improved the “final smoothing” part of the “noise reduction” tool (median is gone, replaced by a custom-tweaked non-local means implementation)
FYI
3 Likes