>>3713283>Not true. Canon sensors fare really well at video. It is true. Readout speed does not impede other aspects of video (bit depth, DR, bit rate) but it absolutely affects whether or not you can do full sensor width 4k. (FHD you just line skip.)
>Hacked original Eos M can do 4k raw with little problems, and it's old as fuck. I have an original M with the latest ML build...which was literally released and featured on Zeek's YT channel days ago...and the best you can do at 24p is 2.7k in a 2.35:1 ratio. And that's with a heavy >3x crop. You can stretch to 2.8k if you're OK with only a few seconds of filming. There are no 24p 4k modes and certainly no 24p 4k full sensor width modes. This release is an improvement over previously releases limited to 2.5k24.
>5d's were very easy to modify, and were extensively hacked for better video modes. They were go to cams for budget video. I believe the 5D3 with ML has a 4k24 mode but...again...with a heavy crop. That means the DIGIC processor can handle the data stream but the sensor does not have the readout speeds to support a FF read at 24p.
>Lately the policy was changed. First they locked firmwares further to prevent tampering, Have they? Last I checked the only camera the ML team is forbidden from tampering with is the 1D line (1DC and 1DX).
>then they started to gimp their cams feature wise.The R5 and R6 are not gimped feature wise. Hell, the R isn't gimped aside from the crop which would appear to be a technical limitation.
Either Canon shipped shitty firmware or Canon was trying to quietly limit the cameras. I contend the latter does not make sense when you can attach a Ninja V and bypass the limit. It also really doesn't make sense for the R6 which would not compete with cine cameras but would be a hit for amateur cinematographers absent the heating.
Let's see if they release fixed firmware.
