unusual warnings

[bigfire60]

Any clues to the cause/source of these warnings?

Code Select Expand

Warning                         : [minor] Unknown APP5 'debuginfo' segment
Warning                         : [minor] Unknown APP4 segment


[Phil Harvey]

ExifTool doesn't recognize the data in these JPEG segments.  You can use the -v3 or higher options to view the raw data.

- Phil

[bigfire60]

Thanks Phil. Any way to clean/remove that data?
TagsFromFile appears to copy them along with valid tags.

[Phil Harvey]

-tagsFromFile will not copy unknown APP segments.

- Phil

[bigfire60]

Can you point out what I'm missing?

Code Select Expand

D:\windata\exif>exiftool -validate -warning -error -a 2024-0092.jpg
Validate                        : 2 Warnings (all minor)
Warning                        : [minor] Unknown APP5 'debuginfo' segment
Warning                        : [minor] Unknown APP4 segment

D:\windata\exif>exiftool -overwrite_original -TagsFromFile 2024-0092.jpg -all:all 2024-0092.jpg
    1 image files updated

D:\windata\exif>exiftool -validate -warning -error -a 2024-0092.jpg
Validate                        : 2 Warnings (all minor)
Warning                        : [minor] Unknown APP5 'debuginfo' segment
Warning                        : [minor] Unknown APP4 segment

D:\windata\exif>


[bigfire60]

I figured it out, thanks.

Code Select Expand

D:\windata\exif>exiftool -overwrite_original -all:all= -TagsFromFile 2024-0092.jpg -all:all 2024-0092.jpg


[bigfire60]

OK, so although it did resolve the unknown APP segments,
this is something that I didn't expect.

Here is the region data prior to execution of the TagsFromFile command:


And after:


The AppliedToDimensions tags are missing.
Any ideas?

[Phil Harvey]

That shouldn't happen if these tags are written properly and you aren't using a very old version of ExifTool.

Could you post the sample image for testing?

- Phil

[bigfire60]

I am running 12.8.0.0. which provided your recent ACDSee improvements.

Here's a link to the sample file: test file

[StarGeek]

Do you have a test file that has the original ACDSee region?

I tested Phil's config on an ACDSee sample I have and it came out correctly.  In your file, the AppliedToDimensions part is ending up separate from the rest, outside of the "Region" block, which isn't happening with my test file.

Code Select Expand

         <mwg-rs:Regions rdf:parseType="Resource">
            <mwg-rs:RegionList>
               <rdf:Bag>
                  <rdf:li rdf:parseType="Resource">
                     <mwg-rs:Name>Vern Beausoleil</mwg-rs:Name>
                     <mwg-rs:Type>Face</mwg-rs:Type>
                     <mwg-rs:Area rdf:parseType="Resource">
                        <stArea:x>0.440972</stArea:x>
                        <stArea:y>0.461454</stArea:y>
                        <stArea:w>0.31002</stArea:w>
                        <stArea:h>0.555066</stArea:h>
                        <stArea:unit>normalized</stArea:unit>
                     </mwg-rs:Area>
                  </rdf:li>
               </rdf:Bag>
            </mwg-rs:RegionList>
         </mwg-rs:Regions>
         <mwg-rs:AppliedToDimensions rdf:parseType="Resource">
            <stDim:w>1816</stDim:w>
            <stDim:h>4032</stDim:h>
            <stDim:unit>pixel</stDim:unit>
         </mwg-rs:AppliedToDimensions>
My results from the using the ACDSee sample from this post with Phil's config

Code Select Expand

  <mwg-rs:Regions rdf:parseType='Resource'>
   <mwg-rs:AppliedToDimensions rdf:parseType='Resource'>
    <stDim:h>683</stDim:h>
    <stDim:unit>pixel</stDim:unit>
    <stDim:w>1024</stDim:w>
   </mwg-rs:AppliedToDimensions>
   <mwg-rs:RegionList>
    <rdf:Bag>
     <rdf:li rdf:parseType='Resource'>
      <mwg-rs:Area rdf:parseType='Resource'>
       <stArea:h>0.194964</stArea:h>
       <stArea:w>0.107262</stArea:w>
       <stArea:x>0.291964</stArea:x>
       <stArea:y>0.156188</stArea:y>
      </mwg-rs:Area>
      <mwg-rs:Name>Austin Powers</mwg-rs:Name>
      <mwg-rs:Type>Face</mwg-rs:Type>
     </rdf:li>
     <rdf:li rdf:parseType='Resource'>
      <mwg-rs:Area rdf:parseType='Resource'>
       <stArea:h>0.190366</stArea:h>
       <stArea:w>0.104732</stArea:w>
       <stArea:x>0.588839</stArea:x>
       <stArea:y>0.387371</stArea:y>
      </mwg-rs:Area>
      <mwg-rs:Name>Jane Doe</mwg-rs:Name>
      <mwg-rs:Type>Face</mwg-rs:Type>
     </rdf:li>
     <rdf:li rdf:parseType='Resource'>
      <mwg-rs:Area rdf:parseType='Resource'>
       <stArea:h>0.194504</stArea:h>
       <stArea:w>0.107009</stArea:w>
       <stArea:x>0.418155</stArea:x>
       <stArea:y>0.326493</stArea:y>
      </mwg-rs:Area>
      <mwg-rs:Name>Mini Me</mwg-rs:Name>
      <mwg-rs:Type>Face</mwg-rs:Type>
     </rdf:li>
     <rdf:li rdf:parseType='Resource'>
      <mwg-rs:Area rdf:parseType='Resource'>
       <stArea:h>0.207815</stArea:h>
       <stArea:w>0.111308</stArea:w>
       <stArea:x>0.500888</stArea:x>
       <stArea:y>0.178508</stArea:y>
      </mwg-rs:Area>
      <mwg-rs:Name>John Doe</mwg-rs:Name>
      <mwg-rs:Type>Face</mwg-rs:Type>
     </rdf:li>
     <rdf:li rdf:parseType='Resource'>
      <mwg-rs:Area rdf:parseType='Resource'>
       <stArea:h>0.261101</stArea:h>
       <stArea:w>0.148017</stArea:w>
       <stArea:x>0.744227</stArea:x>
       <stArea:y>0.279751</stArea:y>
      </mwg-rs:Area>
      <mwg-rs:Name>Mike Miller</mwg-rs:Name>
      <mwg-rs:Type>Face</mwg-rs:Type>
     </rdf:li>
    </rdf:Bag>
   </mwg-rs:RegionList>
  </mwg-rs:Regions>

[bigfire60]

StarGeek,
I went back as well to the original file with the ACDSee regions
and ran ACDSeeRegions2MWGRegion to create the MWG Regions.
As you reported, that process seemed to work properly.
I'm not sure how the file that I posted got into that condition, but it sounds like
it contained an improperly formatted MWG Region.
I do have a few files in this condition.
I'll see if I can find the common link to try and determine what software/condition caused the issue.

Thanks for the reply.

[Phil Harvey]

Yes.  In your sample the AppliedToDimensions is written incorrectly as stand-alone tags whereas they should be elements within the Regions structure (called RegionInfo by ExifTool).

- Phil

[bigfire60]

Thanks for the confirmation Phil.
Found the culprit. XnViewMP.