[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 309341] New: digiKam doesn't write XMP-tiff Orientation tag for raw files
From:       Elle Stone <l.elle.stone () gmail ! com>
Date:       2012-10-31 20:11:46
Message-ID: bug-309341-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=309341

            Bug ID: 309341
          Severity: normal
           Version: 2.9.0
          Priority: NOR
          Assignee: digikam-devel@kde.org
           Summary: digiKam doesn't write XMP-tiff Orientation tag for raw
                    files
    Classification: Unclassified
                OS: Linux
          Reporter: l.elle.stone@gmail.com
          Hardware: openSUSE RPMs
            Status: UNCONFIRMED
         Component: Sidecar Management
           Product: digikam

Under digiKam settings/Metadata/Rotation, I have "When rotating a file, Rotate
only by setting a flag" and "Write flag to metadata if possible". Under
settings/Behavior I have "Write to sidecar files"/"Write to XMP sidecar only". 
When using the rotation arrows to change the image rotation, the orientation
tag is correctly written to the .jpg.xmp sidecar file for jpegs. But it is
never written for .cr2.xmp or for .mrw.xmp sidecar files. So I'm guessing it
isn't being written for any raw files at all.

Reproducible: Always

Steps to Reproduce:
1.Select a raw file that needs to have the rotation flag changed.
2.Change the flag using the rotation arrows.
3.Select Image/"Write metadata to image"
4.Use exiftool to check the sidecar orientation tag. It doesn't change.
Actual Results:  
The image display changes orientation like it should. But the information in
the raw file sidecar doesn't change. (It changes for jpeg sidecars, but not for
raw file sidecars).

Expected Results:  
For both raw file sidecars and jpg sidecars, the orientation flag should change
to reflect the actual orientation that was set using the rotation arrows.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]