https://bugs.kde.org/show_bug.cgi?id=498798
caulier.gil...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |caulier.gil...@gmail.com
--- Comment #3 from caulier.gil...@gmail.com ---
Hi,
The debug traces are printed ont he console under Linux to show advanced
information about digiKam processing. This include the ExifTool command line
parameters.
Under Windows, this such console rules do not exists. You need to use the
DebugView program from Microsoft for that, as explained here :
https://www.digikam.org/contribute/#windows-host
The ExifTool debug traces will look like this:
digikam.metaengine: Check ExifTool availability: true
digikam.metaengine: ExifTool "Load Chunks" "-TagsFromFile
/mnt/data/Images/RAW/IMG_0057.CR3 -all:all -icc_profile -o -.exv"
digikam.metaengine: ExifToolProcess::readOutput(): ExifTool command completed
digikam.metaengine: ExifTool complete command for action "Load Chunks" with
elasped time (ms): 223
digikam.metaengine: EXV chunk size: 3807
digikam.metaengine: ExifTool parsed command for action "Load Chunks" 1
properties decoded
digikam.metaengine: ExifTool complete "Load Chunks" for
"/mnt/data/Images/RAW/IMG_0057.CR3"
digikam.metaengine: Metadata chunk loaded with ExifTool
digikam.metaengine: Loading metadata with "ExifTool" backend from
"/mnt/data/Images/RAW/IMG_0057.CR3"
digikam.metaengine: Exif color-space tag is sRGB. Using default sRGB ICC
profile.
Here ExifTool is used to extract the color profile from a CR3 RAW file before
to preview image. The command line arguments are:
"-TagsFromFile /mnt/data/Images/RAW/IMG_0057.CR3 -all:all -icc_profile -o
-.exv"
Best
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
