kaylee

They put the fan you're supposed to hold up on the port side of the R5 inside the C70. That's at least $1500 right? So then they threw in the NDs to cover the rest of the price bump for good measure.

Yes I see them now, maybe it's only a 2 and 4 stop ND filter, I just can't imagine how they will cripple it, I've learned though thanks to the R5 and R6 fiasco; never underestimate Canon's cripple hammer creativity.
 
I'll bet Canon wishes they could only offer 1080P and get away with it. I think they won't offer RAW, probably no CLOG3, no XLR, no more than a 4 stop ND filter, definitely no IBIS, oh and it will overheat but only if it detects that you haven't yet purchased a Cinema camera. With the purchase of each cinema camera you'll get an unlock code for the CLOG3 and removal of the overheating timer in the C70.

When dinosaurs roamed the earth and I was starting off as a tape op, Beyer DT100s were all a boy needed and I used to wear them all day long.
I use Audio Technica ATH-M50s now and I can still do fairly long stretches with them but the DT100s still edge it for me in terms of duration.
I don't like the way either option messes up my bouffant though.

Someone suggested that the overheat icon should be changed with a middle finger on a future firmware... I love this idea!🖕
 

According to TechRadar, the firmware doesn't address the overheating and actually engages it when using an external monitor:
"Canon has today released the EOS R5’s first firmware update and it’s available to download from the camera maker’s regional websites around the world. However, if you were expecting the firmware to improve on the current video limitations the R5 suffers from (as previous reports indicated it would), you’re going to be sorely disappointed.
The EOS R5 firmware version 1.1.0 only brings a couple of minor upgrades – it improves image stabilization for video recording, while also improving the combined stability of the camera’s in-body image stabilization system when paired with a stabilized lens, specifically the RF 100-500mm f/4.5-7.1 L IS USM telezoom.
According to Canon, the update also ensures that the overheat control on the EOS R5 doesn’t get disabled when using an external monitor or recorder. It will also improve the accuracy of the video time display when recording several short clips back to back.
None of these are quite what we were expecting but Canon has said there’s more to come."

Thanks for the chart. It's good to have it in black and white that there's only a 6-8C increase in temps after 20 minutes.
Certainly not enough to justify the shutdown (let alone a long lockout).
And also interesting to see the temps are basically flat for the last 50 minutes after the first 50 minutes.
I think if we are going to put credits on stuff by the way, make sure to include @BTM_Pix
His app has been key to understanding the temperature status and EXIF temp.

Actually it's both.
The original has quite a lot of blue in it, and the reference images have no objects in them that are blue and all the colours in the reference image are in completely the opposite direction in terms of colours.  
You can pull a key and neutralise out the blues, but then you end up with some salmon tones, which you then need to fix, and in the end you end up with a background that is bland and may as well have been desaturated.
The reference images all have darker green foliage in the background, the footage has a bright orange/blue city in the background.

Ultimately, the best thing to apply for this look would be one of these:

 

You sir win the internet today. I just tried it on my Canon RP, which like the R5 forgets any changes to the camera's settings (like exposure settings) if you pull the battery in the middle of the recording but will remember the changed settings if you stop a recording normally.
Procedure:
Tape down the door sensor and leave the door open so the battery is accessible Put a 32GB card in the camera and Turn the camera on and format the card. It will automatically use FAT32 cards with a capacity <= 32GB Start a video recording, in this case I used 4K 24P, which has an average total video/audio bitrate of 14.43 MB/s. Shoot a video whose length will exceed 4GB. For my 4K 24P that's any video longer than just under 5:00. I shot one for exactly 5:00 Pull the battery Check the card and verify there's a single .MP4 file Reinsert the battery and verify the camera "forgot" the previous session's settings We know the camera saves its settings whenever it has successfully recorded a video. The question is whether @Jn- idea will avoid that save for the FAT32-case of splitting up a video file at 4GB/each (FAT32 limit), provided we still pull the battery at the end of the recording. In other words, will the camera save NVRAM for each intermediate 4GB-split file or only for the final file after properly stopping a recording?
Drumroll...It works! My RP's aperture was f/4 when I turned it on for step #3. I changed it to f/11 for the test. After reinserting the battery my RP's aperture reverted back to f/4!
Andrew, please test this ASAP on your R5 and see if it matches my RP's behavior of forgetting the settings, the most important of which is of course the thermal timer.
 

Thanks Kaylee!!
I think we should get a new guinea pig meme going.

Everyone is so focused on the R5 debacle but stay tuned for some further Canongate reveals as the R6 releases this week..

I'm sorry, but this just isn't the case. People buy C-line video cameras for a plethora of reasons and for many use cases there's no way they would swap out a full-control, fully specified professional cine camera for a hybrid body. The form factor of a hybrid just wouldn't cut it in a wide range of professional working situations. Codecs, resolution and so on are important, but they really are only one part of the considerations that apply to choosing a working tool.

Just in case anyone missed it here is the hack methodology in full:
https://www.eoshd.com/news/this-is-my-canon-eos-r5-recording-8k-video-50-minutes-straight-until-empty-battery-video-evidence/
Here’s what I did during the 50 minutes 8K test:
00:00 – Power on the EOS R5 normal from cold 01:00 – Remove battery card door, camera powers down but power switch remains in “on” position 01:30 – Insert small screw in the battery door sensor as pictured below. Camera turns back on. 02:00 – Set video mode to DCI 8K resolution (IPB codec) to SD card. 02:10 – Hit record 17:00 – Roll to approximately 17 minutes (“overheat” warning icon will be flashing) 17:05 – At this point pull battery during recording 17:15 – With battery disconnected remove SD card and put freshly formatted SD card in the slot instead 17:20 – Push battery back in and power will return, overheat warning is gone and timer is reset 35:00 – Record for another 17 minutes! 50:00 – End of test I could go until the battery died, basically.

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.

About having to manually put all your settings in...
Imagine if someone had already written an app that uses Canon's API for testing this overheating and that could also reset all those settings in one go when you haven't used the battery reset workaround that I certainly never advocated using?

Andrew....do you know the "Magic Lantern" guys? Do you know how to contact or reach out to them?
I would literally bet my life that they are very interested in this R5 mess. 
If you want to upset Cannot and REALLY ring their bell, get some dialog going with ML and REALLY start a fire here....
If Cannot has not yet encrypted their firmware, could you imagine ML reversing all these cripples in firmware? Maybe It could be just as easy as taking timer values in lines of code and replacing them with high values like "99999" or something of that sort.
Cannot doesnt fear bad R5 press....but they DO absolutely fear somebody circumventing their carefully chosen marketing strategies and tactics!

That is certainly in line with the sort of thing I'm not talking about.
It's likely a smaller battery in the R5 so it would likely require a smaller version of what I'm sure we can all agree that I'm absolutely not talking about.

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.

Ok. I know many dps shooting tv dramas, indie and studio films in Korea using af. But I guess your experience and reality is all that matters.
And I specifically said docus, weddings, bts and indie filmmaking so it vibes with most of you in the West but again I guess your 'pro' opinion is reality. Maybe I need to reboot my simulation.

How can the camera build up heat to throw the overheat warning sitting in the menus at idle but run for extended times externally without getting a warning? Firmware cripple??
How can one shoot in 102 degrees externally for an hour with a camera that is said to overheat without even a overheat warning, but overheat internally indoors in cool air? Firmware cripple??
How can one get exif data that says the camera had a temp of 65 C / 149 degrees in 100 + degrees operate without an overheat warning but another user saw overheat warning at 46 C?? Firmware bugged the F out??
Doesn't really matter if it was intentional or accidental, it doesn't make sense and should be corrected.

It’s not crippling it’s the cynicism that everyone finds offensive. In fact this is canon’s snarky answer to all the criticism built over the years over their crippling. It’s like the C200. You can have the usual 8bit but you also get the completely impractical raw and also no 10bit which is what most professionals would use. Now you can’t accuse them of crippling. It’s the same cynicism with the R5. You get hq4k AND 8k so you can’t accuse them of crippling. But they can only be used for 20 minutes every 3 hours otherwise just use the line skipping 4k that was meh even 5 years ago. So before you point fingers and say we’re all noobs for pointing out this new level of cynicism from Canon maybe you should look in the mirror and try to see what’s really goin on. Noob. 

crippleclock.exe

Personally, I'd feel like I just bought a hotrod of a car that can only drive 5 miles.

once people dig deep enough into the firmware we're gonna find cripplehammer.exe