Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Pro Res?

Don't get too excited Terry... No it is not... I am pretty sure Antony just made it up.


Hmmm.. I guess I can infer from this that read-resets can overlap and so frame rates are not limited as indicated in Antony's post? Sometimes I can't tell if you are just yanking my chain, Jarred. LOL

On a side note, read-reset action is something I always had a hard time visualizing for some reason. I gives my feeble imagination can't work in milliseconds. :smiley: That's why I am sort of obsessed with understanding i
 
Terry,

My (possibly incorrect!) understanding is as follows:

<Read-reset>
+) Is the minimum time for the sensors data to be completely read, and primed (reset) for the next read.

<Dragon>
+) The data from the sensor is read line by line - and there is a maximum rate.
+) The top line is read first ... and about 0.0025 secs (2.5ms) the bottom line is read (for a 6k FF)
+) At 6k - the resolution is 6144 x 3160 lines.
+) This means that it takes the 2.5ms / 3160 for the current Dragon circuitry to read 1 x line.
+) When screen resolutions have less lines in them -> it takes less time to read all the lines.

<Read process at 24 frames per second, with Shutter 'open' for 1/2 the time = 180 degrees>
+) Sensor is exposed to light for 1/48 of a second.
+) Sensor is read as fast as possible in the first 2.5ms (or less) of the next 1/48 second.
+) Total of the 2 above twi lines = 1/24th of a second (hence 24 fps)

<one line or two lines at the same time?>
+) If the Dragon could read more then 1 line at the same time ... then Red would already be doing this so as to minimise the time it takes to read all the lines on the sensor.
+) This means that the upper limit of the frame rate is determined by how many read-reset cycles can be competed.
+) 1000 ms (1 sec) / 2.5 ms = 400 frames in one second. (with No gaps)
+) 1000 ms (1 sec) / (5 ms) = 200 frames in one second. (with the sensor is only exposed for half of each frame =180deg)

AJ
 
Last edited:
Back
Top