The question remains, why do you suppose they left oversampled 4K60 off (if not due to heat)?Well the R5II is a new camera body, it is expectable that not all possible video modes are implemented at the time of release.
By the way 4K60 is already implemented, 4K60 downsampled (= HQ) is not (yet) implemented.
As mentioned, I expect heat generation and therefore max. recording time somewhere between 8K30 and 8K60. Of course, the sensor has to capture 8K60, while downsampling to 4K60 is less computationally intensive than full processing of 8K60 (= 4x the data of 4K60), also writing to the card is only 1/4 for the same codec, consequently the card will most likely not overheat.
Note that with firmware 1.6.0 or later installed the R5 (Mark I) records 4K24 HQ longer than 8K24 (see //community.usa.canon.com/t5/EOS-DSLR-Mirrorless-Cameras/R5-firmware-1-6-Overheating-Fixed/m-p/380097):
Auto power off temp = Standard
4k HQ 23.98 warning @ 31m 02s, shutdown @ 40m 18s
8k IPB 23.98 warning @ 25m 50s, shutdown @ 33m 57s
Auto power off temp = High
4k HQ 23.98 ran for 3 hours, no warning or shutdown, gave up
8k IPB 23.98 ran for 4 hours plus, white warning after an hour or so, red warning intermittent, no shutdown
Maybe there were some issues other than heat with it at launch and they need additional time to work out the bugs?? Pure speculation.The question remains, why do you suppose they left oversampled 4K60 off (if not due to heat)?
Incidentally, setting single shooting disables pre-capture. Easily accessed with the Drive button on the top left.Makes sense, thanks!
Now if only ACR/Bridge had metadata indicating an image was part of a precapture. That would make culling that much easier.Incidentally, setting single shooting disables pre-capture. Easily accessed with the Drive button on the top left.
Reading your comment made me actually just think about the R1 for a moment as I now have one as well as an R3, as much as I love the R3 my god the r1 is a fantastic camera. All of the flagship cameras are great right now. But I gotta say in my own personal subjective experience after using all of them the R1 is really awesome. Sure people complain about megapixels, but I don’t.You need to upgrade your R5 II to an R1, where the diopter dial must be pulled out to unlock it. Unfortunately, that’s a somewhat costly firmware upgrade.
I would love the shutter angle too but 14 bit raw in this camera would be so much dataR1 misses shutter angle and 14 bit RAW for cinematography.
Reading your comment made me actually just think about the R1 for a moment as I now have one as well as an R3, as much as I love the R3 my god the r1 is a fantastic camera.
I would love the shutter angle too but 14 bit raw in this camera would be so much data
I was a little surprised that the color saturation and the way that the data was being rendered is a bit different. I actually think I like the video coming out of the R3 more than the R1 but for work no one will ever know or care. For most video stuff though I still use my C300mkiii and c70. Which all four of those cameras play very well together.Yeah...amazing.
And dramatic difference overall to R3. I remembered couch experts with "R3 mk2" comments and propaganda clowns complaining and laughed.
Tough to go back after that EVF.
Did you compare the colour, sharpness and Cinema RAW ? I found some things...differed.
So much data is already with 12 bit raw. : )
I don't care about that size difference with the advantage, if I'm burning GB every 5 sec I want full bit depth of the sensor and sensor can handle 40 fps in 14 bits.
This is why I actually really liked the previous implementation that stored pre-captures in folders on the camera. I would just extract the keepers in camera and never need to open DPP at all.Now if only ACR/Bridge had metadata indicating an image was part of a precapture. That would make culling that much easier.
You can achieve something similar by protecting the keepers and then mass erasing the burstThis is why I actually really liked the previous implementation that stored pre-captures in folders on the camera. I would just extract the keepers in camera and never need to open DPP at all.
A lot of times Canon announces big whites after CP+. For example, the Canon RF 100-300 mm f2.8 L was announced on April 20, 2023. If Canon does decide to announce the 200-500 mm this year I would expect it in the March-May timeframe.Was there any major firmware release this week at CP+ for bodies? I saw the lens updates related to R1/R5II but nothing related to updating the bodies itself. Also disappointed in the no show of the 200-500, now I'm wondering if it was scrapped. I remember it being said here that it was spotted in field test last year, then crickets. Wasn't there a recent patent discovery that mentioned a 300 - 600? Maybe that's the focus, no pun intended hahahaha