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 :)

EPIC News...

That's what I've been asking on page 10 of this thread!

This has been answered multiple times in multiple threads. The maximum frame rate is dependent on the vertical resolution (number of rows) that you are using, NOT the total number of pixels.

Since 16:9 is using more rows, it is going to have to read more of them which limits the fps.

In other words, clipping off the left and right side of the cropped image isn't buying you any speed in the sensor. It is however probably buying you space in your stream of data coming from the sensor which means smaller files.

Two different issues.
 
This has been answered multiple times in multiple threads. The maximum frame rate is dependent on the vertical resolution (number of rows) that you are using, NOT the total number of pixels.

Since 16:9 is using more rows, it is going to have to read more of them which limits the fps.

In other words, clipping off the left and right side of the cropped image isn't buying you any speed in the sensor. It is however probably buying you space in your stream of data coming from the sensor which means smaller files.

Two different issues.

I think it's very interesting that they're hitting the limits of the sensor read-reset before they hit limits of the brain's processing power. These things are freakin' POWERFUL.
 
Back
Top