My Canon EOS R5 recording 8K video 50 minutes straight

[Electroholic Anonymous]

I had to cut the 5th run of 17 short to 10 minutes, battery empty icon was flashing. Doing a 6th run with a fully charged LP-E6NH and letting the overheating timer crash and lock me out. Doing the JPEG immediately after. If it reaches 20 minutes, if it gives more we might surpass 100 minutes.

5th run also peaking at 62C. It's an all day 8K camera, people.

[wolf33d]

FW update to fix thermal issue coming tonight
https://www.canonrumors.com/canon-eos-r5-firmware-update-coming-in-the-next-24-hours/

Obviously it's not like they will release many of them so the moment of truth is tonight. Tomorrow we will know if the camera is usable or not. 
Either they will go deeper in the same and shit on us with allowing something like 5min more recording and little shorter recovery (but overall still timer based), or they will make it right and make it non timer based but temperature based making this camera perfect or if they can't (because of poor thermal data access) then at least push the timer as much as they can according to extensive testing. From what we see in the test from Andrew and others, that camera should have no problem going to the recording limit of 30min and then recover in that time or less. 

Fingers crossed. 

[ntblowz]

Just now, jacoblewis said:

Clickbait? https://www.canonrumors.com/canon-eos-r5-firmware-update-coming-in-the-next-24-hours/

We will know once it's up

[mechanicalEYE]

Hope they dont sprinkle in a little more cripple 

[Electroholic Anonymous]

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.

[douglaurent]

Abruptely unlocking the battery grip door (with two batteries in it) while recording, and then inserting a new CFexpress card after the camera has shut down, unfortunately did not reset my timer.  Why did it work in one of those videos?

Was it because i didn't record one long clip until the limit?  To avoid getting corrupted clips of important material, I intentionally did stop the regular shots shortly before the limit, and then turned off the camera power in a dedicated last recording meant to be corrupted.

That did work so far, but didn't solve the timer reset problem.

[Electroholic Anonymous]

At the end I did not take a single JPEG, no, I hammered the buffer, guess, did the temperature get higher than the video max of 62C, or, lower?

[PaulUsher]

18 hours ago, wolf33d said:

I think you should create a new thread just for that petition. In fact it would be nice if @Andrew Reid created a blog post with it as it would reach far more people. 

Thanks @wolf33d People are seeing it (1286 views) but only a fraction are signing it. Importantly, Canon were emailed the petition end of play yesterday, containing all signatures thus far and a link to the live version which continue to accumulate.

The 30-day returns period (from release 30 July) expires this weekend so technically Canon have until then to respond with a firmware update that resolves the complaints. If they don’t, then petitioners could opt to wait the full 30 days from their signature before taking further action.

Depending on where someone files a class action, they may need a minimum party of 40 claimants who have an existing and unresolved complaint with the company. Since this petition has preserved the complaints, the dates, and the contact details of well over 40 prospective claimants - and if Canon demonstrably ignores their complaints to the expiration of their 30-day returns period - then this petition offers decent case development to whomever files the class action.

Let’s see if that firmware update comes before Friday and, assuming it doesn’t satisfy, then yes let’s turn the pressure up whilst the technical wizards of this forum continue to find alternative solutions. Keep up the good work lads.

https://www.change.org/p/stop-the-cripple-hammer

[horshack]

6 minutes ago, Electroholic Anonymous said:

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.

Thanks. So the only difference between this run peaking at 62C and earlier one at 72C was the camera being on the desk? Ambient temps in your room the same as before? How warm does the bottom of the camera get? If that's a thermal conduction point maybe the desk was inhibiting it whereas it would be available to the air on your tripod.

[Electroholic Anonymous]

7 minutes ago, horshack said:

Thanks. So the only difference between this run peaking at 62C and earlier one at 72C was the camera being on the desk? Ambient temps in your room the same as before? How warm does the bottom of the camera get? If that's a thermal conduction point maybe the desk was inhibiting it.

The ambient temperature is perhaps only 1 or 2C lower, that should not make such a difference. I think it's mainly convection, and that I held it in my hands perhaps a minute at the start and end of each run earlier, and now on the tripod I did not. Ah, and that's it, I used 8K 24p now, and 8K 30 earlier, that's of course it. I specifically chose 24 p for the long test, because that is the mode I am personally most interested in. I could run the 8K30p also, we'll see. The inordinate number of RAW+jpeg's that I shot at the end produced 64C exifs after only 257 photos. So that's in line with my personal experience of the R5 feeling hotter hammering lots of stills than recording 8K.

[horshack]

11 minutes ago, Electroholic Anonymous said:

The ambient temperature is perhaps only 1 or 2C lower, that should not make such a difference. I think it's mainly convection, and that I held it in my hands perhaps a minute at the start and end of each run earlier, and now on the tripod I did not. Ah, and that's it, I used 8K 24p now, and 8K 30 earlier, that's of course it. I specifically chose 24 p for the long test, because that is the mode I am personally most interested in. I could run the 8K30p also, we'll see. The inordinate number of RAW+jpeg's that I shot at the end produced 64C exifs after only 257 photos. So that's in line with my personal experience of the R5 feeling hotter hammering lots of stills than recording 8K.

Odd that stills would get hotter. Would really like to see that verified with measurements one day. That's either the sensor (14-bit readouts for stills vs likely 12-bit operation for video), the CFE card (total data rate, or perhaps peak rate during long bursts), DIGIC (more processing for stills, which seems unlikely vs handling/compression for video), the fact you're holding the camera for stills and not video (conduction), etc...

One way to eliminate the sustained rate difference is to try 8K raw.

[Electroholic Anonymous]

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

[Electroholic Anonymous]

[Andrew Reid]

7 minutes ago, Electroholic Anonymous said:

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

Where is this chart from? Is it your test data or somebody else's?

Asking because I want to give credit to the right people, if I feature it on the blog. Cheers EA

[Electroholic Anonymous]

It is from the test I ran the past few hours. Now with your name 😉

[Andrew Reid]

I see. The credits were confusing me, as I thought they'd contributed the data.

So it's very interesting that it levels off like that.

Would it be possible to change the time axis to show minutes from 00:00 instead of the time stamps?

Cheers!

[Electroholic Anonymous]

19:02:22,00006996.MP4,47.5475,28
19:03:10,00006997.MP4,47.5475,32
19:03:58,00006998.MP4,47.5475,34
19:04:45,00006999.MP4,47.5475,36
19:05:33,00007000.MP4,47.5475,37
19:06:20,00007001.MP4,47.5475,39
19:07:08,00007002.MP4,47.5475,40
19:07:55,00007003.MP4,47.5475,41
19:08:43,00007004.MP4,47.5475,42
19:09:30,00007005.MP4,47.5475,43
19:10:18,00007006.MP4,47.5475,44
19:11:05,00007007.MP4,47.5475,45
19:11:53,00007008.MP4,47.5475,46
19:12:41,00007009.MP4,47.5475,47
19:13:28,00007010.MP4,47.5475,48
19:14:16,00007011.MP4,47.5475,48
19:15:03,00007012.MP4,47.5475,49
19:15:51,00007013.MP4,47.5475,50
19:16:38,00007014.MP4,47.5475,50
19:17:26,00007015.MP4,47.5475,51
19:18:13,00007016.MP4,47.5475,52
19:20:28,00006996.MP4,47.5475,48
19:21:16,00006997.MP4,47.5475,51
19:22:03,00006998.MP4,47.5475,52
19:22:51,00006999.MP4,47.5475,52
19:23:38,00007000.MP4,47.5475,53
19:24:26,00007001.MP4,47.5475,53
19:25:13,00007002.MP4,47.5475,54
19:26:01,00007003.MP4,47.5475,54
19:26:48,00007004.MP4,47.5475,55
19:27:36,00007005.MP4,47.5475,55
19:28:23,00007006.MP4,47.5475,56
19:29:11,00007007.MP4,47.5475,56
19:29:59,00007008.MP4,47.5475,56
19:30:46,00007009.MP4,47.5475,57
19:31:34,00007010.MP4,47.5475,57
19:32:21,00007011.MP4,47.5475,57
19:33:09,00007012.MP4,47.5475,57
19:33:56,00007013.MP4,47.5475,58
19:34:44,00007014.MP4,47.5475,58
19:35:31,00007015.MP4,47.5475,58
19:36:19,00007016.MP4,47.5475,58
19:38:32,00006996.MP4,47.5475,55
19:39:20,00006997.MP4,47.5475,57
19:40:07,00006998.MP4,47.5475,58
19:40:55,00006999.MP4,47.5475,58
19:41:42,00007000.MP4,47.5475,58
19:42:30,00007001.MP4,47.5475,59
19:43:18,00007002.MP4,47.5475,59
19:44:05,00007003.MP4,47.5475,59
19:44:53,00007004.MP4,47.5475,59
19:45:40,00007005.MP4,47.5475,60
19:46:28,00007006.MP4,47.5475,60
19:47:15,00007007.MP4,47.5475,60
19:48:03,00007008.MP4,47.5475,60
19:48:50,00007009.MP4,47.5475,60
19:49:38,00007010.MP4,47.5475,60
19:50:25,00007011.MP4,47.5475,61
19:51:13,00007012.MP4,47.5475,61
19:52:01,00007013.MP4,47.5475,61
19:52:48,00007014.MP4,47.5475,61
19:53:36,00007015.MP4,47.5475,61
19:54:23,00007016.MP4,47.5475,61
19:55:11,00007017.MP4,47.5475,61
19:56:53,00006996.MP4,47.5475,58
19:57:41,00006997.MP4,47.5475,60
19:58:28,00006998.MP4,47.5475,60
19:59:16,00006999.MP4,47.5475,60
20:00:03,00007000.MP4,47.5475,61
20:00:51,00007001.MP4,47.5475,61
20:01:39,00007002.MP4,47.5475,61
20:02:26,00007003.MP4,47.5475,61
20:03:14,00007004.MP4,47.5475,61
20:04:01,00007005.MP4,47.5475,61
20:04:49,00007006.MP4,47.5475,62
20:05:36,00007007.MP4,47.5475,62
20:06:24,00007008.MP4,47.5475,62
20:07:11,00007009.MP4,47.5475,62
20:07:59,00007010.MP4,47.5475,62
20:08:46,00007011.MP4,47.5475,62
20:09:34,00007012.MP4,47.5475,62
20:10:22,00007013.MP4,47.5475,62
20:11:09,00007014.MP4,47.5475,62
20:11:57,00007015.MP4,47.5475,62
20:12:44,00007016.MP4,47.5475,62
20:14:50,00006996.MP4,47.5475,58
20:15:38,00006997.MP4,47.5475,60
20:16:26,00006998.MP4,47.5475,61
20:17:13,00006999.MP4,47.5475,61
20:18:01,00007000.MP4,47.5475,61
20:18:48,00007001.MP4,47.5475,61
20:19:36,00007002.MP4,47.5475,61
20:20:23,00007003.MP4,47.5475,62
20:21:11,00007004.MP4,47.5475,62
20:21:58,00007005.MP4,47.5475,62
20:22:46,00007006.MP4,47.5475,62
20:23:34,00007007.MP4,47.5475,62
20:26:21,00006996.MP4,47.5475,57
20:27:09,00006997.MP4,47.5475,59
20:27:56,00006998.MP4,47.5475,60
20:28:44,00006999.MP4,47.5475,60
20:29:31,00007000.MP4,47.5475,61
20:30:19,00007001.MP4,47.5475,61
20:31:06,00007002.MP4,47.5475,61
20:31:54,00007003.MP4,47.5475,61
20:32:41,00007004.MP4,47.5475,61
20:33:29,00007005.MP4,47.5475,61
20:34:16,00007006.MP4,47.5475,61
20:35:04,00007007.MP4,47.5475,62
20:35:52,00007008.MP4,47.5475,62
20:36:39,00007009.MP4,47.5475,62
20:37:27,00007010.MP4,47.5475,62
20:38:14,00007011.MP4,47.5475,62
20:39:02,00007012.MP4,47.5475,62
20:39:49,00007013.MP4,47.5475,62
20:40:37,00007014.MP4,47.5475,62
20:41:24,00007015.MP4,47.5475,62
20:42:12,00007016.MP4,47.5475,62
20:42:59,00007017.MP4,47.5475,62
20:43:47,00007018.MP4,47.5475,62
20:44:35,00007019.MP4,47.5475,62
20:45:22,00007020.MP4,47.5475,62
20:46:10,00007021.MP4,6.423083333,62

That is the CSV data, so have at it 😉

[Electroholic Anonymous]

In case people would start doubting whether this is all just made up. Here is a screenshot of the MP4 file thumbnails of the 4th run.

[Electroholic Anonymous]

I will try to upload the whole boring a7R4 video of this 100+ minute 8K IPB test now after a quick and dirty render.

And about the FW update, I consider it riskier to update my FW then to run the R5 like this. Will they close this loophole, will they cripple my much loved superb Canon EF glass that has never ever worked better on any native body I owned, all to give RF an edge, in exchange for 20% more overheating time? No thanks!

[horshack]

9 minutes ago, Electroholic Anonymous said:

I will try to upload the whole boring a7R4 video of this 100+ minute 8K IPB test now after a quick and dirty render.

And about the FW update, I consider it riskier to update my FW then to run the R5 like this. Will they close this loophole, will they cripple my much loved superb Canon EF glass that has never ever worked better on any native body I owned, all to give RF an edge, in exchange for 20% more overheating time? No thanks!

Thanks for the .CSV data. Here's your data plotted. The running elapsed time was calculated from the EXIF timestamps: