7D Ghost Images

L_F_L wrote in post #8904137
It's official in the US too:

http://www.usa.canon.c​om …356&keycode=211​2&id=60427

Curious that Canon states that the issue will be addressed by a firmware update. Have they been aware of this problem for some time and already determined that it is not hardware related? To a non-engineer such as myself, it certainly appears more like an image latency issue than a software issue. Of course, if the problem is tied to the speed with which the sensor can be fully cleared of a prior image, the firmware "fix" might involve throttling back the maximum available frame rate based on selected shooting parameters. I'm sure Canon doesn't even want to think about a recall. Let's hope the ghosts really can be exorcised through a firmware update.

It will be interesting to see how this story evolves.

Dave F.

heh

Throttle back the FPS

7D Service Note from Canon - "Residual Image in Picture" - Firmware update imminent

http://www.usa.canon.c​om …356&keycode=211​2&id=60427

FYI all ...

Cheers

David

PS. Never had this problem myself, but they've obviously admitted it's a possible problem.

Good to see them acknowledge the problem and jump on it quickly. Granted the camera never should have had the issue in the first place but their quick action is commendable.

https://photography-on-the.net/forum/showthre​ad.php?t=771433

tetrode wrote in post #8904256
Curious that Canon states that the issue will be addressed by a firmware update. Have they been aware of this problem for some time and already determined that it is not hardware related? To a non-engineer such as myself, it certainly appears more like an image latency issue than a software issue. Of course, if the problem is tied to the speed with which the sensor can be fully cleared of a prior image, the firmware "fix" might involve throttling back the maximum available frame rate based on selected shooting parameters. I'm sure Canon doesn't even want to think about a recall. Let's hope the ghosts really can be exorcised through a firmware update.

It will be interesting to see how this story evolves.

Dave F.

I was thinking the same think.
I "must" believe it's something a firmware can fix.

Getting the word out there that they know about it is important. I know it's a toss-up between keeping mum so the camera doesn't have bad word of mouth (and having people hold off on getting it, thus affecting impressions), but I like the approach of acknowledging the problem and proposing a fix.

Let's believe it's just about a firmware update.
I really want to believe on that.

Just cancelled my BH order. I am too far away for a return/recall if needed.

Let's wait to see if it's just about a firmware fix, if ok, I'll get one near future.


Sorry guys, but it's a shame.

It most likely is in the algorithm that takes the sensor readings and creates the raw data from that reading. In a burst mode, it may be possible that memory buffers are not initialized and data is XOR'd with the preceding data in that buffer, and you get residual ghost data left over in memory. Not sure, but this is a guess. I definitely don't see this as a hardware/sensor issue and is rather a memory mapping exercise.

Canon always has problems like this with new cameras. Remember 5DII and "black dots" phenomena? 50D and magenta colors? It will be good if it is fixable via firmware update. But could be more serious issue, like AF in 1DIII.... Hopefully, this is not the issue this time.

TeamSpeed wrote in post #8904616
It most likely is in the algorithm that takes the sensor readings and creates the raw data from that reading. In a burst mode, it may be possible that memory buffers are not initialized and data is XOR'd with the preceding data in that buffer, and you get residual ghost data left over in memory. Not sure, but this is a guess. I definitely don't see this as a hardware/sensor issue and is rather a memory mapping exercise.

They should have used Java....No memory management needed for the user (unlike that nasty language called C :lol

Don't you people understand what is happening here? The 7D is a time machine! imagine what the future holds! we may one day be able to take pictures of Jesus...

sounds like the "bucket brigade" isnt fully dumping the electrons from the pixels
or the empty register isnt doing its job well enough...
ahhh cmos technology, wish i could get a job doing this stuff, im just not a EE guy lol

I've still only seen once example of this occurring in a shot on the web. It was a picture of an eagle and if you looked you could make out the ghosting on the underside of the wing IIRC. And that's with a month of the camera being out and everyone on DPR trying to beat the camera to death.

egordon99 wrote in post #8904243
Kudos to Canon for coming out and admitting they have a problem.

This to me is the really good news.
Hopefully the attitude I perceived of arrogance, not listening and not
admitting things could be improved is gone.
Sounds like they see they have an issue and are letting us know they are working on it.
A change.