Quick take: Canon's R5 C firmware 1.0.4.1 had a bug that enabled pixel shift on a camera without IBIS, with no way to turn it off. Canon pulled it, and firmware 1.0.5.1 fixes it. I've run it on both of my R5 Cs without issues. Here's how to install it, plus why I still think Canon needs to communicate better.
What Went Wrong
Two weeks earlier, Canon released firmware 1.0.4.1 for the R5 C. It had a bug that essentially enabled pixel shift, a feature this camera doesn't have since it has no IBIS. There was no way to turn it off, and I, along with other owners, worried it could damage the camera. About a week later, Canon pulled the firmware after multiple reports, and then released 1.0.5.1, which solves the problem. I've been shooting on it for a couple of days with no bugs.
How to Install Firmware 1.0.5.1
Format an SD card. It won't work from the CFexpress card.
Download the firmware for the R5 C from Canon's support site for your operating system and unzip it.
Copy the update file to the root of the SD card, not into any folder.
Make sure your battery is fully charged, or keep the camera plugged in.
Insert the card, turn the camera on, open the menu, go to Setup, and on the last (ninth) screen choose Firmware, then Camera, and confirm the update to 1.0.5.1.
Wait about 10 minutes for it to finish.
The update resets all your settings, so you'll need to re-enter them or sync them with the app. Canon says not to save settings on the old firmware and load them after updating, so I followed that advice.
The best part of the update is still the much shorter delay when switching between photo and video modes. Anyone who bought this camera recently is lucky they never dealt with the old delay of nearly 10 seconds.
A Hardware Difference?
Oddly, only one of my two R5 Cs showed the bug after the bad update. I bought them a few months apart, and my theory is there was a hardware change, maybe due to the supply chain shortages. The newer one also updated faster, possibly because of the battery grip.
Why This Matters
One commenter said they'll wait before updating firmware in the future, and that's the right mindset. You usually shouldn't update right away. I jumped in because I was excited about the new features.
The number one reason to buy professional equipment isn't codecs or features. It's reliability. The C line is Canon's professional line, and you can't have issues on a shoot day. Every manufacturer ships buggy firmware sometimes, including Fujifilm, but Fujifilm tends to pull bad firmware quickly and communicate openly. Canon's usual stance is not to comment, and that isn't helpful when you've invested a lot of money in the system. I stuck to manual settings and kept a Fuji camera with me as backup, but I wanted Canon to confirm whether some button combination could accidentally trigger it.
Some people said I was making a big deal out of it, or doing a hit job on Canon. Brand loyalty is a weird thing when you're the one paying the company. I invested in this system because it's good, but that doesn't mean companies should get a pass when they mess up and don't communicate.
Features I'd Like to See
C-Log2. Canon says the sensor doesn't have the dynamic range for it, but Cinema RAW Light with a denoiser grades much like C-Log2. It's just not available in a compressed codec.
Full 8K60 access with a dummy battery. Right now you need USB-C PD power to unlock everything. I've rigged a dummy battery without issues, and it's odd not to get full codec access that way. That might be a hardware limitation now, though.
Final Thoughts
The firmware is out, it's tested and it's good to go.
Keep Reading
Watch This Before Updating Your Canon R5 C to Firmware 1.0.4.1
Taking The Canon 24-105mm F2.8L For A Spin: A Real World Test
Gear in This Video
Gear in this video
As an Amazon Associate I earn from qualifying purchases. Buying through these links costs you nothing extra and helps support the channel.
