Ziffl3 wrote:
While the lines between hardware /software can blur, you still need to have a solid hardware baseline married with a software architecture that is flexible.
While I see your point ... You forget that Canon is squarely a Japanese company. The engineering staff wants to deliver more but is handcuffed by marketing and a very conservative approach.
I don't really agree with this, it sounds nice on paper but the real world isn't that perfect. A lot of hardware out there isn't as solid as people would like to think it is, it's poorly designed, halfway complete, or just downright broken altogether. Things are designed in pieces, so a 'nice to have' feature might make it into only some pieces of hardware but not others. And hence it becomes the software team's job to work with hardware in this state as best as they can -- to make something that at least minimally works or does the job it needs to do. Since they can't just kick a project back for another hardware redesign or revision without a lot of resistance -- especially as the product gets closer to its planned release.
I'm not saying this is black and white -- of course if some core feature or vital function of the product simply can't work with the hardware in the state it is, they might have no choice but to fix the hardware (and likely cause a delay in the release of the product). My point is just in the process of designing one piece of hardware to another and then the software, it would often seem haphazard, inefficient, and maybe even nonsensical and wasteful to an outside observer. A lot of nonvital functions and features can fall by the wayside and this "dual ISO" mode of operation was likely one of them.
It would be nice to see this feature implemented "the way it ought to be", by Canon, in the official firmware (whether the hardware is perfect or not). Especially if it could be scalable to the point where it could work in multiple modes of trading off resolution for DR.