You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also I am interested in readout speed for a given CMOS sensor crop format (usually only vertical resolution affects that) - not just shutter speed - in a manner where global shutter can be a defined thing.
For shutter speed: yes I can convert mechanical shutter deg. to 1/XYZ sec. for electronic shutter) but why is the range upper limited. I realized timelapses etc are not the major concern here for this group but say a 2 sec exposure in such case etc is a thing.
Left undetermined at the moment is readout temporal offset from the time considered the start of the frame, whether that start time be a timecode or a PTP timestamp. If one assumes (not unreasonably for virtual production, not neck. the case for more general production) a constant frame rate, one could define in some normalized manner integration start time, integration completion time, readout start time, readout end time, charge clear start time and charge clear end time. Coupling PTP-synced cameras and LED walls with all that background info could of course make for some interesting possibilities.
The parameter shall be an integer in the range (0..360000].
Is this a typo - 360X100 = 36,000 - it says 0.01 as precision, is one suggested minimal precision and the other (10X that) the encodable precision
The text was updated successfully, but these errors were encountered: