Re: Corrupt JPG Files
- From: "Martin Brown" <|||newspam|||@nezumi.demon.co.uk>
- Date: 12 Apr 2007 01:10:38 -0700
On Apr 11, 9:52 pm, "Mark" <n...@xxxxxxxxxxxxxxxxxx> wrote:
On 11 Apr, 21:05, ASAAR <cau...@xxxxxx> wrote:
On Wed, 11 Apr 2007 15:34:10 -0400, jimbok wrote:
Simply put, windows, upon seeing a .jpg extension, reads the file's
header. If is is - in any way incorrect - windows will reject it as a
jpg file and treat it as "unknown file type."
And Photoshop in particular will choke on a JPEG with even the tiniest
defect.
That may be true for windows, but I'd be surprised if all
applications are similarly fooled. Many times I've tried to view
image files (jpg, gif, etc.) using Irfanview and will see a message
stating that the file extension is incorrect and with an offer to
correctly rename the file. Whether I did or didn't allow renaming,
Irfanview then was always able to display the images.
That will work if the program understands file headers and the file
has a wrong extention. The problem here is that the file extention is
correct but the file header and very possibly the file contents have
been corrupted somehow.
Yes, but as per my OP, I tried irfanview as one the first progs. The
actual error it gives for all 9 images is "Huffman table 0x01 was not
defined".
OK that is *very* important information. No normal application will be
able to display such a file. It is missing the crucial table to tell
it how to do the initial decompress of the JPEG components. What you
have is a random sequence of compressed bits with no information about
how to interpret it! There may be a fairly simple fix, but I would
need to see a couple of sample files to determine if the fault is
easily repairable (ie if the damage is only to the header).
BTW, I tried "jpeg recovery" and that told me the file header was
corrupt.
And it is correct. It requires JPEG wizard tricks to read a damaged
file. I am happy to examine a couple of sample files to determine the
nature of this fault. I have never seen a fault that breaks the
Huffman tables before and I am curious to see exactly what has
happened to it. Usually most errors are in the bulk data after start
of stream.
My instinct given the large number of identical faults you have seen
is that the camera firmware is suspect.
A typical failure rate is more like 1:10000 shots (most digicams can
sometimes glitch in a way that generates a broken JPEG file if
suitably provoked). The main way to corrupt files is by ejecting media
with the power still on and read/write in progress. Press
photographers tend to do this in the heat of the moment when a card
fills and they need to replace it quickly. Windows XP can be unkind to
removable media that is ejected unexpectedly too.
I'll review the file header comparison thing. It's going to take a
long time as at first glance, the bytes that differ are different on
all images including those that load fine. I'll need to look closer.
Re calling HP - yes, I might give it a go but I'm not encouraged that
it is now listed as an obsolete camera. Also, last time I contacted
them about the compression settings, they didn't seem to know that the
compression level could even be changed!- Hide quoted text -
That sounds about right for HP support :(
Regards,
Martin Brown
.
- Follow-Ups:
- Re: Corrupt JPG Files
- From: Mark
- Re: Corrupt JPG Files
- References:
- Corrupt JPG Files
- From: Mark
- Re: Corrupt JPG Files
- From: Martin Brown
- Re: Corrupt JPG Files
- From: Mark
- Re: Corrupt JPG Files
- From: jimbok
- Re: Corrupt JPG Files
- From: ASAAR
- Re: Corrupt JPG Files
- From: Mark
- Corrupt JPG Files
- Prev by Date: Re: raw files are HUGE
- Next by Date: Only 11mm LED slim light box in China!
- Previous by thread: Re: Corrupt JPG Files
- Next by thread: Re: Corrupt JPG Files
- Index(es):
Relevant Pages
|