Firmware Updates -- Security Code

[Kayaker72]

This seems to be more about protecting your privacy, but the latest firmware updates for a number of Canon cameras include a new password option that will need to be entered each time the camera is turned on or awaken from sleep. If you do not want the password, you can disable it by checking the "do not ask again" box at the time you set up the password.

For more, once again, you can turn to Rudy Winston.

[Kayaker72]

More details on the firmware upgrades. Bryan's News page for the R1 and R5 II.

If you can't get enough of Rudy Winston, he has a new video outlining the key features.

I am probably most intrigued by:

• Setting the number of images taken in pre-capture mode for the R1/R5II. Previously it was 1/2 sec. Now it sounds like you can set the # of images. I do not use precapture much, but I can see using it occasionally.
• "Over the Net AF". A new special case feature that will ignore nets if your subject is on the other side of the net. I can see this being useful.
• Setting focus pre-set distance using Canon App.

Not really impacting any core features for me, but some interesting new features.

[Jonathan Huyer]

I was hoping that the pre-capture mode would be made programmable to a button, so you could turn it on and off quickly. But I guess that didn't happen. Also have you heard if the 'over the net AF' mode also works with wildlife? Not necessarily in a tennis match , but will it help ignore grass and such in front of the animal?

[neuroanatomist]

I usually wait a few weeks to install an update. This update demonstrated why that’s a good idea. For the R1, the update was pulled after a day or two, and a replacement update issued that, “Fixes an issue where the camera failed to operate properly after updating to Firmware Version 1.1.0 if the still photo shooting/movie recording switch function was set to [Silent shutter function switching] or [Disable].” Since I use the photo/video switch to toggle silent shooting, my R1 would have ‘failed to operate properly’ (whatever that means, maybe bricked?) had I applied the 1.1.0 update right when it came out.