Upvote
0
Canon EOS R5 Mark II Firmware v1.1.0 Now Available (Update: Firmware has been pulled)
- Thread starter Canon Rumors
- Start date
As someone who has worked for many years in the software and hardware industry the comments in the article such as “screwed up again” are IMHO a bit unwarranted. Firmware in this case is a very complex beast. It gets doubly hard when we also consider that this may not even be with all models of memory card. It is actually a lot more complex than many may realise. Even the likes of Apple, who have a very specific hardware set all made in house, have had to very quickly pull updates or urgently push new versions. It happens to almost every brand, even those who are software only.
What is more important is how well a company goes on to deal with said issues. Pulling very quickly seems to be a good way to go. Instead of letting it go until another update is released. Some companies just bury their heads in the sand, or pass the buck to third parties. Mistakes happen no matter how hard or how much work goes into testing. I know, I have done it myself.
What is more important is how well a company goes on to deal with said issues. Pulling very quickly seems to be a good way to go. Instead of letting it go until another update is released. Some companies just bury their heads in the sand, or pass the buck to third parties. Mistakes happen no matter how hard or how much work goes into testing. I know, I have done it myself.
Upvote
0
Even though I can certainly agree with you, I still don't understand Canon's lack of reaction.
The AF issues are real, and started with firmware 1.0.3. Before, AF worked well.
So, instead of leaving us uninformed, and releasing a new firmware which doesn't solve the AF and battery problems, they could have facilitated the downgrading back to 1.0.2. At least, those who need their camera could again get their subjects in focus. Will new customers buy an expensive camera hoping for a fix of known issues someday???
Silence is the worst you can opt for in such a case, letting rumors develop and doubts about Canon's reliability install. Ask the auto industry, they paid a high price.
The AF issues are real, and started with firmware 1.0.3. Before, AF worked well.
So, instead of leaving us uninformed, and releasing a new firmware which doesn't solve the AF and battery problems, they could have facilitated the downgrading back to 1.0.2. At least, those who need their camera could again get their subjects in focus. Will new customers buy an expensive camera hoping for a fix of known issues someday???
Silence is the worst you can opt for in such a case, letting rumors develop and doubts about Canon's reliability install. Ask the auto industry, they paid a high price.
Upvote
0
Upvote
0
Could you please give a one sentence summary of the take home message - it will save loads of us having to watch yet another YouTube.
Upvote
0
Duade speaks from previous personal experience with AF. He says that he does not noctice a difference with the AF in this firmware update v1.1.0. He explains various situations and is giving some tips how he deals with specific circumstances.
Upvote
0
If my camera was working fine (and it is) I would leave it alone. Unless there is something there you really have to have, I'd save it for after the trip.
Upvote
0
Upvote
0
Sorry, I was only answering AlanF's question about Duade Paton's video! I should have written "what I saw in the video".
I wasn't relating my experience (my R5 IIs are still on 1.0.2 and 1.0.3)
Upvote
0
I think that one is more complex. So many have been unable to replicate the problem. So it could be specific hardware/software combinations that cause the problem. Add in the usual people who read there is a problem so then have something to blame for their own errors and the water becomes quite muddy, It becomes even harder when all internal audits under change control point to nothing being changed that could affect AF. But then with all complex software it can be something totally in theory unconnected that leads to an issue.
The problem Canon, and all camera manufacturers have compared to connected devices such as phones, is that there is no live and directed feedback. On connected devices there are logs, crash dumps etc that can lead to a speedy resolution, With cameras there is no such thing at present, so it often comes down to to a combination of close code examination coupled with attempts to replicate an issue. With rapid development as we are seeing now with the move to ML, coupled with an ever increasing list of third party accessories I can see us having an increase in the amount of bugs we see as time moves on. Not just from Canon, but all brands. It is getting much harder for working togs to trust firmware updates and this will only get worse. Add in seemingly deliberate blocking of third party kit such as Nikon did recently with some third party batteries and I think many working togs will only update if they really need to. It made me cringe reading of companies updating all their cameras last week while the firmware was available and then being seemingly proud they did so. I sincerely hope it doesn’t affect their businesses. It is fine for a hobbyist like me, but for those with business critical kit it is a different matter. I would wait a few months if that was my business, unless I needed a fix for an ongoing issue. Even then I would never chuck all my eggs in the same basket.
Upvote
0
D
Deleted member 392350
Guest
I mean yes but also no. Just imagine if this was a hardware issue, Canon would be all over it and would probably have it fixed by now. And in this particular case, not all people are imagining it.
To be clear I'm saying you are right, but also that this line of argumentation just can't be a valid cop-out for Canon in 2025 anymore. They're selling a camera and the firmware is a huge huge part of it. It's the main differentiator nowadays and AF is the most important part of the product. Better get their s..tuff together and fix it, or I won't be buying Canon in the future
I already didn't get the Mk II because I wanted to see if there were any showstopper bugs.
My R5 Mk I still locks up occasionally, and while they tried to address that issue in several updates it's not fixed and Canon gave up. Bad AF is arguably worse, because you only notice after the fact and all your pictures are ruined.
Just imagine this issue was present at release. The R5 II would've been torn to shreds by reviewers, and rightfully would have been a flop. So why would it be acceptable now to have bad AF?
And put another way, how come the R1 is not affected? Clearly they have been doing something to prevent the issue from occurring on their flagship, so it doesn't seem impossible.
Upvote
0
Think is, as an owner of the R5II I have been completely unable to replicate these issues. Many others are in the same boat and cannot do so. In face from my perspective the AF is astonishingly good. Yes, it is not perfect, but no camera is. There will be times as per the recent Duade Paton video where the camera does something our own eyes would not. But millions of years of evolution outweigh a few years of technical development.
As for lock ups, that is something that we n the next few generations I can only see as getting worse as the software and hardware becomes more complex, as components are pushed further and faster. I get the impression that currently certain parts of all systems are being pushed hard. At this point even small bit errors can cause crashes. We are moving and manipulating a huge amount of data extremely quickly in a small and low powered space. That is something very challenging and it is bound to error, usually at the most inconvenient moment.
Upvote
0
What should also not be forgotten, is that Canon are no small electronics or software development company, but a giant in that world. With myriads of specialists. And also that they-unintentionally- "sabotaged" their own camera with a corrupted software. I am simply not ready to swallow a lack of reaction, be it a credible explanation, or a fix. This passivity is not acceptable!
Upvote
0
They've been having problems with the Firmware updates on and off for a while. I don't expect it to change because it's like a race with the other companies to provide the most and/or best and be fastest. I don't think it's going to change.
Upvote
0
How many menu settings combinations are there? Multiply that by how many hardware combinations of lenses, flashes, memory cards and wireless connectivity there are and you start to see the complexity of the situation. When you write code it is so easy to miss a trailing space or something similar in a price of code that seems innocuous. Then you have a limited period to test all those setup combinations and it soon becomes very clear the challenge is immense. I am not trying to stick up for Canon here, but software development in general. We all expect perfection but I cannot think of any company that can deliver that in any complex bit of kit, doubly so when you add in third party elements such as memory cards and environmental interference etc.
Upvote
0
I was very happy to see the firmware re-released for my R5 Mark II and I have updated both my camera and my partners identical camera body. Right now she is taking bird pictures outside. I will get to do quite extensive shooting (wildlife) from this coming Sunday onwards with the camera. We did not notice any negative difference in our R5 Mark II autofocus between the earlier firmwares as some folk have.
I already got rid of the password requirement on start up as it is not anything I have need of.
I already got rid of the password requirement on start up as it is not anything I have need of.
Upvote
0
Seems to be working on mine. Can you detail your settings, lens etc? I would like to see if I can get mine to do it.
Upvote
0
Similar threads
