visionrouge

Thanks for sharing.
It's look like they tweaked the recovery time and add new functionality to the infamous counter that now include the length of previous recording in the balance.
If you shoot short clip,s you can shoot more of them (from 22 to 96 now in his testing)
Recovery time is about 2 minutes wait for 1 minute recovery, or one minute wait for one minute recovery inside a fridge.
Still a bit far from the graph I can see on this post threat. Recovery temperature look way faster than this.

Bye the way; 0 apology from Canon so far.
The best sentence is:
"We have and will continue to be transparent about recording limits for the EOS R5" 😂

Like you can't shoot any HQ mode after 60 picture during an hour inside a fridge...
Transparency? Please Canon, let me know where in your manual you explain this?

The max recording time is reset if you remove the battery cause we don't check temperature at boot but be assured we are very conservative on temperature management.


 

Oh Yes, I forgot someone all right, Andrew Reid, how could I, thanks Andrew!!

My R5 survived the 1 hour and 45 minute 8K IPB SD FAT32 recording test! Peaking at 62C exif from the end of the 3rd run to the end of the 6th run. Will the FW update allow us to run 8K IPB for more or less than 100 minutes at a time? I will present the exif temps shortly and send the data to Horshack.

News just in:
Canon is currently finding ways to create loops and bugs in R5's firmware to properly overheat at 20 minutes... code to keep running for two hours after. They've terminated the employment of the engineer responsible for choosing a heat-efficient, modern processor, allowing the R5's limitations to be bypassed.
A spokeswoman for the company released this statement: 
 "We deeply regret that some renegade customers have (illegally?) hacked the R5's abilities to record 8k footage and its limitations of a 20 minute recording every 2 hours. These customers are not in compliance with the user agreement and risk a non-functional device. We have addressed the problem and corrected the R5's firmware to perform as advertised."
Unofficially, the companies spokeswoman, categorically criticized EOSHD.com for their lack of believing the R5's specifications at the time of release, despite Canon's best marketing efforts in the matter.

It's always laike this with all Canon camera. If you lose the power, all parameters are not saved.

But here is what you should do.
Put your camera parameters as you like until you are ready to shoot.
Turn off the camera with the power switch (The recording parameters as shutter speed, aperture, iso,...) are saved there
Turn on the camera.
Record and drop the battery when you like.
When you put again the battery, the parameters will be the same as last turn on/off sequence.
 

\
As is wrote above, despite 60W of Peltier cooling power supplied, with a copper heatspreader covering the whole back of the R5 behind the LCD screen and cooling it to -5 degrees Celsius, risking internal condensation, it has ZERO impact on the time I can record in 8K RAW, with my R5 with firmware v 1.0.0.
I was willing to walk around with this ugly contraption if it would give me longer recording times. I need a full NP-F970 battery per hour for the maximum cooling. I doubt Tilta will apply that much cooling power.

Made a lot of progress on understanding the .DAT files. Using my Canon RP as a test bed, I recorded two 1:00 videos, one regularly and the other power-interrupted. I then copied the entire SD card for each case as a file image to my system for analysis. Prior to recording video each SD was prepared by fully wiping it with dd, then formatting in the camera. I also went back to FAT32 because it's easier to analyze those structures than exFAT.
This yields two very similar filesystem images. For the regularly-recorded video SD image I see a single data file (MVI_0478.MP4 in this specific case). However if I analyze the directory entries in the FAT32 structure I see a second file that's been deleted, named ?VI_047.DAT. The '?' is there because the file has been deleted (0xE5 is the FAT32 marker to indicate a deleted directory entry), meaning its original name is MVI_0478.DAT. Even though MVI_0478.DAT has been deleted its FAT32 cluster location and most-recent file size is still available in the directory entry.
Looking at the contents of the .DAT I see an "mdat" field. This is the raw MP4 data holding the video/data of the video - it's called an "mdat atom" in MP4 container parlance. The size of the .DAT file is exactly 128KB less than the size of the .MP4. What's more, the on-SD location of the .DAT is exactly 128KB after the .MP4, which means the two files are actually contiguous with each other.
So the camera wrote the .DAT first (while recording the video) but left 128KB before it pre-allocated in the FAT32 cluster table. When the video recording stopped it then wrote the 128KB before the .DAT, which contains all the other MP4 atoms necessary to represent the file, including the 'moov atom' which was reported missing when trying to recover the .DAT as .MP4 earlier using open-source recovery tools (failed because it's missing the full 128KB .MP4 header).
The 128KB MP4 container header stuff + mdat atom content represents the full MP4 file.
So the .DAT files we're seeing for the interrupted recordings on the R5 are the actual raw video/audio data sans the proper 128KB MP4 header area.
On my Canon RP the .DAT directory entry is missing for the interrupt recording. However if I go to the location on the interrupted-SD image as where the .DAT file exists on the good-SD image I see the mdat data. So it appears that on my RP the camera writes to this area during recording without first setting the directory entry to reflect that area is allocated. If you're able to see the .DAT files from your 1DX that means the behavior of that camera is different. Not sure how the R5 acts. Either way, recovering the .DAT file for my RP is trivial because I know what cluster it begins on by comparing it to the good-SD image.
I found the .DAT area on the interrupted-SD image and spliced in the 128KB MP4 header from the .MP4 from the good image. The file plays...and I hear a quick snippet of sound, but no video. So there is work to do there. But at least it demonstrates the basic integrity of the full MP4 is in place.
To get this working on R5 images we'd have to determine how to build the proper 128KB MP4 container header, the same as how the camera builds it when the user ends a video recording. This might be as simple as splicing from a "good" .MP4 image, but probably requires a lot more effort, and then graft that 128KB header data with the the .DAT file to reconstruct the full .MP4

Canon is not responsible.
Who can certify that the camera is not oberhrat after say 20 minutes ?
As camera has probably no tenperature sensor, and as 8k requires a lot of power processing, which translates to heat. 
FOR ME is totally normal that canon decide to not allow more than N number of minutes of recording. And yoy cannot say that Canon is dishonest in this way.
Canon eos C models are bigger with bigger cooling solutions and indded dont have 8 recording.
SO STOP complaining to Canon for that, and enjoy more than 15 minutes of full 8k recording in a dslr camera, coño

I have updated my post with 3 tests to do. One is pretty simple with the help of a external recorder, just to start stop with HDMI command

Yeah, unfortunately video is the main traffic grabber nowadays 

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

This is a Tsunami for Canon, but the outcomes may be quite interesting.

Think about the overall design? It was actually not too bad as they need to implement a timer to shut it down.
I can't imagine their meeting between the guy in charge of the R5 project when he learn that Canon will put a timer to shut it down, even if he did a great job preventing overheating.

Sony should start worried a bit too as the R5 camera is a real hybrid without this tiny battery cell. Not so much overheating, high resolution sensor, great AF and dynamic range.
The advantage of A7R3 will be reduced quite drastically. 

Can Canon goes with a firmware to remove this timer? Sure (And I don't think there is a need for a recall, it's purely software related)
Can magic lantern just create a smart app that change the value of the timer? That's seems quite simple if you know where this flag is located in memory.

Think of all these fake youtuber and website who have been reported about their camera not overheating, or even presented the Tilta solution as viable. What a joke.
All these blogs and comments explaining that the sensor have to overheat; that tests was badly done; bla bla bla.
How ridiculous they are now? How will they come clean on this one?
I can tell you that it put them on a weird position with the brand they supported if they keep this silence.

Canon have to answer this one.
Either by dropping the "overheat" flag by software, or at least explain what they did and call it with real word : "Recording Timer"

Knowing that it's a complete fabricated issue is actually a relief and I may consider one again. It just have to be fixed.

 

I'm not sure what will be the outcome of all this Canon overheat issue.

But in any case, it have helped me clearing a lot of so called "opinion leader" / Youtubers and other Facebook group that claim knowing something and analyzing a problem.

I listen people talking about their oven and explain why a R5 take 2 hours to cool down 😂
I have witness someone who never touched the camera and able to do a review, holding another body in their hand..
And when the facts became so obvious, and so their previous statement useless, they just jump to another subject. Their is no correction, excuses or update.

It shows how today's world is driven only by audience and not facts.

Ah, I see what you did there... never buy a Canon ‘DSLR’ again, leaving the mirrorless door ajar 😘

TBH and with best wishes to mr Reid's efforts that already achieved their honest goal without supporters - that bald guy looks to me as just another package of obscurity.  As also his (more sympathetic naive) psychologically typical advisory/conspiracy space arrangement of deep knowledge cave. IMO someone stole his dreamy ideal - so let's to be a little part of it.
It looks as counter-twin brother of that another advisory guy with presenting room where forever stays Christmas Eve...

/troll on
Canon is doing a silent recall, so no one heard or know about...
/Toll off

/troll on
Canon is doing a silent recall, so no one heard or know about...
/Toll off

/troll on
Canon is doing a silent recall, so no one heard or know about...
/Toll off

/troll on
Canon is doing a silent recall, so no one heard or know about...
/Toll off

No it does not overheat.
It is a fake information displayed on the screen to stop you for recording video HQ based on time and not temperatures.

Canon never says taking a 60 pictures per hour will stop you from taking video in HQ mode. 

Sorry; These are plain lies from the brand that limits the video capability drastically. The 8K logo on the main poster is clearly misleading. This was never explained anywhere.

No it does not overheat.
It is a fake information displayed on the screen to stop you for recording video HQ based on time and not temperatures.

Canon never says taking a 60 pictures per hour will stop you from taking video in HQ mode. 

Sorry; These are plain lies from the brand that limits the video capability drastically. The 8K logo on the main poster is clearly misleading. This was never explained anywhere.

I'm not sure what will be the outcome of all this Canon overheat issue.

But in any case, it have helped me clearing a lot of so called "opinion leader" / Youtubers and other Facebook group that claim knowing something and analyzing a problem.

I listen people talking about their oven and explain why a R5 take 2 hours to cool down 😂
I have witness someone who never touched the camera and able to do a review, holding another body in their hand..
And when the facts became so obvious, and so their previous statement useless, they just jump to another subject. Their is no correction, excuses or update.

It shows how today's world is driven only by audience and not facts.

I'm not sure what will be the outcome of all this Canon overheat issue.

But in any case, it have helped me clearing a lot of so called "opinion leader" / Youtubers and other Facebook group that claim knowing something and analyzing a problem.

I listen people talking about their oven and explain why a R5 take 2 hours to cool down 😂
I have witness someone who never touched the camera and able to do a review, holding another body in their hand..
And when the facts became so obvious, and so their previous statement useless, they just jump to another subject. Their is no correction, excuses or update.

It shows how today's world is driven only by audience and not facts.

I'm not sure what will be the outcome of all this Canon overheat issue.

But in any case, it have helped me clearing a lot of so called "opinion leader" / Youtubers and other Facebook group that claim knowing something and analyzing a problem.

I listen people talking about their oven and explain why a R5 take 2 hours to cool down 😂
I have witness someone who never touched the camera and able to do a review, holding another body in their hand..
And when the facts became so obvious, and so their previous statement useless, they just jump to another subject. Their is no correction, excuses or update.

It shows how today's world is driven only by audience and not facts.

I'd like to hear from Tilta as well as Canon.
If my fridge doesn't cool the camera externally what does their fan do differently?
Canon said officially: "Use an external fan to dissipate heat"
Well I used an external fridge to dissipate heat and it made no fucking difference.