This question is not answered.


Permlink Replies: 94 - Pages: 7 [ Previous | 1 2 3 4 5 6 | Next ] - Last Post: 31-Oct-2017 17:26 Last Post By: AndreWolff Threads: [ Previous | Next ]
jGromit

Posts: 33,160
Registered: 31-Jan-2006
Re: jAlbum 14 mutilates Lightroom comments
Posted: 19-Jul-2017 06:59   in response to: davidekholm in response to: davidekholm
 
  Click to reply to this thread Reply
This got lost in the shuffle during jAlbum 14 beta testing. I'm away from my Windows platform, but I believe the attached image, one of André's, illustrates the problem. jAlbum settings don't matter. The skin doesn't matter. All that matters is the platform.

Add this image to a project. Right-click, and choose List metadata. Take a look at the EXIF Copyright field. If memory serves, on macOS, it displays correctly, but on Win10, the characters are incorrect. The difference carries over into the completed album.
karlmistelberger

Posts: 732
Registered: 5-Dec-2013
Re: jAlbum 14 mutilates Lightroom comments
Posted: 19-Jul-2017 07:26   in response to: jGromit in response to: jGromit
 
  Click to reply to this thread Reply
Confirmed:

http://karlmistelberger.jalbum.net/testjAlbum/index.html#img=Vecht%20Sahara%20140328%201005.jpg

Adobe jpeg.Color Transform=YCbCr
Adobe jpeg.DCT Encode Version=25600
Adobe jpeg.Flags 0=128
Adobe jpeg.Flags 1=0
Aperture Value=f/8,0
Bits Per Sample=8 8 8 bits/component/pixel
Brightness Value=9937/1280
Color Space=sRGB
Components Configuration=YCbCr
Compressed Bits Per Pixel=4 bits/pixel
Contrast=None
Copyright=©  2016 André Wolff
Custom Rendered=Normal process
Date/Time=2017:06:19 13:33:26
Date/Time Digitized=2014:03:28 10:05:16
Date/Time Original=2014:03:28 10:05:16
Digital Zoom Ratio=1
Exif Image Height=3264 pixels
Exif Image Width=4912 pixels
Exif Version=2.30
Exif thumbnail.Compression=JPEG (old-style)
Exif thumbnail.Resolution Unit=Inch
Exif thumbnail.Thumbnail Length=6961 bytes
Exif thumbnail.Thumbnail Offset=1506 bytes
Exif thumbnail.X Resolution=72 dots per inch
Exif thumbnail.Y Resolution=72 dots per inch
Exposure Bias Value=0 EV
Exposure Mode=Auto exposure
Exposure Program=Aperture priority
Exposure Time=1/200 sec
F-Number=f/8,0
File Source=Digital Still Camera (DSC)
File.File Modified Date=Mi Jul 19 07:11:09 +02:00 2017
File.File Name=Vecht Sahara 140328 1005.jpg
File.File Size=1253828 bytes
Flash=Flash did not fire, auto
FlashPix Version=1.00
Focal Length=44 mm
Focal Length 35=66 mm
Gps.GPS Latitude=52° 30' 27,2"
Gps.GPS Latitude Ref=N
Gps.GPS Longitude=6° 27' 42,26"
Gps.GPS Longitude Ref=E
Huffman.Number of Tables=4 Huffman tables
ISO Speed Ratings=100
Icc profile.Blue Colorant=(0,1431, 0,0606, 0,7141)
Icc profile.CMM Type=Lino
Icc profile.Class=Display Device
Icc profile.Color space=RGB 
Icc profile.Copyright=Copyright (c) 1998 Hewlett-Packard Company
Icc profile.Device Mfg Description=IEC http://www.iec.ch
Icc profile.Device Model Description=IEC 61966-2.1 Default RGB colour space - sRGB
Icc profile.Device manufacturer=IEC 
Icc profile.Device model=sRGB
Icc profile.Green Colorant=(0,3851, 0,7169, 0,0971)
Icc profile.Luminance=(76,0365, 80, 87,1246)
Icc profile.Measurement=1931 2° Observer, Backing (0, 0, 0), Geometry Unknown, Flare 1%, Illuminant D65
Icc profile.Media Black Point=(0, 0, 0)
Icc profile.Media White Point=(0,9505, 1, 1,0891)
Icc profile.Primary Platform=Microsoft Corporation
Icc profile.Profile Connection Space=XYZ 
Icc profile.Profile Date/Time=1998:02:09 06:49:00
Icc profile.Profile Description=sRGB IEC61966-2.1
Icc profile.Profile Size=3144
Icc profile.Red Colorant=(0,4361, 0,2225, 0,0139)
Icc profile.Signature=acsp
Icc profile.Tag Count=17
Icc profile.Technology=CRT 
Icc profile.Version=2.1.0
Icc profile.Viewing Conditions=view (0x76696577): 36 bytes
Icc profile.Viewing Conditions Description=Reference Viewing Condition in IEC61966-2.1
Icc profile.XYZ values=0,964 1 0,825
Image Description=Start van de wandeling, de parkeer plaats over het spoor.
Image Height=3264 pixels
Image Width=4912 pixels
Interoperability.Interoperability Index=Recommended Exif Interoperability Rules (ExifR98)
Interoperability.Interoperability Version=1.00
Iptc.Application Record Version=0
Iptc.Caption/Abstract=Start van de wandeling, de parkeer plaats over het spoor.
Iptc.Coded Character Set=UTF-8
Iptc.Copyright Notice=©  2016 André Wolff
Iptc.Date Created=2014:03:28
Iptc.Object Name=Parkeer 1 plaats
Iptc.Time Created=10:05:16+0000
Jpeg.Component 1=Y component: Quantization table 0, Sampling factors 2 horiz/2 vert
Jpeg.Component 2=Cb component: Quantization table 1, Sampling factors 1 horiz/1 vert
Jpeg.Component 3=Cr component: Quantization table 1, Sampling factors 1 horiz/1 vert
Jpeg.Compression Type=Baseline
Jpeg.Data Precision=8 bits
Jpeg.Image Height=3264 pixels
Jpeg.Image Width=4912 pixels
Jpeg.Number of Components=3
Lens Model=E PZ 16-50mm F3.5-5.6 OSS
Lens Specification=16-50mm f/3,5-5,6
Make=SONY
Max Aperture Value=f/5,6
Metering Mode=Multi-segment
Model=NEX-6
Orientation=Top, left side (Horizontal / normal)
Photometric Interpretation=RGB
Photoshop.Caption Digest=33 133 240 21 134 203 209 7 56 109 143 225 74 30 141 107
Photoshop.Color Halftoning Information=[72 values]
Photoshop.Color Transfer Functions=[112 values]
Photoshop.Global Altitude=30
Photoshop.Global Angle=30
Photoshop.Grid and Guides Information=0 0 0 1 0 0 2 64 0 0 2 64 0 0 0 0
Photoshop.JPEG Quality=3 (Low), Standard format, 3 scans
Photoshop.Pixel Aspect Ratio=1.0
Photoshop.Print Flags=0 0 0 0 0 0 0 0 1
Photoshop.Print Flags Information=0 1 0 0 0 0 0 0 0 2
Photoshop.Print Info 2=[237 values]
Photoshop.Print Scale=Centered, Scale 1.0
Photoshop.Print Style=[557 values]
Photoshop.Resolution Info=350x350 DPI
Photoshop.Seed Number=1
Photoshop.Slices=Vecht Sahara 140328 1005 (0,0,3264,4912) 1 Slices
Photoshop.Thumbnail Data=JpegRGB, 160x106, Decomp 50880 bytes, 1572865 bpp, 6961 bytes
Photoshop.URL List=0
Photoshop.Version Info=1 (Adobe Photoshop Elements, Adobe Photoshop Elements 15.0) 1
Printim.PrintIM Version=0300
Printim.Unknown tag (0x0002)=0x00000001
Printim.Unknown tag (0x0003)=0x00000022
Printim.Unknown tag (0x0101)=0x00000000
Recommended Exposure Index=100
Resolution Unit=Inch
Samples Per Pixel=3 samples/pixel
Saturation=None
Scene Capture Type=Standard
Scene Type=Directly photographed image
Sensitivity Type=Recommended Exposure Index
Sharpness=None
Shutter Speed Value=1/199 sec
Software=Adobe Photoshop Elements 15.0 (Windows)
Unknown tag (0xea1d)=0
User Comment=
White Balance=Daylight
White Balance Mode=Manual white balance
X Resolution=350 dots per inch
Xmp.XMP Value Count=36
Y Resolution=350 dots per inch
YCbCr Positioning=Datum point
xmp.aux:Lens=E PZ 16-50mm F3.5-5.6 OSS
xmp.aux:LensInfo=160/10 500/10 35/10 56/10
xmp.dc:creator=
xmp.dc:description=
xmp.dc:description[1]=Start van de wandeling, de parkeer plaats over het spoor.
xmp.dc:description[1]/xml:lang=x-default
xmp.dc:format=image/jpeg
xmp.dc:rights=
xmp.dc:rights[1]=©  2016 André Wolff
xmp.dc:rights[1]/xml:lang=x-default
xmp.dc:title=
xmp.dc:title[1]=Parkeer 1 plaats
xmp.dc:title[1]/xml:lang=x-default
xmp.photoshop:ColorMode=3
xmp.photoshop:DateCreated=2014-03-28T10:05:16
xmp.photoshop:ICCProfile=sRGB IEC61966-2.1
xmp.xmp:CreateDate=2014-03-28T10:05:16+01:00
xmp.xmp:CreatorTool=NEX-6 v1.00
xmp.xmp:MetadataDate=2017-06-19T13:33:26+02:00
xmp.xmp:ModifyDate=2017-06-19T13:33:26+02:00
xmp.xmpMM:DocumentID=adobe:docid:photoshop:1c3b323f-54e3-11e7-92f9-c65b251ac728
xmp.xmpMM:History=
xmp.xmpMM:History[1]=
xmp.xmpMM:History[1]/stEvt:action=saved
xmp.xmpMM:History[1]/stEvt:changed=/ 
xmp.xmpMM:History[1]/stEvt:instanceID=xmp.iid:8d21cbd6-98f7-0d4c-909b-1cb69a34fb4b
xmp.xmpMM:History[1]/stEvt:softwareAgent=Adobe Photoshop Elements 15.0 (Windows)
xmp.xmpMM:History[1]/stEvt:when=2017-06-19T13:33:26+02:00
xmp.xmpMM:History[2]=
xmp.xmpMM:History[2]/stEvt:action=saved
xmp.xmpMM:History[2]/stEvt:changed=/ 
xmp.xmpMM:History[2]/stEvt:instanceID=xmp.iid:0674c943-605b-f347-b806-ee5ac8bdca11
xmp.xmpMM:History[2]/stEvt:softwareAgent=Adobe Photoshop Elements 15.0 (Windows)
xmp.xmpMM:History[2]/stEvt:when=2017-06-19T13:33:26+02:00
xmp.xmpMM:InstanceID=xmp.iid:0674c943-605b-f347-b806-ee5ac8bdca11
xmp.xmpMM:OriginalDocumentID=C2B76CD538AE1C266A6ECF25C0A4FA1D8
jGromit

Posts: 33,160
Registered: 31-Jan-2006
Re: jAlbum 14 mutilates Lightroom comments
Posted: 19-Jul-2017 07:51   in response to: karlmistelberger in response to: karlmistelberger
 
  Click to reply to this thread Reply
karlmistelberger wrote:
Confirmed:

What result do you get in Windows 10? If you're testing only in Linux, you can't possibly be seeing or understanding the problem.
AndreWolff

Posts: 2,127
Registered: 14-Dec-2007
Re: jAlbum 14 mutilates Lightroom comments
Posted: 19-Jul-2017 09:18   in response to: davidekholm in response to: davidekholm
 
  Click to reply to this thread Reply
Attachment TestMetaData.zip (4,7 MB)
davidekholm wrote:
I think you need to make a minimal album project that demonstrates this problem with this image, zip it and attach it here.

Well David, I see the same problem with the Minimal skin, see my Minimal test album.
In the attached zip file is the whole project.

I hope this helps!
davidekholm

Posts: 21,446
Registered: 18-Oct-2002
Re: jAlbum 14 mutilates Lightroom comments
Posted: 19-Jul-2017 11:15   in response to: AndreWolff in response to: AndreWolff
 
  Click to reply to this thread Reply
Now I can reproduce this. Well, first the whole header for this thread is wrong. jAlbum doesn't "mutilate" any comments. It's about jAlbum not reading some EXIF fields correctly anymore on some platforms. jAlbum never writes these fields so it can't "mutilate" them.

Further, this problem only relates to old style deprecated EXIF comments and copyright fields, the preferred xmp equivalents are correctly presented. Please use them instead.

So why break something that worked before? This is an unfortunate side effect of moving from our modified outdated version of metadata-extractor to the official, maintained version which reads metadata from many file types and not only from JPEG files. Unlike xmp, EXIF has never been good at supporting "foreign" characters. There are various ways to present them. More clever "EXIF writers" add an encoding specification to the first 8 bytes. If this is missing, the EXIF reader has to make guesses. My earlier modified version of metadata-extractor would fall back to using jAlbum's encoding setting, so if you had that one set to an encoding that matched your EXIF data, then it would work. The current metadata-extractor however relies solely on the platform's default encoding, which on Windows is "Cp1252" and on Mac "UTF-8", this is why it worked on Mac cause your sample images had their EXIF strings UTF-8 encoded.

My advice is to simply rely on the xmp based equivalents. If you really want to be able to use the old EXIF fields you'd have to file a bug report / feature request to the maintainers of metadata-extractor to basically alter their API so one can specify a default encoding for EXIF strings and simply not assume the platforms' encoding.
AndreWolff

Posts: 2,127
Registered: 14-Dec-2007
Re: jAlbum 14 mutilates Lightroom comments
Posted: 19-Jul-2017 11:36   in response to: davidekholm in response to: davidekholm
 
  Click to reply to this thread Reply
davidekholm wrote:
Now I can reproduce this. Well, first the whole header for this thread is wrong. jAlbum doesn't "mutilate" any comments. It's about jAlbum not reading some EXIF fields correctly anymore on some platforms. jAlbum never writes these fields so it can't "mutilate" them.
Glad you can reproduce it! Please change the thread header, I have no privilege to do that.
Further, this problem only relates to old style deprecated EXIF comments and copyright fields, the preferred xmp equivalents are correctly presented. Please use them instead.
Well David these data are written by Adobe Lightroom 5.7, I don't think I can do anything to this.
So why break something that worked before? This is an unfortunate side effect of moving from our modified outdated version of metadata-extractor to the official, maintained version which reads metadata from many file types and not only from JPEG files. Unlike xmp, EXIF has never been good at supporting "foreign" characters. There are various ways to present them. More clever "EXIF writers" add an encoding specification to the first 8 bytes. If this is missing, the EXIF reader has to make guesses. My earlier modified version of metadata-extractor would fall back to using jAlbum's encoding setting, so if you had that one set to an encoding that matched your EXIF data, then it would work. The current metadata-extractor however relies solely on the platform's default encoding, which on Windows is "Cp1252" and on Mac "UTF-8", this is why it worked on Mac cause your sample images had their EXIF strings UTF-8 encoded.
My advice is to simply rely on the xmp based equivalents. If you really want to be able to use the old EXIF fields you'd have to file a bug report / feature request to the maintainers of metadata-extractor to basically alter their API so one can specify a default encoding for EXIF strings and simply not assume the platforms' encoding.
Again I do not know how to change that in Lightroom, but I will have a like and report back if I have a solution.

But there is a solution, even with the current jAlbum 14 version:

PhotoBlogger shows the caption sometimes correctly, see the end of this thread. But I do not know which code Laza uses to display the caption. And I can't explain the difference between this PhotoBlogger album and the PhotoBlogger test album used above.
AndreWolff

Posts: 2,127
Registered: 14-Dec-2007
Re: jAlbum 14 mutilates Lightroom comments
Posted: 19-Jul-2017 12:14   in response to: AndreWolff in response to: AndreWolff
 
  Click to reply to this thread Reply
I know now a trick to solve this!

In all the problem albums was the xmp check-mark not set, see attached screenshot.
Setting that checkmark solves the problem in jAlbum 14.
This is not required in jAlbum 13.
davidekholm

Posts: 21,446
Registered: 18-Oct-2002
Re: jAlbum 14 mutilates Lightroom comments
Posted: 19-Jul-2017 17:43   in response to: AndreWolff in response to: AndreWolff
Correct
  Click to reply to this thread Reply
AndreWolff wrote:
I know now a trick to solve this!

In all the problem albums was the xmp check-mark not set, see attached screenshot.
Setting that checkmark solves the problem in jAlbum 14.
This is not required in jAlbum 13.


Yes, xmp should be checked by default. It is a new and better standard. One should have very good reasons for unchecking it. And now you know why this wasn't needed on jAlbum 13 (see my lengthy explanation above)
AndreWolff

Posts: 2,127
Registered: 14-Dec-2007
Re: jAlbum 14 mutilates Lightroom comments
Posted: 19-Jul-2017 19:00   in response to: davidekholm in response to: davidekholm
 
  Click to reply to this thread Reply
davidekholm wrote:
Yes, xmp should be checked by default. It is a new and better standard. One should have very good reasons for unchecking it. And now you know why this wasn't needed on jAlbum 13 (see my lengthy explanation above)
I wonder now who will uncheck this xmp check-mark?

Is it not better to remove that checkmark and set it alsways true in jAlbum?
AndreWolff

Posts: 2,127
Registered: 14-Dec-2007
Re: jAlbum 14 mutilates Lightroom comments
Posted: 21-Jul-2017 12:51   in response to: AndreWolff in response to: AndreWolff
 
  Click to reply to this thread Reply
Solved by setting the xmp check mark, but this works only for the comment, not for the camara data.

Edited by: AndreWolff on 25-Jul-2017 10:43
davidekholm

Posts: 21,446
Registered: 18-Oct-2002
Re: jAlbum 14 mutilates Lightroom comments
Posted: 21-Jul-2017 14:25   in response to: AndreWolff in response to: AndreWolff
 
  Click to reply to this thread Reply
AndreWolff wrote:
davidekholm wrote:
Yes, xmp should be checked by default. It is a new and better standard. One should have very good reasons for unchecking it. And now you know why this wasn't needed on jAlbum 13 (see my lengthy explanation above)
I wonder now who will uncheck this xmp check-mark?

Is it not better to remove that checkmark and set it alsways true in jAlbum?


Well, a skin developer might want to investigate the handling of EXIF data that may be hidden by xmp equivalents, another user may want to ignore xmp data for whatever reason (broken/incorrect xmp data for instance). Remember the default setting is checked and that this is an advanced setting.
AndreWolff

Posts: 2,127
Registered: 14-Dec-2007
Re: jAlbum 14 mutilates Lightroom comments
Posted: 25-Jul-2017 10:41   in response to: davidekholm in response to: davidekholm
 
  Click to reply to this thread Reply
Attachment jAlbumBug.PNG (599,9 KB)
David, setting the xmp check-mark solves the problem for the image comment, but not for the camara data.

To see this open this Amsterdam PhotoSwipe slide page.
You see the caption is OK, but click the arrow icon in the upper right corner and select menu item 'Show/Hide Exif data', next you see that my name and the copyright statement is still mutilated.

See also enclosed screen shot.
AndreWolff

Posts: 2,127
Registered: 14-Dec-2007
Re: jAlbum 14 mutilates Lightroom comments
Posted: 25-Jul-2017 10:43   in response to: AndreWolff in response to: AndreWolff
 
  Click to reply to this thread Reply
The solution does not work for camara data
davidekholm

Posts: 21,446
Registered: 18-Oct-2002
Re: jAlbum 14 mutilates Lightroom comments
Posted: 25-Jul-2017 14:33   in response to: AndreWolff in response to: AndreWolff
 
  Click to reply to this thread Reply
AndreWolff wrote:
The solution does not work for camara data

Please attach that image.
Also, if you feel this is a bug in the existing metadata-extractor library, please post a report about it to the metadata-extractor GitHub repository.
AndreWolff

Posts: 2,127
Registered: 14-Dec-2007
Re: jAlbum 14 mutilates Lightroom comments
Posted: 25-Jul-2017 14:47   in response to: davidekholm in response to: davidekholm
 
  Click to reply to this thread Reply
davidekholm wrote:
Please attach that image.
See enclosed Amsterdam-140622_1158.jpg image ( I had to reduce it in size).
Also, if you feel this is a bug in the existing metadata-extractor library, please post a report about it to the metadata-extractor GitHub repository.
I think you did this already: see here and here.

Edited by: AndreWolff on 25-Jul-2017 17:40:

The List metadata output of this image are enclosed.

I see there the wrong text:
Artist=André Wolff
and
Copyright=Copyright © André Wolff

But also correct text in:

Iptc.Copyright Notice=Copyright © André Wolff
xmp.dc:rights[1]=Copyright © André Wolff
Iptc.By-line=André Wolff
xmp.dc:creator[1]=André Wolff

How can I fetch these strings?

Edited by: AndreWolff on 25-Jul-2017 17:40

Reading Template file variables photographer, copyright and writer all delivers empty strings!

Edited by: AndreWolff on 25-Jul-2017 18:31
Legend
Forum admins
Helpful Answer
Correct Answer

Point your RSS reader here for a feed of the latest messages in all forums