Andrew Reid

It is because the camera may write the last clip length and 'overheat' timer status to the cripple clock memory when you hit stop on the recording. Going to test a few things around this aspect soon.

Ah Sony are just another bunch of opportunists really, using the suffering of a rival to drum up some more sales - I'm no great fan of the A7S III. I think this is a watershed moment, and I hope it encourages people to spend their money differently. Maybe buy more from Sigma, who are family owned. Let's put business ethics in the spotlight. Let's see what really goes on behind closed doors and what they try to hide from their customers.

The other ugly thing is that I have taken an absolute beating online with people questioning my reputation left right and centre for revealing this timer and behaviour from Canon. Canon meanwhile, brand reputation virtually untouched, not two hoots from them, no statement, no recall and the EOS R5 continues to fly off shelves!! BBC and CNN tech reporters should be all over it. Where are they?

Yes certainly possible but it is one heck of a reverse engineering project with many complexities and arduous effort, and would likely take a long time even for somebody as skilful and experienced as a1ex. I think after being mislead we deserve Canon to come out with an official fix, and a public apology. It would also be smart of Canon to make a development kit so that Magic Lantern didn't have to reverse engineer in order to add modules and code. Can you imagine if developers had to do this to make Android apps?!

Interesting point. I'll see if I can give it a go. First I need to work on a YouTube video showing it going for 1 hour in 8K. That should shut some people up.

On topic please people.

Updated article with more clarifications. It is battery backed RAM not NVRAM EEPROM (that's why the Baidu internal battery pull worked) but the basic workings are the same https://www.eoshd.com/news/canon-eos-r5-so-called-overheat-timer-defeated-by-a-single-screw-in-battery-door/ A lot to get our heads around, so please if you are commenting on this topic, make sure to read the full article first.

Yes that's true. Lot's to try next. I'll see what state the clip is in and see if I can still transcode it in EditReady. The 8K HEVC is a bitch to edit! So I'll be doing this anyway with 8K material to ProRes. The main goal for me is not so much the workable workaround but rather the truth gets out, and to force Canon's hand in removing any artificial limitations. Your contributions here have become invaluable, so thank you. Yes this could indeed work but it'll be beyond the patience of most filmmakers I think. I'll try @BTM_Pix's suggestion first and see if there is a simple way to get around it and produce a usable last recording...

Looks like somebody has been right?

Magic Lantern just became Magic Screw. Tried the second test differently. Found a way to get the full record times back: https://www.eoshd.com/news/canon-eos-r5-so-called-overheat-timer-defeated-by-a-single-screw-in-battery-door/ You're only supposed to blow the bloody battery door off!!!!

On Friday, I received a message from the lead developer at Magic Lantern. An interesting theory was being put forward by one of their open source contributors, which he believed could defeat the so-called overheat timer on the Canon EOS R5. Initially I was skeptical as to whether it would work! Mainly because the initial real-world tests on my own EOS R5 did not reset the timer. But then, a break-through. Magic Lantern just became Magic Screw! Read the full blog post here: https://www.eoshd.com/news/canon-eos-r5-so-called-overheat-timer-defeated-by-a-single-screw-in-battery-door/

It's worth another look. Quite a few variables and ways to do it. I haven't had the time try everything to be honest. The guy on YouTube has tried pulling the battery during a recording, and got 5 mins remaining. I also got 5 minutes remaining, but stopped the recording first. I thought at this point, if the timer is in RAM then it should go up to 20 mins in 8K not 5. Then I went out and had an ice cream with the girlfriend. So tomorrow maybe I should put more effort in!?

It has parallels with the world in general. We have in Russia today a dying man who has been horrifically poisoned, screaming in agony on a plane and straight into a coma from which he may never pull out. Leader of the opposition to Putin. The RT news anchor tosses the peasant people some lie. "It is low blood sugar. Always carry candy" The low effort of that bullshit, and the distain for the intelligence of the general populace. And it is the same thing with Toneh. Toss the peasants some badly research bullshit dressed up with a whiteboard zapping key phrases at the audience. Pure clickbait. Pure cynicism. Ah you stole the idea... Nobody will notice. Just say you forgot. Whatever. Who cares. End of days stuff my friends. Thank you to all on here who have helped research and inform on the overheating findings these past few weeks.

Amazing how easily people are fooled. Suddenly Tony is considered the source. Makes me fucking sick.

Breaking news... His source was actually the well known EOS DH. The famously relaxed guy who doesn't mind being ripped off at every turn and his journalism work uncredited. The DH stands for "Die Hard" as in die hard Canon fan, loyal to the bone and willing to pay $4000 for broken shit. Not a cross word spoken. You know... A bit like how TONEH is with Sony. I think myself and BTM_Pix deserve a credit and apology in TONEH's next video? Don't you? Let's make it happen. And come up with a little plan.

EOSHD tabs in his browser...

"Breaking news" And people wonder why I take issue with so many YouTubers.

Yeah, I don't pay $4000 to have to reset a cripple clock or disassemble the body. Over to you Canon! (That doesn't mean to say we shouldn't continue to explore and investigate. I find the workarounds shed light on the camera's design and behaviour, which allows us to hold Canon to account with hard evidence).

I have shot a comparison between the A7R IV and EOS R5 myself. Blog post coming up. The A7R IV has the sharper looking 4K and is very good in low light. 8bit not too much of a hinderance really. The EOS R5 is much softer in the 4K mode we can actually use (pixel binned) but has less aliasing, and moire is well controlled. It's alright. Does it let Canon off the hook though? Nope.

You are talking informed armchair shite. YOU have not taken a single shot with YOUR EOS R5 and reported anything here of value. YOU have not taken the back off like some people, and even measured internal temps with an infrared thermometer. A heavy load for an Intel CPU is 90C. I have a laptop that registers even 95C during rendering. If the CPU goes above this it will throttle to maintain 90C-95C. Only if the temperature carries on rising, is it a risk. 90C is fine. Fans and heatsinks in a PC are only there to maintain stable temperatures - to dissipate heat - for very hot running components that use a lot of energy. A smartphone does not have a fan, as the energy consumption is lower and efficiency far higher - these kind of CPUs are RISC as is the ARM based CPU in the EOS R5 and R6. The EOS R5 maintains a stable temperature below 65C in all video modes - this is not conjecture, it shows in the PCB temperature sensor and EXIF metadata, infrared thermometer tests, and just plain old application of common sense. If the EOS R5 can run at "heavy load" in 8K for 10 mins... what's so special about the 20 min point at same temperature that it has to shut off... Nothing. It's a timer. And the recovery times are even more artificial. If your laptop can render 8K for 20 mins at 65C it means the temps are stable and plateau at a comfortable level. Same with a camera CPU.

Just tried this as well. It does forget the aperture because it didn't write it to NVRAM in time if you pull the battery quite quickly - I tried after about 10 seconds, with the battery door open and a small screw lodged in the pin to force the camera into ON state even with door open. It does not forget the timers That seems to work off a separate clock to the main date / time and is constantly ticking away like a quartz powered by the button cell. One solution I wish the Chinese guy had tried is to permanently remove the internal battery and see if the recovery timer is reset every time you reboot without it. It would be annoying to be kept asking to input date and time on every startup though.

Let's be honest, these stupid workarounds are not practical on set. It is up to Canon to fix the damn camera, not us. We paid the money, and not a small amount. Unscrewing the back, prodding the card door sensor, ripping the clock battery out... None of it is acceptable for $4000

We tried this via the Wifi App by @BTM_Pix It just changes the data and time, it does not reset the separate clock used to measure the camera up-time. I can confirm Magic Lantern are looking into it.

58C for 45 mins in the special "not limited by heat" mode!! But what's a few degrees C between friends when you want to sell a C500 II, right?

I see it plateaus around the 57C-61C mark for 15 mins. So it can roll along just fine at 60C for 15 mins... But come the 30th minute of thou hour, the great Thermal Christ beams down from Cripple HQ to read us the Ten Commandments.