I thought that when you have:
[Lensfun]
DBDirectory=
then ART should search in the default location./share/lensfun.
At least it works like that on my PC.
Do you think it is required to add the path in option file?
In this case when building for windows, we will have to use the -DLENSFUNDBDIR=./share/lensfun cmake flag
That’s the intended behaviour, yes. It seems though that something is not working properly, but I don’t know what yet…
Hello everyone, do we know who is building ART’s V1.3 packages for the PPA?
In the mean time, I will add the flag. It should not hurt!
@Carmelo_DrRaw perhaps to be sure, you could add the flag?
If you can rebuild 1.3 with that flag, I will re-generate the installer from your generic build and reupload on the webpage
Hi everybody,
just a quick piece of info: I’d like to release 1.4 “soon” (not better specified at this point). If there are any outstanding issues/blockers you think should be addressed, please speak up.
Personally, I’m quite happy with the current state of things, so I expect development to slow down a little bit after this new version (which doesn’t mean that there will be no more developments, just fewer new features for a while – bugs will always be addressed asap).
Here’s another one who is quite happy with the (your) state of things, your state of ART. There’s a tendency in software development that there must always be a next version that offers more and better and sexier functions and tools. But one can also take another approach, saying hey, this software does what I want and need, so why add more stuff ?
One can even go a step further by asking, are there redundant tools in Art? An example is the black&white filter. That works well (for years in RawTherapee), but desaturating in Color Correction works equally well for me, combined with the different sliders there. Same with Saturation & Vibrance, White Balance and perhaps some more.
When you, Alberto, started with Art by saying you wanted to make a kind of simplified (and enhanced) version of RT, I was wondering what could be left out of RT without sacrificing its basic functionality, and for me, that was quite a lot. For me, you could reduce Art just to the masks section plus sharpening and denoising and I would be happy (perhaps I forget a filter or two). But of course everybody wants or needs another toolset…
Anyway, thanks a lot for your work, Art is my preferred raw processor now, before RawTherapee (quite complex), Darktable (quite complex) and dcraw (quite basic but functional).
Regards, Paul.
I find most of the filters useful so I would leave it as is. I vote to maintain the current state of the ART! Thanks again.
The last few days I have edited many photos with Art, including panoramas and HDR. Many sunrises, where I have used the equelyzers a lot. I still have to practice with log tone mapping (especially at sunsets), otherwise everything works smoothly. Great software!
Thanks for the replies. Just to clarify: I have no intention of removing stuff. I agree there is some redundancy, but overall not too much, and the current set of tools is a good sweet spot for me
@agriggio he strange behaviour of the file browser on opening has returned - the filter panel is always open. Windows 10. Might be due to an update of Windows 10 breaking it.
The proper place would be bitbucket, otherwise it might be forgotten here… Anyway, I’ll try to look into that, thanks
Hopefully fixed now
In my opinion ART is ready for the new release.
The only thing I see that would need to be fixed is the history message for the radius of the new gaussian mode in smoothing (HISTORY_MSG_SMOOTHING_SIGMA).
Noted, thanks!
Thanks for fixing!
I am happily using ART almost every day and I haven’t noticed any big problems or crucial missing features.
I have a few ideas for small improvements or new features but nothing that would prevent the release of 1.4.
Sorry, I missed this message. Is this still needed?
I think so, yes. Currently, users need to edit their options file to make lensfun work with the appimage (see here)
