Johan van der Knijff

@mehclere See also ; in particular if you run into any unexplained IsoBuster 1005 errors, you might want to give IsoBuster 4.9 a try. IsoBuster's author did some major refactoring...

Embeddable Python packages still work under Wine: As for making pip work with these, see:

Abandoned Wine-based approach after trouble installing PyInstaller, and used Jpylyzer's Docker script instead: This seems to work, but I don't really understand how/why! EDIT - I think it uses this:...

FWIW I just came across this by chance, and this is now fixed in Jpylyzer. The fixed development version now correctly handles the missing Bits per Component Box, resulting in...

@fmw42 You're probably right, but IM's current behavior makes it impossible to distinguish between JPEGs that were actually compressed at 92% quality, and JPEGs for which the quality is unknown,...

A bit of further digging seems to confirm that IM actually determines the JPEG compression quality from the quantization tables, and not from some pre-defined metadata field:

We could repeatedly call IsoBuster for each session, using the `/s:` option. Then for each iteration write the ISO image using a naming suffix that allows us to figure out...

Update - the multisession case is further complicated by the fact that the file system within a session may link to previous sessions, see: and a bit of history: (Via...

I just stumbled across this issue again. In addition to the confusing message itself, the fact hat JHOVE exits with an error (instead of parsing the file) also doesn't seem...

Seems JHOVE 1.28 changes fixed this, so closing this issue now.