Update: Canon has started to install firmware v.1.0.1 on serviced Canon EOS R5 Mark II camera bodies. This update looks like it addresses an issue with the screen going green when shooting video.
There are still other bugs with the EOS R5 Mark II that will need to be workerd out in short order, and as mentioned yesterday, we expect that to be available before the end of September.
You can see both the issue and the new firmware confirmation below.
We rarely get tipped off about future firmware updates, but it does happen from time to time. It should come as no surprise, but the Canon EOS R5 Mark II will be getting one in the very near future. We do know that the new firmware is currently being tested by numerous friends of Canon.
The new firmware is scheduled to appear before the September 26, 2024 ship date of the RF 28-70mm f/2.8 IS STM. As always with firmware, discovered bugs in testing may delay the release. Which isn't a bad thing, Canon had a lot of firmware that needed to be pulled for both the EOS R6 and EOS R5 because bugs were found, a few of them were pretty significant.
We weren't privy to the firmware release notes, however it's obvious that they'll be cleaning up a lot of the bugs that people have experienced. However, we were told that there will be a “worthwhile feature update or two”. Hopefully any feature updates are more than just video additions. Us photographers always feel somewhat left out of the new feature fun.
Now if only the new firmware update could make LP-E6P batteries appear.
Canon EOS R5 Mark II
- Midwest Photo $4299
- B&H Photo $4299
- Adorama $4299
- Canon USA Store $4299
- Foto Koch €4799
- Foto Erhardt €4799
- Wex Photo £4499
- Camera Canada $5899
When you purchase through links on our site, we may earn an affiliate commission. Here's how it works. |
Better still, have the LP-E6NH do pre-capture.
I agree with IBIS high Res being a gimmick. In three months with the R5 I haven't even tested it yet.
I think this is one of the features that get better over time. I do find it a better implementation than the pixel-shift. We'll see how it progresses though.
I have set the drive mode to H in 15fps per Default and set the dof Preview Button to engage the H+ for 30fps as long as it's held down.
I code as a day job. It'd 100% make sense that they had a 'wish list' of stretch goal features, and disabled any that weren't ready at launch. These are unlikely to be 'new' features but rather work that wasn't complete and tested earlier. After launch, they'd be finishing these up and addressing bug reports as they come in.