Quote:
Originally Posted by cornelious2
all I need to say is A.) you obviously don't have the ability to read at a comprehension level above the 2nd grade. YES the processing happens after the sensor because it has to. think of the data like water draining out of a sink a blockage in the pipe can make the water exit the sink slower regardless as to how much or little water you spray into it.
and B.) just drop it as much as you don't want to admit it you are wrong. Just stop arguing with everyone and drop it.
|
Sorry, you're just plain wrong and these drivers fix nothing about the camera's exposuring whatsoever, nor would they. Digital camera sensors like the one in our phones utilize electronic shutters to control exposuring and light collection. CMOS sensors control exposure precisely by pushing data from the light-collecting pixels into the readout pipeline, when this happens, the exposure time is effectively over. Now, there is a native maximum speed of this readout for the sensor. That could possibly be an issue with our cameras, HOWEVER this is a property of the hardware itself and would not be affected by a Direct3D driver. (EDIT: I am actually now thinking the hardware read speed limit very well could be a significant issue, but there is no way to fix that short of replacing the sensor with a better one. If we could find the sensor specifications, we'd know for sure.).
There is no conceivable way the Direct3D driver could affect the exposure time of the camera.