Django

I have the R5 and the 1Dx III but not the R6 but the 1Dx III being somewhat similar (probably the same) sensor I may help a bit.
R5 FF 4k vs 1Dx III FF 4k is very similar as you say but the rolling shutter is a huge difference.
R5 4k 120 is miles ahead of 1Dx III 1080 120….. not even fair.
R5 4k LQ is miles ahead of 1Dx III 1080
 
On the processing of RAW vs. 10bit other than on an M1 or waiting on the new intel CPUs the RAW is way faster in Resolve PC. RAW is much faster. The problem for is mostly storage so it depends on your usage and archiving strategy. I would suggest downloading some files 10bit and RAW and compare on your machine.
 
So far I never hit the recording limit of the R5 and I mostly shoot RAW or 4k 120. But here is cold and I do a lot of 1-2min max takes with breaks in between. Before I was turning the camera off between takes now I don’t bother anymore.
But having say that not sure I would live with the R6 risk that I cannot shoot 4k…….. as I said 4k LQ is way better that full hd actually imo is a solid 4k….
 
R5 big plus:
- Rolling shutter
- RAW
- very usable 120fps
- Non overheating 4k modes FF and S35
R6 plus:
- cheaper
- 4k 60fps quality
Are these worth 2k more? Only you can really answer this.

Bro I think you know that the R6 will be a great option for you. Think of what you’ve had to work with using canon in the past. You’re getting 4K 10 but super 35 with PDAF. Despite all the limitations I think that’s all you really need, realistically. If you have 2K laying around I’d definitely get the R5 but I don’t think it’s something you need or will really miss not having. My two cents. 

Welcome back...its' been awhile. I pretty much posted all of my thoughts on the R6 on the following thread, which is here: 
 And I ended up with the Panasonic S5 which is perfect for my uses in every way (except AF of course) so this thread may be useful as well:
 
 

In defense of the C200, it also introduced 4K60p, internal RAW recording, and Touch DPAF... amongst a host of other features, IO, media and ergonomic enhancements .
It was a lot more than just a C100 with 4K. Aside from 10-bit codec, it actually did more than the at the time flagship C300 mk2!
And that’s the funny thing with Canon. Lower end models often have better features than flagship models but always have the infamous cripple hammer on some crucial aspect.. 

As a Canon EOS Cinema owner since the C100 (which I still own alongside C200) this is my dream Canon cine cam.  Scratch that, it's my dream cine cam period. I will be selling off my C100/C200 for the C70. 
Of course perfect it is not, I will be missing Canon RAW Lite, EVF, SDI & custom LUTs.
I'll be keeping my FS7 for gigs where EVF, SDI & LUTs are mandatory.
I think I might also upgrade EOS R to R5 for RAW/8K B-cam shots.
If anyone in EU is looking for a good deal on a mint boxed C200 with CFast media, HMU! 

In defense of the C200, it also introduced 4K60p, internal RAW recording, and Touch DPAF... amongst a host of other features, IO, media and ergonomic enhancements .
It was a lot more than just a C100 with 4K. Aside from 10-bit codec, it actually did more than the at the time flagship C300 mk2!
And that’s the funny thing with Canon. Lower end models often have better features than flagship models but always have the infamous cripple hammer on some crucial aspect.. 

In defense of the C200, it also introduced 4K60p, internal RAW recording, and Touch DPAF... amongst a host of other features, IO, media and ergonomic enhancements .
It was a lot more than just a C100 with 4K. Aside from 10-bit codec, it actually did more than the at the time flagship C300 mk2!
And that’s the funny thing with Canon. Lower end models often have better features than flagship models but always have the infamous cripple hammer on some crucial aspect.. 

No, No need to do anything

It's very simple.
Canon do a very simple calculation.
When camera is running, a counter is setup. When the counter reach a certain level, you have a warning logo.
If you keep recording, the Log will become a shut down. This raise a flag that I will call "Fake Overheating flag"

At each of these step Canon is writing the exact time this occurs. Let's call it the "overheat start time".
This is done in an eeprom that is kept even if you remove the battery. The writing occurs when you shut down with the power button. This is the mistake right there.

There are only one way of getting the camera to work again is to wait extra time.
Canon do a simple calculation between "actual time" and "overheat start time". This way, even if the camera is off without battery, they can keep the time running with the help of the RTC.
It's a way of doing coding something very fast.

They also put a conditional test on "Fake Overheating flag" to make sure changing the time during the overheat mode will not change this calculation. My best guess is that they modify the "overheat start time" with the same value the camera time is shifted in this condition only. So each tentative to play this way is not working.

But I have the impression that the new "overheat start time" is written ONLY when the camera is power down. The new real time is written immediately.
So by dropping the battery, you are avoiding the "overheat start time" to be written and only the last one is in the memory.

When the power is restored, there is the calculation to see if you have been waiting enough. But based on the old "overheat start time", not the one shifted by the time modification. BOOOOM.

So the flag is now remove and the camera can start.
Even better, The camera is writing this new "Fake Overheating flag" value into the EEprom. So you can turn off the right way and it will restart without any problem.

You can now shift the time back, there is no check for a possible "overheat start time" cause we are not supposed to be in overheating mode.

So whatever card you are using, whatever R5 or R6, whatever firmware... it's working.
That was my idea at first when I noticed that the battery drop do not save all parameters. An yes, it works so beautifully.

Medium format & cheap don't really associate.. that said the GFX 50R is now only $3500 which places it around FF cams like A7R4/A7S3/R5.
Unfortunately the video specs are crap..

Cinema cams have active cooling and therefore don’t overheat. You can clearly see the fan vents on the side. Probably no weather sealing though.

The form factor and model number would suggest a price point and segment under the C200, which surely has a mark 2 coming soon. 
 
This is basically the super long awaited C100 mk3.

I have zero doubt it is going to be 10-bit 4:2:2 as even the $2500 R6 has such codec. The pricing however does appear a tad steep for an entry level cine cam although Canon C line has never been cheap..

The form factor and model number would suggest a price point and segment under the C200, which surely has a mark 2 coming soon. 
 
This is basically the super long awaited C100 mk3.

How about that deep freeze test where the R5 was able to shoot like an hour before overheating warning? Looks like the timer gets triggered after a certain temp threshold and the battery door hack defeats the artificial recovery time.
Canon will never apologize just like Apple never did during their numerous scandals like Antennagate where Jobs responded:
 
 "Just avoid holding it that way" - led to widespread mockery, and the phrase "you're holding it wrong" still sticks around whenever an Apple product has a fault. Eventually, Steve Jobs held a press conference at Cupertino and announced free bumper cases for all users, saying: "We're not perfect… but we want all our users to be happy."
Same with bendgate: Apple responded to Bendgate, stating that it had received only nine complaints of bent devices and that the damage occurring due to regular use was "extremely rare". Apple offered to replace phones that were bent.
At best Canon will issue a firmware “fix” claiming “overheat management optimization” or something. 

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

hmm well I guess there goes the whole artificial timer conspiracy theory. now all we need is a portable cryogenic device to carry R5 during shoots!

Yikes what a messy situation.
Although I guess the good news is no recall necessary. The rumored firmware update will probably “fix” the issue. They’ll claim a “bug” messed up recovery times and software “optimizations” will enhance heat management & recording times.
 

No camera is perfect. We all have different needs.
S1H is Netflix approved as it is one of the only large sensor hybrids that check marks their capture requirements ie. Timecode, high bitrate 10-bit 4:2:2 Log, DCI 4K, Anamorphic support. Of course the fact it has an active cooling system and won't overheat doesn't hurt. Narrative work rarely requires AF lenses so AF simply isn't an issue. It also has all the cine cam features like LUT assist, vector scopes etc.
But for hybrid shooters, solo video shooters, vloggers, youtubers etc. AutoFocus is crucial, especially in FF which rules out the Pannys.
R5 vs A7S3. Tough call. On paper, R5 should destroy A7S3. It has 45MP, 8K, DCI 4K, Better IBIS, better ergonomics, internal RAW.
..but in the real world, all that means nothing if your camera can't operate because it overheated.
so by default, it would seem A7S3 wins. However if you're an outdoor shooter in warm weather, A7S3 may overheat even faster than R5. 
and when A7S3 overheats, it completely shuts off while it appears R5 allows you to switch to pixel-binned 4K.. but HQ recovery times are long.
A7S3 does appear to be the safer bet if you're hard pressed for an upgrade. But if you already have an A73, is 12MP non-oversampled 4K really worth the 4200€ investment? Maybe for the HFR & 10-bit. I'll let you be the judge. Personally I'm not rushing in to buy either, hate being a beta-tester to first gen e-products.