Messages

Raw data is raw data. There's no "log" in raw. I think you have a reading to do. As Danne said, you can use 12-14bit if you need more dynamic range.

raw data is also numbers array in memory (a kind of voltage value? ), number can of course be remapped by a non-linear function curve (such as log), just value modification, nothing else.
A log profiled data does not need special data or treatment, only the remapped value taking place of the original one, same size and structure as the original, the only thing need to do is to let the cpu remap the value when down sampling to 10 bit, it is a kind of tiny calculation, i wish cpu can afford it, although, it can already do the down sampling calculation, right?
Anyway, thanks to all the contributors

What is you point? 10bit is a compromise to get continuous recordings. If 12bit or 14bit works use that but we are talking eos m here. Not the most obvious cpu powerhorse 

thank you for your great job, first! i am using your build.
i mean current 10bit raw is linear, right? if it is log profied, it will be almost perfect, just within the progress down sampling to 10bit, i don't know whether the cpu can afford it (i use eosm too) , just a suggestion

10bit raw is a great solution, but there is a problem, 10bit is linear right? so it does not contain enough data for mid tone and shadow area, worse than 10bit log (not raw file), i think it should be recorded in log profile, not in post-production in MLVApp (data has already lost at that time), it should be done within the progress something like cmos data to 10 bit.
i think 10bit log profiled raw is the perfect solution, it can replace 14bit linear raw in most cases, 10bit linear raw has a obvious gap to 14bit linear, especially when grading mid tone an dark area, mid tone is so important!