![\"SignalSaturationLimit\"](\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2015\/05\/SignalSaturationLimit-1024x833.png\")
<\/a><\/p>\n<\/p>\n
The ideas are as follows.<\/p>\n
Record time for saturation<\/h3>\n
Imaging if each sub pixel could EITHER register the number n<\/em> of incoming photons during the shutter time T<\/em> OR<\/strong> the time t<\/em> it took to reach the saturation N<\/em>, and could signal either\u00a0n<\/em> or t<\/em> back with a flag for which it is.<\/p>\n That way all non saturated cells would have an n<\/em>\u2264N<\/em> as usual, but for all over saturated, we calculate<\/span>\u00a0n<\/em> = N<\/em> \u00d7 T<\/em>\/t<\/em> , note\u00a0N<\/em> < n<\/em> since t<\/em><T<\/em><\/p>\n This should be great for HDR, or post adjusting the levels.<\/p>\n I imaging something like this: For a shutter time T<\/em> an easily invertible signal \u0192(t<\/em>)\u00a0 is supplied to all subpixels. Each subpixels have electronics that detects overrun (transistor?), and a way to store the height of\u00a0\u0192 (micro capacitor?) when this happens. A readout should then consist of either of the two, and a flag of which it is. For the calculated n<\/em> = N<\/em> \u00d7 T<\/em>\/\u0192-1<\/sup>(\u0192(t<\/em>))<\/p>\n A simple choice could be \u0192(t<\/em>) =K \u00d7 t<\/em>\/T and thus\u00a0 n<\/em> = N<\/em> \u00d7 K \/\u0192<\/p>\n Of course this would be more complex -and thus more expensive- than a traditional sensor, but if it could be done, we would get WAY more dynamic range, without any reduction in the quality of the signal for what is still below the saturation limit. There are no more noise introduced, as the normal signal is unchanged<\/p>\n Sure there is a limit on this as well, depending on the granulation\/accuracy of the \u0192(t<\/em>). If this is close to zero, or if discrete a few step-sizes, the calculation will be inaccurate – but still way better than current unknown level where we have no idea where between N<\/em> and \u221e the output should have been.<\/p>\n If even more dynamic range than the linear function offers is wanted, another \u0192(t<\/em>) could be used. If it grows quickly, the risk of division by a small integer or inaccurate value is reduced.<\/p>\n E.g. a scaled (square) root function could be used. \u0192(t<\/em>) =K \u00d7 \u03b1<\/sup>\u221a(t<\/em>\/T) , n<\/em> = N<\/em> \u00d7 (K\/\u0192)\u03b1<\/sup> – But I believe that would be overkill.<\/p>\n <\/p>\n Why not replace the standard passing<\/em> R, G, G, B filters, with filters blocking<\/em> R, G, B and InfraRed (Ir)?<\/p>\n So the recorded signal would be: (IrGB, IrRB, IrRG, RGB)<\/p>\n The sum of this will be 3 x IrRGB. Subtracting each from a third of this gives\u00a0 (R, G, B, Ir).<\/p>\n (The number that should be used is most likely a tad over 3 due to non-sharp filters, but that is a calibration issue – though poor filters would reduce the SNR)<\/p>\n The same interpolation patters using 4 cells as usual Bayer could be used<\/p>\nDifferent Bayer filter<\/h3>\n
![\"PixelGrid_CMYW\"](\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2015\/05\/PixelGrid_CMYW-300x181.png\"){kind=tracking}
<\/a><\/p>\n![\"PixelGrid_CMYW_45\"](\"https:\/\/eskerahn.dk\/wp-content\/uploads\/2015\/05\/PixelGrid_CMYW_45-300x204.png\"){kind=tracking}
<\/a><\/p>\n