![apache edit exif metadata apache edit exif metadata](https://cdn.ttc.io/i/fit/1035/0/sm/0/plain/exposingtheinvisible.org/ckeditor_assets/pictures/126/content_tellall.png)
Just to eliminate my phone/camera from the equation, I've downloaded a stock JPEG onto my app and written UserComment and Caption/Abstract to it. Warning : Odd offset for ExifIFD tag 0x829a Warning : Odd offset for ExifIFD tag 0x9292 Warning : Odd offset for ExifIFD tag 0x9003 Warning : Odd offset for ExifIFD tag 0x9201 Could you please have a look at the attached file test_bare.jpg and see if it looks messed up?Ĭ:\Users\joakimk\Downloads\exiftool-10.46>exiftool.exe -validate -warning -a. So I'm starting to think this is maybe a losing battle - that some of the bugs ExifTools is reporting are maybe due to the phone? If the starting point (original, bare JPEG) is flawed, then it's really hard to debug my app. Even if I don't modify it with my app at all, ExifTool still finds problems. Warning : Wrong IFD for ExifIFD tag 0x010e ImageDescription (found in IFD0)īut first: I've attached a "plain" JPEG as generated by my cell phone (Nexus LG 5). It always ends up in the wrong IFD (IFD0, instead of. I think I'm able to write successfully to UserComment, and to the IPTC field Caption/Abstract, but I can't seem to write properly to the ImageDescription field. I've read the EXIF specification, and I understand more about the details for the tags I'm interested in (ImageDescription and UserComment). What does the "Wrong IFD" warning (on ImageDescription) actually tell me? I'm writing to that field in a much more simple way than what I do for UserComment I'm not using the "big hack" with the Unicode marker. If I validate a "plain" JPEG, taken with the same phone but with no metadata written to it, I still get "Odd offset" minor warnings. I'd really like to get it working with UTF-8, since I don't understand why UserComment specifically requires a different encoding than the other fields, where I can write UTF-8 directly (with no "markers" etc). I can only make ExifTool happy if I use UTF-16LE.Īlso, apparently, the content (text) has to be prefixed with a "Unicode marker": 7 bytes actually spelling out " UNICODE", with null-termination: 554E49434F444500Ĭould you please take a look at the attached file? As far as I can see, ExifTool no longer complains about the UserComment field. Apache Sanselan has some bugs, which I apparently have to work around. What I'm finding, is that the EXIF UserComment tag requires a specific charset - as warned by ExifTool.
![apache edit exif metadata apache edit exif metadata](https://a.fsdn.com/con/app/proj/edit-exif/screenshots/49259.jpg)
However, the errors/warnings you're referring to (from validate) refer to the ImageDescription field, and not the UserComment field we were looking at here?
#Apache edit exif metadata windows#
![apache edit exif metadata apache edit exif metadata](https://i.stack.imgur.com/scpv0.jpg)
Thumbnail Image : (Binary data 38439 bytes, use -b option to extract)Ĭ:\Users\joakimk\Downloads\exiftool-10.46> Viewing Cond Desc : Reference Viewing Condition in IEC 6
![apache edit exif metadata apache edit exif metadata](https://i.stack.imgur.com/mLQkJ.png)
Red Tone Reproduction Curve : (Binary data 2060 bytes, use -b option to extract) Green Tone Reproduction Curve : (Binary data 2060 bytes, use -b option to extract) Profile Description : sRGB IEC6 black scaledīlue Matrix Column : 0.14307 0.06061 0.7141īlue Tone Reproduction Curve : (Binary data 2060 bytes, use -b option to extract)ĭevice Model Desc : IEC 6 Default RGB Colour Space - sRGB Interoperability Index : R98 - DCF basic file (sRGB)ĭevice Attributes : Reflective, Glossy, Positive, ColorĬonnection Space Illuminant : 0.9642 1 0.82491 Warning : Invalid EXIF text encoding for UserComment C:\Users\joakimk\Downloads\exiftool-10.46>exiftool.exe.