-
Notifications
You must be signed in to change notification settings - Fork 79
JPEG hul Messages
DTT segment without previous DTI
Needs review
- Type: ErrorMessage
- Source location: JpegModule.java L1227
- Examples: Needed
Needs review
Needs review
Unexpected end of file
Needs review
- Type: ErrorMessage
- Source location: JpegModule.java L654
- Examples: 1
Needs review
Needs review
I/O exception processing Exif metadata
Needs review
- Type: ErrorMessage
- Source location: JpegExif.java L168
- Examples: Needed
Needs review
Needs review
Invalid JPEG header
Needs review
- Type: ErrorMessage
- Source location: JpegModule.java L887
- Examples: 1
Needs review
Needs review
JFIF APP0 marker not at beginning of file
Needs review
- Type: ErrorMessage
- Source location: JpegModule.java L928
- Examples: Needed
Needs review
Needs review
Marker not valid in context
Needs review
- Type: ErrorMessage
- Source location: JpegModule.java L645
- Examples: 1
Needs review
Needs review
Expected marker byte 255, got ...
Needs review
- Type: ErrorMessage
- Source location: JpegModule.java L489
- Examples: 1
Needs review
Needs review
SPIFF marker not at beginning of file
Needs review
- Type: ErrorMessage
- Source location: JpegModule.java L1131
- Examples: Needed
Needs review
Needs review
File does not begin with SPIFF, Exif or JFIF segment
Needs review
- Type: ErrorMessage
- Source location: JpegModule.java L503
- Examples: 1
When this error is raised for a well-formed but not valid file it typically hints at an uncommon but not necessarily broken file structure. From the JHOVE documentation:
A file which consists of a JPEG data stream, but does not contain the required segments for a JFIF, SPIFF, Exif, JTIP, or JPEG-LS file is considered well-formed but not valid.
In particular, the most common JPEG file formats JFIF and Exif expect a file to start with the hex sequence ffd8 ffe0 (SOI + APP0) or ffd8 ffe1 (SOI + APP1), respectively. However, the original JPEG specification (ITU-T T.81, Annex B) allows other data immediately after the SOI marker (e.g., a DQT marker or other APPn segments) as well. That may not be in line with one of the abovementioned formats though which restrict the file structure in one way or another, leading to this error.
So as long as a file with this error opens correctly in a viewer (better yet, in several different viewers) and has no other errors it may just be an uncommon JPEG variant, making the final verdict a file format policy question.
As long as this is the only error in a file one of the following measures may be appropriate:
- Ignoring the error i.e., accepting the file format although it is (very) uncommon.
- Converting it to another, more common JPEG format like JFIF. (TODO With which tool?)
- Adding an APP0 segment like ffe0 0010 4a46494600 0102 00 0001 0001 00 00 (must be adapted to the concrete file!) after the SOI marker to turn the file into a JFIF file. However, this is adventurous at best; don't try this at home!
Error creating temporary file. Check your configuration
Needs review
- Type: ErrorMessage
- Source location: JpegExif.java L69
- Examples: Needed
Needs review
Needs review
Unrecognized tiling data
Needs review
- Type: ErrorMessage
- Source location: JpegModule.java L1519
- Examples: Needed
Needs review
Needs review
TIFF-HUL module required to report Exif data
Needs review
- Type: InfoMessage
- Source location: JpegModule.java L1054
- Examples: Needed
Needs review
Needs review