mackguyver said:This is a tiny incremental update - there's no indication that Canon won't give the 5DIII updates the same or similar features once the 1DX update is out.Scott_McPhee said:Look at the recent 1DX firmware update and compare it with what the 5D3 has got so far.
No comparison.
I think most of us do... The forum is just that, it's a forum, a place to talk shop, offer opinions, advice, etc.Harv said:It never ceases to amaze me how many people are never satisfied with what Canon does. If the 5D3 falls short of their expectations, why buy it in the first place?
For crying out loud, the 5D3 is half the price of the 1Dx. If someone wants the 1Dx features, they should reach into their pocket and pony up the funds to buy the 1Dx. It's that simple.
I elected to add the 5D3 to my bag as a second body to my 1D4. I knew what the specifications were when I made the decision to buy it. It performs as advertized. Firmware updates to deal with bugs that show up are appreciated and I'm thankful that the manufacturer offers them up. I don't expect Canon to turn my 5D3 into a 1Dx.
Anyone who purchased a 5D3 knew full well what it's features and limitations were when they made the decision and laid their money down.
If you own the 5D3, which is a great camera, just pick it up and go take some photos.
+1 on this, too, but I'm guessing there is a hardware limitation that prevented them from including it in the next-to-last firmware update.Krob78 said:I'd still like a RED focus point in AI Servo! :![]()
neuroanatomist said:Oh wait, it did. But the 1DX was neglected and did not get uncompressed HDMI output.
arbitrage said:5D3 still has a good chance of getting the 1DX stuff.
Marsu42 said:...so what's the reason for Canon to further enhance the 5d3 (or 6d) right now?
Harv said:It never ceases to amaze me how many people are never satisfied with what Canon does. If the 5D3 falls short of their expectations, why buy it in the first place?
Could be but it sure seems like something a FW update could alter... I'd like the center red focus in all cases pretty much, not just AI Servo. It's just that I shoot there so much!mackguyver said:+1 on this, too, but I'm guessing there is a hardware limitation that prevented them from including it in the next-to-last firmware update.Krob78 said:I'd still like a RED focus point in AI Servo! :![]()
Krob78 said:Could be but it sure seems like something a FW update could alter... I'd like the center red focus in all cases pretty much, not just AI Servo. It's just that I shoot there so much!mackguyver said:+1 on this, too, but I'm guessing there is a hardware limitation that prevented them from including it in the next-to-last firmware update.Krob78 said:I'd still like a RED focus point in AI Servo! :![]()
+1 and thanks for the explanation and view! Definitely helps me understand that better.neuroanatomist said:Krob78 said:Could be but it sure seems like something a FW update could alter... I'd like the center red focus in all cases pretty much, not just AI Servo. It's just that I shoot there so much!mackguyver said:+1 on this, too, but I'm guessing there is a hardware limitation that prevented them from including it in the next-to-last firmware update.Krob78 said:I'd still like a RED focus point in AI Servo! :![]()
There might be a technical limitation. People who used previous 1-series bodies are used to red AF points. Like other cameras that don't have the transmissive LCD, the AF points are etched into the focus screen, and that makes them easy to illuminate from an angle which avoids significant wide-field reflection. On cameras with a transmissive LCD, there are no etched grooves to 'side-light', but rather the flat surface of the LCD has to be illuminated, and that's a lot less specific. The red light from the illuminator reflects off the surface of the transmissive LCD, and some of it reaches the metering sensor. You can see that here:
![]()
That's not a problem for still shooting, but for servo shooting, the near-continuous metering would be impacted by the illumination for the LCD. The solution for the 1D X is intermittent (blinking) illumination of the AF points in servo mode, and although that sounds like it could be implemented on the 5DIII, it's possible that they tweaked the interpretation from the metering sensor to ignore that red light, which might be possible with the RGB metering sensor of the 1D X but not possible with the less distinguishing metering sensor of the 5DIII.
Lots of 'mights' there, and I suppose it's equally likely that Canon simply decided not to add that feature to the 5DIII, just as they decided not to add clean HDMI out to the 1D X.
Couldn't help but laugh out loud! Thanks again! ;DLots of 'mights' there, and I suppose it's equally likely that Canon simply decided not to add that feature to the 5DIII, just as they decided not to add clean HDMI out to the 1D X.
mWaltari said:For me the worst part of MkIII firmware is that HRD does not produce RAW/TIFF images like it should. Fact that it produces jpeg makes it just automatic bracketing tool
I really do not understand what they where thinking of???
In many situations it would make the Workflow so much faster and easier when you could use HDR results from straight from the camera. And if want to you could still use individual files if camera did not produce what you where looking for...
-Tee-
Etienne said:I assume you mean HDR ... You can set it to save all images. When I do HDR I get the processed HDR in camera plus all of the RAW images.
That wretched Canon... How is it, not to include the 1Dx in these feature sets? I've noticed that they left your hallowed 1Dx without a built in flash too, as even the Rebel series have them... Not very sporting of them at all... I feel your pain, no built in flash or articulating LCD screen on the lowly 5D MkIII either!neuroanatomist said:Etienne said:I assume you mean HDR ... You can set it to save all images. When I do HDR I get the processed HDR in camera plus all of the RAW images.
Yeah, in-camera HDR. Another feature found on the 5DIII (and other models, including my lowly PowerShot S100), but not found on the 1D X.![]()