Panasonic Lumix S1R Mk II Problem with ExifTool

Started by romanholiday, April 27, 2025, 08:49:34 AM

Previous topic - Next topic

romanholiday

About 25% of the photos taken with this new Lumix camera are corrupted by ExifTool. Even the latest version, 13.28 does not fix this.

Any tag that is changed by ExifTool results in the file being corrupt and not able to be read properly by Adobe Camera RAW and/or Lightroom.


romanholiday

Here is one of these images:-

https://drive.google.com/file/d/1c-PjSU7DIw2wYKQj3Z0r_ni8HLQNlO5M/view?usp=sharing

It is an untouched RAW file straight from the camera.

Thanks for your help!

StarGeek

There are a bunch of duplicate tags and a non-standard EXIF block. (MyExifTags is a shortcut of mine for the most common EXIF tags I'm interested in)

C:\>exiftool -a -s -G1 -MyExifTags Y:\!temp\x\y\P1000642.RW2
[IFD0]          Copyright                       :
[IFD0]          Copyright                       :
[ExifIFD]       DateTimeOriginal                : 2025:04:10 07:43:37
[ExifIFD]       DateTimeOriginal                : 2025:04:10 07:43:37
[ExifIFD]       OffsetTimeOriginal              : -07:00
[ExifIFD]       OffsetTimeOriginal              : -07:00
[ExifIFD]       CreateDate                      : 2025:04:10 07:43:37
[ExifIFD]       CreateDate                      : 2025:04:10 07:43:37
[ExifIFD]       OffsetTimeDigitized             : -07:00
[ExifIFD]       OffsetTimeDigitized             : -07:00
[IFD0]          ModifyDate                      : 2025:04:10 07:43:37
[ExifIFD]       OffsetTime                      : -07:00
[ExifIFD]       OffsetTime                      : -07:00
[IFD0]          Artist                          :
[IFD0]          Artist                          :
[IFD0]          Make                            : Panasonic
[IFD0]          Make                            : Panasonic
[IFD0]          Model                           : DC-S1RM2
[IFD0]          Model                           : DC-S1RM2

C:\>exiftool -g1 -a -s -warning -validate  Y:\!temp\x\y\P1000642.RW2
---- ExifTool ----
Warning                         : [minor] Non-standard EXIF at TIFF-IFD0-JPEG-APP1-IFD0
Warning                         : [minor] Undefined value for MakerNotes:ClearRetouchValue
Validate                        : 2 Warnings (all minor)

A simple edit gives a warning
C:\>exiftool -P -overwrite_original -description=test "Y:\!temp\x\y\P1000642 - Copy.RW2"
Warning: [minor] Adding 10738618 bytes of padding before fixed-offset image data - Y:/!temp/x/y/P1000642 - Copy.RW2
    1 image files updated

Adobe Bridge won't load this file, so I can't test this file any further.
"It didn't work" isn't helpful. What was the exact command used and the output.
Read FAQ #3 and use that cmd
Please use the Code button for exiftool output

Please include your OS/Exiftool version/filetype

Phil Harvey

Thanks for this report!  And for the sample image to allow me to reproduce this problem.

I've added a patch to ExifTool 13.29 to fix this issue, and just released this new version.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

romanholiday

It works! So fast of you  :) Thank you so much!

However, I still get that "minor" warning. What does this mean? Anything to worry about?

StarGeek

See this post.

For some reason, the image data is at a fixed point in the file. Any edits to the file means the image data must remain at that point, even though exiftool has optimized the metadata structures (see FAQ #13, Why is my file smaller after I use ExifTool to write information?).

In order to keep the image data at that fixed point, exiftool has to add padding between the location of the metadata and the image data.

To quote Phil from that post
Quote from: Phil Harvey on September 16, 2022, 01:11:06 PMSo the raw data offsets in the file are not used.  All I can do is assume that these offsets have been hard coded for this camera model.  I can't express how insanely bad form this is for the Panasonic programmers.  It is bad enough to have 2 pointers to the raw data (there should only ever be one pointer to one piece of data), but to ignore them both and hard code the offset is another level of stupidity.
"It didn't work" isn't helpful. What was the exact command used and the output.
Read FAQ #3 and use that cmd
Please use the Code button for exiftool output

Please include your OS/Exiftool version/filetype

romanholiday