Magic Lantern are a werid creature to digest. On one hand they are not part of te official Canon team. On the other, they realese incredible features for Canon touching an all aspects of the camera, from RAW video to (the dynamic range enhancing) dual ISO.
Their latest announcement revels a great feature call ML ISO, as opposed to “Canon ISO”. (The develpment name is a boring four letters acronym: ADTG)
The method involves quite a bit of tech, which I dont full understand, but it involves changing the way the sensor is being amplified. Tests done by Canon Rumors member Marsu42 show improvment of 1/3 to 1/2 a stop of dynamic range depending on the used ISO.
This is not a lot comparing to Dual ISO, but it also does not change any of the camera image processing algorithm. According to Marshu,
This means that for example on 5d3, iso 800 with ML has more dynamic range than iso 100 with Canon :-> … and at high iso you’re getting 7% more dr which is nothing to sneeze at, esp. since it builds upon Canon‘s advantage vs. Nikon: [email protected] = ~8.3 & [email protected] = ~9.4 ev. According to sensorgen.info the 6d should add another 2/3 stop (once the code is adapted for it) making good ol’ Canon the superior sensor for low light high contrast shooting.
While the curent tests only performed on the 5DmkII,5DmkIII and 50D, some graphs on the ML forumes suggest that this feature will be availabe for almost all Canon bodies. ML updated that this tweal is confirmed for 5D3, 550D, 600D, 650D, 700D, 60D, 6D, 5D2, 50D and 500D.
To make these news even better it seems that using ML iso will require nothing more than turning it on. (And slightly compensating for the reduced highlights). Here are two of the graphs that show the testing resuts on ML ISO for the 5Dmk3 and 50D:
This question posted on the original ML message was interesting to read:
Does this mean Canon did not fully optimize their sensor for low noise?
I’d say they simply left a safety margin in their code to make sure the ADC is always saturated (that is, to make sure white is always recorded as white).
The usual disclaimer for early ML builds apply – use at your own risk.