From: Mathieu C. <mch...@gm...> - 2016-08-23 18:22:30
|
Hi Tom, Thanks for your reply. I don't know much about JPEG marker bytes or hex in general, but surprisingly, the marker type in the error has so far never been the same. I just checked on a dozen files and these are the types that came up: 0x49 / 0x1d / 0x18 / 0x3a / 0xbb / 0x53 / 0x69 / 0x61 / 0x63 / 0x40 / 0x43 / 0x7d / 0x6d In the three files that I posted, the types were 0x20, 0x10 and 0x06 I also tried opening the files with a hex editor, but couldn't get much out of it. Are there any other linux or windows programs I could use to test these files? Any other ideas would also be very welcome. Thanks, Mathieu On Tue, Aug 23, 2016 at 6:30 PM, Tom Lane <tg...@ss...> wrote: > Mathieu Chellat <mch...@gm...> writes: > > The error message I get is "Error interpreting JPEG image file > (Unsupported > > marker type 0x20)". > > Which sounds more like it does not recognize the file as a jpg file. > > No, that sounds more like a corrupted file. 0x20 is not a legal JPEG > marker byte. > > (The fact that you can read it with some other library does not alter the > conclusion that it's not a valid JPEG file. Some code is pretty forgiving > about ignoring garbage; libjpeg is less so.) > > regards, tom lane > |