For processing, yes, for storage, no. Have a look at MDAT and CMP1 at https://github.com/lclevy/canon_cr3There's too many assumptions
But if they're all true, then again, raw file bitness refers to the content not to the container. There are container types used in CPUs but there's nothing really that's 16 bits in the CR3 files that would refer to pixels. When processing pixel raw data, the software would actually use 16 or 32 bit integer types or 32-bit float type.
The header fields do imply that CR3 files can allow arbitrary bit depths, so it shouldn’t need changes for 16 bit pixel data.
Upvote
0