Quote from: gabriielangel on March 20, 2024, 08:04:37 PMRaw video needs to be turned off,
It's a memory problem, RAW video (mlv_lite) allocate all available memory when it's active, iirc this break screenshots, this issue does exist in official builds, see:
Quote from: ArcziPL on March 06, 2019, 10:24:51 AMBTW: no in-cam screenshots for the last case, as trying to take them in movie mode results in a memory error. Just checked on 700D and it's same.
Quote from: a1ex on March 06, 2019, 10:48:59 AMWith mlv_lite's RAW Video enabled, the entire memory is preallocated during stanby. I'm seriously thinking to revert this change, just haven't managed to code anything in this direction. Been focusing on new ports + QEMU lately (as my main camera is defective anyway).
There are many side effects because of mlv_lite and when "the entire memory is preallocated during stanby", broken screenshots is one of them.
Edit:
Quote from: gabriielangel on March 20, 2024, 08:04:37 PMRaw video needs to be turned off, so False colors and other overlays are not recorded.
I think you are refering to x5 mode, because in x5 mode, ML global draw won't be active only in one case, when RAW video is turned on (it works like this by ML design). In normal Canon video modes like 1080p and 720p, ML global draw will be active with or without RAW video.
When crop mood is active, all presets will use x5 mode and patch x5 mode to the selected preset.
So the main issue here is memory allocation actually, fixing it will make you take screenshot when RAW video is enabled.