Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 660AB200D53 for ; Mon, 20 Nov 2017 10:03:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 647EB160BEC; Mon, 20 Nov 2017 09:03:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B0235160BF9 for ; Mon, 20 Nov 2017 10:03:08 +0100 (CET) Received: (qmail 87345 invoked by uid 500); 20 Nov 2017 09:03:07 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 87000 invoked by uid 99); 20 Nov 2017 09:03:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Nov 2017 09:03:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id C3C52C701F for ; Mon, 20 Nov 2017 09:03:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.011 X-Spam-Level: X-Spam-Status: No, score=-99.011 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KB_WAM_FROM_NAME_SINGLEWORD=0.2, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id QJ87UPKw0dRr for ; Mon, 20 Nov 2017 09:03:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id BBCC761103 for ; Mon, 20 Nov 2017 09:03:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id A911DE095A for ; Mon, 20 Nov 2017 09:03:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id BE69C240D2 for ; Mon, 20 Nov 2017 09:03:00 +0000 (UTC) Date: Mon, 20 Nov 2017 09:03:00 +0000 (UTC) From: "Bruno P. Kinoshita (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IMAGING-205) Imaging (Apache Sanselan) produces "odd offsets" in (EXIF) metadata MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 20 Nov 2017 09:03:09 -0000 [ https://issues.apache.org/jira/browse/IMAGING-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258968#comment-16258968 ] Bruno P. Kinoshita commented on IMAGING-205: -------------------------------------------- Hi Joakim, So I've found a way to get exiftool's htmldump to have no odd offsets. Push a single commit here https://github.com/kinow/commons-imaging/tree/tiff-odd-offsets-1 I slowly read the code, and found that these two parts were simply adding the length in bytes of the field plus a previous offset. Which could result in odd offsets. It would help me a lot if you were able to checkout my branch, `mvn clean package`, use the jar in your app, and let me know if that works fine for you. Once I realized where the odd bytes were coming from, this seemed like the simplest solution (occam's razor). But before we consider this naive solution as a definitive solution, I'd like to: * have a confirmation that the odd bytes is gone and the metadata and image are still *valid/good/correct/etc* * have a better understand of the different between a TIFFOutputItem and TIFFOutputField. The latter has a method, writeField, that seems to be correctly handling offsets oddness. * write a unit test * find the parts of the specification that define that behaviour, and add links to them here, in the unit test, and in the javadoc of the class where the fix is applied > Imaging (Apache Sanselan) produces "odd offsets" in (EXIF) metadata > ------------------------------------------------------------------- > > Key: IMAGING-205 > URL: https://issues.apache.org/jira/browse/IMAGING-205 > Project: Commons Imaging > Issue Type: Bug > Components: imaging.* > Reporter: Joakim Knudsen > Assignee: Bruno P. Kinoshita > Priority: Critical > Attachments: 20171030_214812.jpg, 20171030_214812_copy_desktop.JPG, 20171030_21481_COPY.jpg, DSC_5506.JPG, DSC_5506_copy_desktop.JPG, Gaboxjellyfish-changedexifmetadata.jpg, Gaboxjellyfish.jpg, after.html, before.html > > > I'm using the "last stable version" of Apache Sanselan 0.97 in an Android project (app). I have not upgraded to Commons Imaging yet, since the website says there is no stable release yet. Meanwhile, there are bugs in Sanselan. > If I run the [sample code method WriteExifMetadataExample.changeExifMetadata|http://svn.apache.org/repos/asf/commons/proper/sanselan/trunk/src/test/java/org/apache/sanselan/sampleUsage/WriteExifMetadataExample.java?p=820841] on an image, which updates the Apterture and GPS tags, the resulting image fails to validate (through Phil Harvey's [ExifTool software|https://sno.phy.queensu.ca/~phil/exiftool/]): > {noformat} > > exiftool.exe -validate -error -warning -a "..\20171030_21481_COPY.jpg" > Validate : 19 Warnings (17 minor) > Warning : [minor] Odd offset for IFD0 tag 0x010f > Warning : [minor] Odd offset for IFD0 tag 0x011a > Warning : [minor] Odd offset for IFD0 tag 0x011b > Warning : [minor] Odd offset for IFD0 tag 0x0131 > Warning : [minor] Odd offset for IFD0 tag 0x0132 > Warning : [minor] Odd offset for ExifIFD tag 0x829a > Warning : [minor] Odd offset for ExifIFD tag 0x829d > Warning : [minor] Odd offset for ExifIFD tag 0x9003 > Warning : [minor] Odd offset for ExifIFD tag 0x9004 > Warning : [minor] Odd offset for ExifIFD tag 0x9202 > Warning : [minor] Odd offset for ExifIFD tag 0x9205 > Warning : [minor] Odd offset for ExifIFD tag 0x920a > Warning : [minor] Odd offset for ExifIFD tag 0x9286 > Warning : Non-standard count (1) for GPS tag 0x0001 GPSLatitudeRef > Warning : [minor] Odd offset for GPS tag 0x0002 > Warning : Non-standard count (1) for GPS tag 0x0003 GPSLongitudeRef > Warning : [minor] Odd offset for GPS tag 0x0004 > Warning : [minor] Odd offset for IFD1 tag 0x011a > Warning : [minor] Odd offset for IFD1 tag 0x011b > {noformat} > I need some advice on how to proceed here. Since Sanselan does not appear to do what it should (even on very basic metadata editing), am I correct to assume that the current version of Commons Imaging does a better job? :-) -- This message was sent by Atlassian JIRA (v6.4.14#64029)