What on earth happened here?

S

squirrel$$$bandit

Veteran
Local time
3:07 PM
Joined
Mar 8, 2008
Messages
6,249
I took the picture on top--this is on a Panasonic G1. (Not an interesting picture; I was testing a lens.) But this is what came out in the file. 1) There is no green grass here right now. 2) Nobody in my family owns that sweater. 3) I could have sworn I bought this SD card new, and I have certainly formatted it more than once.

4203459903_9c50df16fa_o.jpg
 
What brand memory card? If it is a Sandisk, take advantage of their excellent warranty and replace if for a new one at any store.
If it's not a Sandisk, throw it out and buy a Sandisk!
 
It's a Kingston, which come to think of it means I got it at the college bookstore. Anyway, I'm not worried, I doubt it will ever happen again. I bet Brian Sweeney could tell us how it happened, though.
 
I do not think it is the card. Looks, as if the camera partially read from memory areas (maybe a buffer) it should not read from. (wild guess). I would not worry too much also. In total, interesting picture.
 
gho said:
I do not think it is the card. Looks, as if the camera partially read from memory areas (maybe a buffer) it should not read from. (wild guess). I would not worry too much also. In total, interesting picture.
Click to expand...

But then that other image must have been in that buffer. If he didn't take a picture of that sweater how did it get there? Because the only photo buffer that survives switching off is the memory card.
 
Yeah, I must have taken that lower picture--though I have no idea who that is, and I don't recognize that setting. And perhaps reformatting doesn't wipe the card? It had to be that there was an error at the end of a file, and whatever it is that tells the camera the file is over, wasn't there. And so it kept on reading into the buffer. But again...why would something be stuck in the buffer for so long that I don't even remember the person in the picture? Wouldn't the buffer get overwritten constantly? Furthermore, it's not like this is the most photos I've ever put on the card...the session was only about 25 pictures...so I wouldn't have reached some area of the card that hasn't been touched in a long time. (That's assuming data is written to the card in a linear way, perhaps it's not.)

I am quite certain now that I bought the card new...
 
Last edited:
mabelsound said:
Yeah, I must have taken that lower picture--though I have no idea who that is, and I don't recognize that setting. And perhaps reformatting doesn't wipe the card?

I am quite certain now that I bought the card new...
Click to expand...

Perhaps you should format it in your PC and then again in your camera?
 
As far as I know, data is still recoverable from cards to a certain extend, unless you do a thorough low level format.

There are rescue programs out there, that allow for file recovery in case something was deleted unintentionally. Good keyword for further information on SD Card filesystems are fat16 and fat32, if you are interested.
 
Last edited:
Photo Kiosk Soft Virus

Photo Kiosk Soft Virus

I have seen this a number of times and it is usually caused by a photo kiosk machine that writes or holds some form of soft virus possibly a 100,000 to one chance of it happening again.
 
Wild! When you copy the file to the computer, do you get anykind of "JPEG Marker Error"?

I get stuff like this when a Sector on a Floppy goes bad. It wants to read something.

1) When you took the picture, did it look correct on the LCD Screen?

2) When you look at the image using the camera, does it do the same thing?

3) Does it do the same thing when viewed plugging the SD card into the computer vs connecting the camera via USB?
 
It did look fine on the camera screen, but looked like this when I opened it in Lightroom. It is an RW2 file. Unfortunately I wiped the card before I looked at the photos!
 
Honestly Dave, this can always be traced to Human Error.

Probably the guy that wrote the Lightroom driver...

Some of these packages provide their own temp working files. I know that Photoshop does this, and it gets big. One file for all the images of a session. if photoshop crashes, the file stays on disk. So it could be the software picking up some dead space on the cache file.

I've had software do this before. One package read the file, another screw it up. Is RW2 format compressed, ie huffman code or run-length encoded? Or is it a straight raw-image without use of lossless compression to save space?

I spent a lot of time looking at HEX dumps of image files. Uncompressed raw files are nice and easy to figure out.
 
Dick Cheney is involved in this. I'm not quite sure how, but I know he bears some responsibility for this. He's tapping into your G1. Dispose of the camera immediately, preferably in some public dumpster. Make sure no one is following you. Also, throw away your cell phone. In the future, only use a prepaid cell and be sure to dump it weekly and replace with a new one. I know he is supposed to have left office, but I'm sure there are moles in the NSA or BestBuy. Do not shop Best Buy anymore. Do not talk about grass on RFF. You can't be too careful.

Last week, you started a thread asking if terrorists ever use cameras. What more proof do you than this? Stick to film. Much safer. Process at home. Drink the chemicals after processing to hide the evidence. Make sure you're not being followed.
 
Actually, more useful information- it is probably the driver in the Lightroom software picking up the cache file. The file was stored using Raw Format. Files in Raw format have not undergone color interpolation for the color Mosaic Filter. Raw values for each site are stored. The image shown here has a portion of the image from one-color plane. If the erroneous information at the bottom left had been in the Raw file, the interpolation would have produced a bad full-color image, and not the single-color image fragment as shown. The erroneous data at the bottom right is full-color and went through the interpolation for RGB. A bar of non-image data appears as noise between the two. Again, Lightroom driver picking up bad data.

This would have been much easier if the raw file had been saved and I could use my custom HEX processor written in FORTRAN. It knows how to deal with Raw images.
 
Brian Sweeney said:
This would have been much easier if the raw file had been saved and I could use my custom HEX processor written in FORTRAN. It knows how to deal with Raw images.
Click to expand...

Brian, I do have the original RAW file and will send it to you later, when I turn on my photo computer. Lightroom doesn't touch the original files, so you can hex it to your heart's content! Thanks, this is really interesting.

robklurfield said:
Dick Cheney is involved in this.
Click to expand...

:D
 
Do you mean Dick Cheney writes device drivers in his spare time too!

If this is a result, he should stick to his day job.
 
... serves ya right fer trustin' digital! :p

(Kinda spooky though I must admit!)
 
You must log in or register to reply here.
Back
Top Bottom