ART new releases

gaaned92 · February 19, 2020, 5:46pm

Unfortunately, It doesn’t fall back to exiftool.
Your exiv2 is 2.7MB instead of 4.3 for the one I build on MSYS2/GCC9.2

Could be due to a difference in the tool chain ( GCC9.2 #GCC8.2…)?

Carmelo_DrRaw · February 19, 2020, 6:03pm

What error are you getting? I have tried to run the bundled exiftool with wine, and it worked…

agriggio · February 19, 2020, 6:08pm

when I tried with a packaged exiv2 the problem was that it was not raising an exception on error, so exiftool was never called… maybe you are using some build flags that cause this?

gaaned92 · February 19, 2020, 6:25pm

When I open a CR3 photo, I don’t get any exif data in ART. So It seems that the exiv2 doesn’t raise the exception.

Carmelo_DrRaw · February 19, 2020, 8:50pm

Maybe the digikam folks found the solution:

github.com

KDE/digikam/blob/master/core/libs/metadataengine/engine/metaengine_p.h#L61

    
      
          // Exiv2 includes -------------------------------------------------------
          
          
// NOTE: All Exiv2 header must be stay there to not expose external source code to Exiv2 API
          //       and reduce Exiv2 dependency to client code.
          
          
#if defined(Q_CC_CLANG)
          #   pragma clang diagnostic push
          #   pragma clang diagnostic ignored "-Wdeprecated-declarations"
          #endif
          
          
// The pragmas are required to be able to catch exceptions thrown by libexiv2:
          // See http://gcc.gnu.org/wiki/Visibility, the section about c++ exceptions.
          // They are needed for all libexiv2 versions that do not care about visibility.
          
          
#ifdef Q_CC_GNU
          #   pragma GCC visibility push(default)
          #endif
          
          
#include <exiv2/exv_conf.h>
          #include <exiv2/error.hpp>
          #include <exiv2/image.hpp>

agriggio · February 20, 2020, 9:16am

Thanks! I’ll try this asap and let you know

agriggio · February 20, 2020, 10:13am

Hmmm, if I understand the GCC wiki correctly, this is something that needs to be fixed when compiling exiv2. So, could you try rebuilding exiv2 with something like -fvisibility=default?

Carmelo_DrRaw · February 20, 2020, 11:19am

@gaaned92 @agriggio I have added the -fvisibility=default flag to the EXIV2 compilation, and generated a new package: https://github.com/aferrero2707/art-win64/releases/download/continuous/ART_master_1.1-16-g049d13415_20200220.zip

I made a quick test and I have the impression that now meta-data is read from CR3 files:

Could you make some tests on your side and confirm the fix?

Thanks!

agriggio · February 20, 2020, 12:23pm

I did a quick test and it seems to work fine now, thanks!
Though I still don’t understand why it doesn’t work out of the box… from my quick look at the Exiv2 code, all their public API (including exception classes) seem to be properly annotated…

gaaned92 · February 20, 2020, 8:41pm

Yes, working now
Thanks

carafife · March 8, 2020, 8:31pm

Thank you @agriggio. This tool is fantastic! very useful and essential :clin d’œil:

agriggio · May 1, 2020, 7:17pm

New release: 1.3.
No binaries yet, I hope they will follow in a few days.
Thanks to all the people who helped with code, translations, suggestions, and bug reports!

gaaned92 · May 1, 2020, 9:21pm

ART_1.3_W64_Skylake.7z
ART_1.3_W64_Znver2.7z
ART_1.3_W64_generic.7z
Uploaded at
https://keybase.pub/gaaned92/ART-W64NightlyBuilds/

built with
Exiv2_0.27_cxx_standard2_v0.27.2-255-gc51a8aa8 (AKA 0.27.3 I think)
lensfun_master_v0.3.95-517-g609148cc
lcms2_master_lcms2.9-80-gfc0fa79 (generic, skylake and znver2)

great improvments!

dheijl · May 2, 2020, 12:54pm

Thanks! Using the generic build I notice that it has the GTK problem where the lens profile selection (automatic or manual) is disabled.

gaaned92 · May 2, 2020, 1:08pm

Could you be more specific with the description of problem : system , meaning of disabled (greyed out no lens displayed…). Provide a raw with pp3 to reproduce. why you think it is a GTK problem?
did you activate “profiled lens correction”?

agriggio · May 2, 2020, 1:28pm

If you are on windows, locate your options file (I think it’s somewhere in c:\users\USERNAME\AppData\Local\ART and add this (or replace if the entry is already there):

[Lensfun]
DBDirectory=share\\lensfun

If that works, the next step is to understand what went wrong to make this needed…

dheijl · May 2, 2020, 1:44pm

Thanks Alberto, that fixed it.

My options file had:

[Lensfun]
DBDirectory=

I did not run an installer, just unzipped the Windows generic 1.3 build and started ART.exe.

dheijl · May 2, 2020, 1:53pm

I must have forgotten to check the profiled lens correction, sorry for causing you trouble.

dheijl · May 2, 2020, 1:57pm

But what is strange that it is now automatically enabled after I applied Alberto’s suggestion in my options file when I open a previously unedited raw file…

Silvio_Grosso · May 2, 2020, 2:44pm

Hello everyone,

THANKS a lot indeed for this release!

Just installed the 1.3 version on Windows 10 (64 bit):
ART_1.3_W64_generic (from today’s builds by gaaned92).

I am stuck with a new option, which is:
Split view (shortcut y)

In short, is it possible to gradually zoom in-out into the 2 images?
I have tried several shortcuts to no avail (e.g. ctr+wheel of the mouse; + - etc)

Is is possible to pan into the images once they are zoomed in?
Zoom to 100% (shorcut z ) works but I don’t know how to pan in the image later on…

Here is my screenshot:

Thanks a lot in advance for any pointer!