Querying compatible camera frame rates
26 views
Skip to first unread message
Armen Avetisyan
Apr 26, 2017, 7:56:11 PM4/26/17
to android-ndk
Hi there,
When querying camera metadata from my samsung s7 with the tag
and the command
then it will show me that frame rate that I can achieve can be quite high. Here is the logcat output:
Note the
Most of the entries are set with 34 or 35 MS/FRAME (I think the duration is in milliseconds). 34 milliseconds mean 30 FPS - I get that.
But 1 MS/FRAME means 1000 FPS - how can it be? I assume it means something like it is not capped but in practice barely feasible.
Anyone thoughts on this?
When querying camera metadata from my samsung s7 with the tag
ACAMERA_SCALER_AVAILABLE_MIN_FRAME_DURATIONS and the command
ACameraMetadata_getConstEntry()
then it will show me that frame rate that I can achieve can be quite high. Here is the logcat output:
...
04-26 16:57:23.040 11145 11168 I FetchingStuff: HEIGHT: 720
04-26 16:57:23.040 11145 11168 I FetchingStuff: MIN FRAME DURATION: 1
04-26 16:57:23.040 11145 11168 I FetchingStuff: WIDTH: 800
04-26 16:57:23.040 11145 11168 I FetchingStuff: HEIGHT: 450
04-26 16:57:23.040 11145 11168 I FetchingStuff: MIN FRAME DURATION: 1
04-26 16:57:23.040 11145 11168 I FetchingStuff: WIDTH: 720
04-26 16:57:23.040 11145 11168 I FetchingStuff: HEIGHT: 720
04-26 16:57:23.040 11145 11168 I FetchingStuff: MIN FRAME DURATION: 1
04-26 16:57:23.040 11145 11168 I FetchingStuff: WIDTH: 720
04-26 16:57:23.040 11145 11168 I FetchingStuff: HEIGHT: 480
04-26 16:57:23.040 11145 11168 I FetchingStuff: MIN FRAME DURATION: 1
04-26 16:57:23.041 11145 11168 I FetchingStuff: WIDTH: 640
04-26 16:57:23.041 11145 11168 I FetchingStuff: HEIGHT: 480
04-26 16:57:23.041 11145 11168 I FetchingStuff: MIN FRAME DURATION: 1
04-26 16:57:23.041 11145 11168 I FetchingStuff: WIDTH: 352
04-26 16:57:23.041 11145 11168 I FetchingStuff: HEIGHT: 288
04-26 16:57:23.041 11145 11168 I FetchingStuff: MIN FRAME DURATION: 1
04-26 16:57:23.041 11145 11168 I FetchingStuff: WIDTH: 320
04-26 16:57:23.041 11145 11168 I FetchingStuff: HEIGHT: 240
04-26 16:57:23.041 11145 11168 I FetchingStuff: MIN FRAME DURATION: 1
04-26 16:57:23.041 11145 11168 I FetchingStuff: WIDTH: 256
04-26 16:57:23.041 11145 11168 I FetchingStuff: HEIGHT: 144
04-26 16:57:23.041 11145 11168 I FetchingStuff: MIN FRAME DURATION: 1
04-26 16:57:23.041 11145 11168 I FetchingStuff: WIDTH: 176
04-26 16:57:23.041 11145 11168 I FetchingStuff: HEIGHT: 144
04-26 16:57:23.041 11145 11168 I FetchingStuff: MIN FRAME DURATION: 35
04-26 16:57:23.041 11145 11168 I FetchingStuff: WIDTH: 4032
04-26 16:57:23.041 11145 11168 I FetchingStuff: HEIGHT: 3024
04-26 16:57:23.041 11145 11168 I FetchingStuff: MIN FRAME DURATION: 35
04-26 16:57:23.041 11145 11168 I FetchingStuff: WIDTH: 4032
...
Note the
MIN FRAME DURATION: 1Most of the entries are set with 34 or 35 MS/FRAME (I think the duration is in milliseconds). 34 milliseconds mean 30 FPS - I get that.
But 1 MS/FRAME means 1000 FPS - how can it be? I assume it means something like it is not capped but in practice barely feasible.
Anyone thoughts on this?
Reply all
Reply to author
Forward
0 new messages