Three firmware updates waiting

[Alastair Norcross]

I got my email from Canon today about the R5II firmware. They emailed me last week about the R7 and R6II. I haven't installed any yet, as I'm still waiting, in case we get any reports of problems. The main thing I want in the R5II firmware is the ability to adjust the number of frames in pre-shooting. Anyone have any feedback on how well these updates are going for them, especially the R5II 1.1.1? I'm still on 1.02 on my R5II, because of some reports of problems with 1.03.

 

[Andy01]

Is there any driver to update any of the older models (like R6 ii, R8, R10 etc) if you don't want the PIN number feature ?

 

[Interpol]

Updated the firmware on my R3, R7 and R5 II all at the same time. No problems encountered.

 

[PicPocket]

Is there any driver to update any of the older models (like R6 ii, R8, R10 etc) if you don't want the PIN number feature ?

The included bug fixes are always a driver for me. If they have been fixed, they are confirmed to exist, so I don't want one of them to suddenly show up one day in the field when I least expect it. It's not important that I have so far not seen them, there is always a first when I may try to do something different

As for password, can be disabled, so not an issue

 

[SigZero]

I got my email from Canon today about the R5II firmware. They emailed me last week about the R7 and R6II. I haven't installed any yet, as I'm still waiting, in case we get any reports of problems. The main thing I want in the R5II firmware is the ability to adjust the number of frames in pre-shooting. Anyone have any feedback on how well these updates are going for them, especially the R5II 1.1.1? I'm still on 1.02 on my R5II, because of some reports of problems with 1.03.

Updated my R5mk2 on the day of 1.1.1 release. No problems so far.

Br, Pawel

 

[Giklab]

I have to admit I was excited when I read about the pre-burst fps setting... Until I realised it only adjusts down, not up.

 

[Alastair Norcross]

I have to admit I was excited when I read about the pre-burst fps setting... Until I realised it only adjusts down, not up.

Down is what I want. 15 is more than I need. I’m usually shooting action at 10 or 15fps, never higher. 1.5 seconds is far more than I need. 1/2 second is plenty (it doesn’t take that long to react). I’m looking forward to setting my pre-burst to 5 frames. I think I’ll use it a lot more now.

 

[Giklab]

I have to admit I was excited when I read about the pre-burst fps setting... Until I realised it only adjusts down, not up.

Down is what I want. 15 is more than I need. I’m usually shooting action at 10 or 15fps, never higher. 1.5 seconds is far more than I need. 1/2 second is plenty (it doesn’t take that long to react). I’m looking forward to setting my pre-burst to 5 frames. I think I’ll use it a lot more now.

Understandable. I'm a bit slow to react and would prefer a full second at 20fps.

--
“When I die, I want to go peacefully in my sleep like my grandfather. Not screaming in terror, like the passengers in his car.” Jack Handey
Alastair
http://anorcross.smugmug.com
Equipment in profile

 

[PicPocket]

I have to admit I was excited when I read about the pre-burst fps setting... Until I realised it only adjusts down, not up.

Down is what I want. 15 is more than I need. I’m usually shooting action at 10 or 15fps, never higher. 1.5 seconds is far more than I need. 1/2 second is plenty (it doesn’t take that long to react). I’m looking forward to setting my pre-burst to 5 frames. I think I’ll use it a lot more now.

Understandable. I'm a bit slow to react and would prefer a full second at 20fps.

If the camera came out with a fixed 15 images in that cyclic buffer for precapture, that just happens to be 0.5 sec at 30fps. Clearly, a firmware update is not adding any physical buffer, so getting more than 15 frames to cycle would would have to borrow from someplace else and I am not sure they would have left such a margin around and not used it on launch unless they found something suboptimal on original firmware to exploit

Lowering down is quite feasible though, and is just a feature implementation

If it's about reaction time, 15fps would have given 1sec even on original firmware, and 15 frames even at 20fps if that is a choice. This firmware allows to avoid 15 if people don't want those many images every time they shoot

--
PicPocket

 

[Charlie Phillips]

No problems here so far Alastair - still practising with the pre-shoot function, being able to adjust it now is so good.

 

[CameraCarl]

Jan Wegener, an excellent bird photographer and long time Canon user, updated his 5D Mark II and had good results. He had hesitated initially because of the "recall" of the firmware, but initially decided to update one of his bodies and use it for a while before reporting about it. Now I believe he went ahead and updated the second one. You should be able to find his YouTube discussion about this.

 

[Alastair Norcross]

Thanks for the feedback everyone. I've updated my R5II, and everything seems fine so far.

 

[RLight]

Thanks for the feedback everyone. I've updated my R5II, and everything seems fine so far.

 

[Alastair Norcross]

Thanks for the feedback everyone. I've updated my R5II, and everything seems fine so far.

Tag. Watching this thread…

Hows autofocus? 1.0.3 regressed AF accuracy. Curious if they resolved.

I never installed 1.0.3. I haven’t done enough shooting yet to tell whether there’s any difference from 1.0.2 in that regard.

 

[R2D2]

Thanks for the feedback everyone. I've updated my R5II, and everything seems fine so far.

Tag. Watching this thread…

Hows autofocus? 1.0.3 regressed AF accuracy. Curious if they resolved.

I never installed 1.0.3. I haven’t done enough shooting yet to tell whether there’s any difference from 1.0.2 in that regard.

When I first installed v1.0.3 I noticed AF issues. So the first thing I did was reinstall 1.0.3 over itself and now the AF is back to being awesome (I shot an airshow last week and was absolutely flabbergasted).

R2

 

[Alastair Norcross]

Thanks for the feedback everyone. I've updated my R5II, and everything seems fine so far.

Tag. Watching this thread…

Hows autofocus? 1.0.3 regressed AF accuracy. Curious if they resolved.

I never installed 1.0.3. I haven’t done enough shooting yet to tell whether there’s any difference from 1.0.2 in that regard.

When I first installed v1.0.3 I noticed AF issues. So the first thing I did was reinstall 1.0.3 over itself and now the AF is back to being awesome (I shot an airshow last week and was absolutely flabbergasted).

R2

Wait a minute. You reinstalled 1.0.3 over itself? Not 1.0.2 over 1.0.3? So your R5II went from having 1.0.3 to 1.0.3 (?!). And that changed things? How would that work? Any idea?

 

[R2D2]

Thanks for the feedback everyone. I've updated my R5II, and everything seems fine so far.

Tag. Watching this thread…

Hows autofocus? 1.0.3 regressed AF accuracy. Curious if they resolved.

I never installed 1.0.3. I haven’t done enough shooting yet to tell whether there’s any difference from 1.0.2 in that regard.

When I first installed v1.0.3 I noticed AF issues. So the first thing I did was reinstall 1.0.3 over itself and now the AF is back to being awesome (I shot an airshow last week and was absolutely flabbergasted).

R2

Wait a minute. You reinstalled 1.0.3 over itself? Not 1.0.2 over 1.0.3? So your R5II went from having 1.0.3 to 1.0.3 (?!). And that changed things? How would that work? Any idea?

Indeed. There have always been reports of firmware updates just not "taking" well (causing irregularities for some users). I've experienced it myself a couple of times. This time instead of rolling it back a notch, I just reinstalled it over itself to see if that would clear things up. Fortunately it did!

I can't be 100% sure of the cause and effect, because at the same time of the reinstall, I also lengthened the "sleep" timers (as suggested by some folks online). But after shooting some 30,000 pics since then, I've been absolutely gobsmacked by the R5ii's performance. I'd recommend anyone who has had issues after an update do the same, at least for starters.

R2

--
Good judgment comes from experience.
Experience comes from bad judgment.
http://www.pbase.com/jekyll_and_hyde/galleries

 

[jjbinx]

Thanks for the feedback everyone. I've updated my R5II, and everything seems fine so far.

Tag. Watching this thread…

Hows autofocus? 1.0.3 regressed AF accuracy. Curious if they resolved.

I never installed 1.0.3. I haven’t done enough shooting yet to tell whether there’s any difference from 1.0.2 in that regard.

When I first installed v1.0.3 I noticed AF issues. So the first thing I did was reinstall 1.0.3 over itself and now the AF is back to being awesome (I shot an airshow last week and was absolutely flabbergasted).

R2

Wait a minute. You reinstalled 1.0.3 over itself? Not 1.0.2 over 1.0.3? So your R5II went from having 1.0.3 to 1.0.3 (?!). And that changed things? How would that work? Any idea?

Indeed. There have always been reports of firmware updates just not "taking" well (causing irregularities for some users). I've experienced it myself a couple of times. This time

instead of rolling it back a notch,

I was told in another thread that Canon camera update process doesn’t allow an earlier version to be installed - ??

jj

I just reinstalled it over itself to see if that would clear things up. Fortunately it did!

I can't be 100% sure of the cause and effect, because at the same time of the reinstall, I also lengthened the "sleep" timers (as suggested by some folks online). But after shooting some 30,000 pics since then, I've been absolutely gobsmacked by the R5ii's performance. I'd recommend anyone who has had issues after an update do the same, at least for starters.

R2

 

[R2D2]

Thanks for the feedback everyone. I've updated my R5II, and everything seems fine so far.

Tag. Watching this thread…

Hows autofocus? 1.0.3 regressed AF accuracy. Curious if they resolved.

I never installed 1.0.3. I haven’t done enough shooting yet to tell whether there’s any difference from 1.0.2 in that regard.

When I first installed v1.0.3 I noticed AF issues. So the first thing I did was reinstall 1.0.3 over itself and now the AF is back to being awesome (I shot an airshow last week and was absolutely flabbergasted).

R2

Wait a minute. You reinstalled 1.0.3 over itself? Not 1.0.2 over 1.0.3? So your R5II went from having 1.0.3 to 1.0.3 (?!). And that changed things? How would that work? Any idea?

Indeed. There have always been reports of firmware updates just not "taking" well (causing irregularities for some users). I've experienced it myself a couple of times. This time

instead of rolling it back a notch,

I was told in another thread that Canon camera update process doesn’t allow an earlier version to be installed - ??

jj

There's a specific (wildcat) procedure to follow that was outlined in a previous thread a couple of years ago. I rolled back the firmware on my R5 once after a bad update was released (Canon released a good update soon after).

I haven't tried it with my R5ii though, since the reinstall did the trick this time.

R2

I just reinstalled it over itself to see if that would clear things up. Fortunately it did!

I can't be 100% sure of the cause and effect, because at the same time of the reinstall, I also lengthened the "sleep" timers (as suggested by some folks online). But after shooting some 30,000 pics since then, I've been absolutely gobsmacked by the R5ii's performance. I'd recommend anyone who has had issues after an update do the same, at least for starters.

R2

 

[RLight]

Thanks for the feedback everyone. I've updated my R5II, and everything seems fine so far.

Tag. Watching this thread…

Hows autofocus? 1.0.3 regressed AF accuracy. Curious if they resolved.

I never installed 1.0.3. I haven’t done enough shooting yet to tell whether there’s any difference from 1.0.2 in that regard.

When I first installed v1.0.3 I noticed AF issues. So the first thing I did was reinstall 1.0.3 over itself and now the AF is back to being awesome (I shot an airshow last week and was absolutely flabbergasted).

R2

Wait a minute. You reinstalled 1.0.3 over itself? Not 1.0.2 over 1.0.3? So your R5II went from having 1.0.3 to 1.0.3 (?!). And that changed things? How would that work? Any idea?

Indeed. There have always been reports of firmware updates just not "taking" well (causing irregularities for some users). I've experienced it myself a couple of times. This time instead of rolling it back a notch, I just reinstalled it over itself to see if that would clear things up. Fortunately it did!

I can't be 100% sure of the cause and effect, because at the same time of the reinstall, I also lengthened the "sleep" timers (as suggested by some folks online). But after shooting some 30,000 pics since then, I've been absolutely gobsmacked by the R5ii's performance. I'd recommend anyone who has had issues after an update do the same, at least for starters.

R2

What you're saying is in fact possible; when initializing new firmware, it may "move the cheese" so to speak in terms of configuration to setting mappings where either restoring settings to default after and upgrade, or sometimes just re-applying the upgrade, resolves. Usually the latter only resolves because part of the upgrade process itself when there is a change of configuration to setting mapping is porting the old configuration, which re-applying the upgrade can re-port it if there was a RACE condition, or otherwise reset services that were hung or otherwise had file locks preventing upgrade. Most of the time resetting defaults after an upgrade that produces odd effects is wise and re-applying upgrades isn't commonplace in this decade to resolve bugs as folks generally vet their upgrade workflow to ensure this sort of thing doesn't happen.

That said, there's nothing new under the sun... Ask CrowdStrike, clearly they didn't dev-test their upgrade last year prior to rollout. Software regressions and lack of proper testing are both the work of cutting corners be it either budget with lack of process handoff or single point of failure, and pushing the boundaries of release scheduling.

A lot of lengthy words, but funny thing is, after writing it? I realize Canon themselves has some significant software development problems as they had to re-release the R1 and R5 II firmware. Maybe you're not crazy re-applying that upgrade... History is a good predictor of the future, and in this case, the present/future is a good indicator of the past.

Maybe I'll wait a little longer on 1.1.1...