Closed boxerab closed 2 years ago
This doesn't look like a bug to me: the image is truncated immediately after the start of the SOT marker segment, which is why no meaningful values of lsot, isot, and so on can be read. This causes an exception in struct.unpack, which is handled by the bytestr conversion function, resulting in the "-9999" fallback values.
The validation output also provides several clues that something is seriously wrong with the image:
<tests>
<siz>
<rsizIsValid>False</rsizIsValid>
</siz>
<tileParts>
<tilePart>
<sot>
<lsotIsValid>False</lsotIsValid>
<isotIsValid>False</isotIsValid>
<tpsotIsValid>False</tpsotIsValid>
</sot>
<foundSODMarker>False</foundSODMarker>
<foundNextTilePartOrEOC>False</foundNextTilePartOrEOC>
</tilePart>
</tileParts>
<foundEOCMarker>False</foundEOCMarker>
</tests>
Yes, you're right. For some reason I though the SOT marker was intact. Closing.
Offending image:
jpylyzer_bad_sot.zip
snippet from jpylyzer output :