Possible corrupted JPEG

angeleyes

While on holidays last week I had some problems with the Sony Cybershot in that when I took a picture I saw it in the LSD screen and then when I went to review them later I had "file error" on the LSD screen.

I downloaded pics onto pc last night and even though they are showing and even the memory they contain - can't open them.

I have been searching online for software all day (and it was my birthday too - fun day lol) but is there anything I can do or should I just delete them and chalk it up to experience.

I have a feeling that the Memory Stick might be for the skip as the camera seems to encounter problems after taking a few minutes of video.

angel

City-Exile

Belated birthday wishes, angeleyes.

Do you format the card after you've removed the pictures?
If so, do you format it in the camera?
How old is the card & how much use does it get?

With regard to the file, there are some programs that can help recover from corruption, but it sounds like the card might have been close to capacity & some images became corrupt.

ThOnda

That sounds bad. Looks like "computer geek" question more than photographic question. Try that way too.
By the way, if you really have LSD display, you wouldn't have any pictures at all

Fajitas!

ThOnda wrote:

By the way, if you really have LSD display, you wouldn't have any pictures at all

You'd have a lot more than pictures tbh.

ThOnda

In fairness, I have never tried LSD. So far. It could make my BW pictures look interestingly colourful ;-)

Vmaxer

angeleyes wrote:

While on holidays last week I had some problems with the Sony Cybershot in that when I took a picture I saw it in the LSD screen and then when I went to review them later I had "file error" on the LSD screen.

I downloaded pics onto pc last night and even though they are showing and even the memory they contain - can't open them.

I have been searching online for software all day (and it was my birthday too - fun day lol) but is there anything I can do or should I just delete them and chalk it up to experience.

I have a feeling that the Memory Stick might be for the skip as the camera seems to encounter problems after taking a few minutes of video.

angel

This just might be of some help to Ya, thats if You haven't formated the stick already..

http://www.sonydigital-link.com/memstick/downloads/downloads_ms.asp?l=en&f=MS_Rescue

angeleyes

Thanks Dubsmax I got this info from Sony Helpline as well and I had formatted the memory stick already which was not too clever - sometimes I do have **** for brains.

Will know the next time and thank you for all your help.

angel

Muineach

what you need is a hard drive recovery program, forget about jpegs etc, treat the memory stick like a hard drive, even if you formatted it was probably a quick format which only wiped away the list of files and where they are, just don't put any new files on it and you may have a chance to recover them.

There are lots of freeware apps out there that can recover files off your hard drive like UndeletePlus, again not 100% on them, but remember if you did a "quick" format you probably just blew away the "table of contents" of the drive, the data should be still there.

I'd say give it one more go :rolleyes:

Sebzy

hey angeleyes by the sounds of it you have partial corruption and using a HDD recovery application wont help a bit in this case.

What you can do is read up about the file level structure of JPEG files and then open up the bad ones using a hex editor and cut out the good portion of the image if there is any.

If this is a bit over your head send the files on or upload them somewhere and I'll see if they can be saved.

jameshayes

this has happened to me on when i first got my camera, as you can see from the attachments!!

I just bought a new MMC, worked a treat!

Sebzy

jameshayes wrote:

this has happened to me on when i first got my camera, as you can see from the attachments!!

I just bought a new MMC, worked a treat!

Hi james if you have an image from the same camera that is complete you can do the following
Open both up in a hex editor find the header information and data block replace the header in the bad image with the one from the good one.

This only works if the data area is still intact you can tell this by looking at the file sizes of a similar picture it should only be one or two KB out.

Sebzy

And for anyone who is interested in doing this themselves here's a quick guide on how the JPEG is built.


================================
Start of Image (SOI) marker -- two bytes (FFD8)

JFIF marker (FFE0)

* length -- two bytes
* identifier -- five bytes: 4A, 46, 49, 46, 00 (the ASCII code equivalent of a zero terminated "JFIF" string)
* version -- two bytes: often 01, 02
o the most significant byte is used for major revisions
o the least significant byte for minor revisions

* units -- one byte: Units for the X and Y densities
o 0 => no units, X and Y specify the pixel aspect ratio
o 1 => X and Y are dots per inch
o 2 => X and Y are dots per cm
* Xdensity -- two bytes
* Ydensity -- two bytes
* Xthumbnail -- one byte: 0 = no thumbnail
* Ythumbnail -- one byte: 0 = no thumbnail
* (RGB)n -- 3n bytes: packed (24-bit) RGB values for the thumbnail pixels, n = Xthumbnail * Ythumbnail

Define Quantization table marker (FFDB)

* the first two bytes, the length, after the marker indicate the number of bytes, including the two length bytes, that this header contains
* until the length is exhausted (loads two quantization tables for baseline JPEG)
o the precision and the quantization table index -- one byte: precision is specified by the higher four bits and index is specified by the lower four bits
+ precision in this case is either 0 or 1 and indicates the precision of the quantized values; 8-bit (baseline) for 0 and up to 16-bit for 1
o the quantization values -- 64 bytes
+ the quantization tables are stored in zigzag format

Define Huffman table marker (FFC4)

* the first two bytes, the length, after the marker indicate the number of bytes, including the two length bytes, that this header contains
* until length is exhausted (usually four Huffman tables)
o index -- one byte: if >15 (i.e. 0x10 or more) then an AC table, otherwise a DC table
o bits -- 16 bytes
o Huffman values -- # of bytes = the sum of the previous 16 bytes

Start of frame marker (FFC0)

* the first two bytes, the length, after the marker indicate the number of bytes, including the two length bytes, that this header contains
* P -- one byte: sample precision in bits (usually 8, for baseline JPEG)
* Y -- two bytes
* X -- two bytes
* Nf -- one byte: the number of components in the image
o 3 for color baseline JPEG images
o 1 for grayscale baseline JPEG images

* Nf times:
o Component ID -- one byte
o H and V sampling factors -- one byte: H is first four bits and V is second four bits
o Quantization table number-- one byte

The H and V sampling factors dictate the final size of the component they are associated with. For instance, the color space defaults to YCbCr and the H and V sampling factors for each component, Y, Cb, and Cr, default to 2, 1, and 1, respectively (2 for both H and V of the Y component, etc.) in the Jpeg-6a library by the Independent Jpeg Group. While this does mean that the Y component will be twice the size of the other two components--giving it a higher resolution, the lower resolution components are quartered in size during compression in order to achieve this difference. Thus, the Cb and Cr components must be quadrupled in size during decompression.

Start of Scan marker (FFDA)

* the first two bytes, the length, after the marker indicate the number of bytes, including the two length bytes, that this header contains
* Number of components, n -- one byte: the number of components in this scan
* n times:
o Component ID -- one byte
o DC and AC table numbers -- one byte: DC # is first four bits and AC # is last four bits
* Ss -- one byte
* Se -- one byte
* Ah and Al -- one byte

Comment marker (FFFE)

* the first two bytes, the length, after the marker indicate the number of bytes, including the two length bytes, that this header contains

* whatever the user wants

End of Image (EOI) marker (FFD9)

* the very last marker
================================