I think it's more been that they've been limited by processing power, since processing only cares about total MP count and not density, than not wanting high MP on FF, I think. 18MP on APS-C or FF requires the same processing power. But 48MP on FF takes a LOT more processing power than 18MP on APS-C (48MP is 18MP APS-C density scaled to FF).
nuther related note, I think processing requirements go up somewhat if people also select in-camera hi-iso NR. Sure can slow down the shooting speed if I accidentally turn that on... clogs the buffer faster anyway. I reduce in-camera overhead with all processing off, raw only, no jpgs either... unless I need really long bursts at full speed then raw gets turned off and jpg compression to minimum.
if sensor density goes up, not only does the size of the data array increase but the required noise reduction processing going on, even for the raw files, will add a bit more overhead compared to a larger pixeled (lower noise) sensor. Yet another reason to wish for less sensor noise at all sensitivities.
couldn't agree more, I have absolutely no interest in any in camera processing It would be nice to have 1 option
- Disable all in camera processing so you dont have to individually hunt down and turn off all the rubbish thats on by default.
- all this in camera lens correction blah blah blah just slows it all down more and produces substandard results
an in camera processor is never going to have a hope of competing against proper desktop editing and thats just from a pure processing power available standpoint.
I could be wrong but i'm fairly sure in camera processor are still essentially running on old DOS system architecture.