Exposure info from camera snapshots?

1

105437

BIT Beta Team
Jun 8, 2015
2,147
1,046
I have several 5442 cameras and it would be nice if the exposure used when the snapshot was created could be included in the metadata of the jpg image file. Anyone ever tried to find a way to do this?
 
Does this reply with the info you're looking for?
Code: 
http://user:password@camera-IP/cgi-bin/configManager.cgi?action=getConfig&name=VideoInExposure
 
Last edited:
  • Like
Reactions: 105437 and looney2ns
Thanks for the reply... It returned a lot of settings but I don't see exposure, perhaps I'm looking right past it.

table.VideoInExposure[0][0].AntiFlicker=0
table.VideoInExposure[0][0].AutoGainMax=2
table.VideoInExposure[0][0].Backlight=0
table.VideoInExposure[0][0].BacklightRegion[0]=3096
table.VideoInExposure[0][0].BacklightRegion[1]=3096
table.VideoInExposure[0][0].BacklightRegion[2]=5096
table.VideoInExposure[0][0].BacklightRegion[3]=5096
table.VideoInExposure[0][0].Compensation=50
table.VideoInExposure[0][0].DoubleExposure=0
table.VideoInExposure[0][0].Gain=1
table.VideoInExposure[0][0].GainMax=40
table.VideoInExposure[0][0].GainMin=0
table.VideoInExposure[0][0].GlareInhibition=0
table.VideoInExposure[0][0].Iris=50
table.VideoInExposure[0][0].IrisAuto=true
table.VideoInExposure[0][0].IrisMax=50
table.VideoInExposure[0][0].IrisMin=0
table.VideoInExposure[0][0].Mode=0
table.VideoInExposure[0][0].RecoveryTime=900
table.VideoInExposure[0][0].Rect[0]=0
table.VideoInExposure[0][0].Rect[1]=0
table.VideoInExposure[0][0].Rect[2]=0
table.VideoInExposure[0][0].Rect[3]=0
table.VideoInExposure[0][0].SlowAutoExposure=0
table.VideoInExposure[0][0].SlowShutter=false
table.VideoInExposure[0][0].SlowSpeed=25
table.VideoInExposure[0][0].Value1=0
table.VideoInExposure[0][0].Value2=2
table.VideoInExposure[0][0].WideDynamicRange=50
table.VideoInExposure[0][0].WideDynamicRangeMode=0
table.VideoInExposure[0][1].AntiFlicker=0
table.VideoInExposure[0][1].AutoGainMax=2
table.VideoInExposure[0][1].Backlight=0
table.VideoInExposure[0][1].BacklightRegion[0]=3096
table.VideoInExposure[0][1].BacklightRegion[1]=3096
table.VideoInExposure[0][1].BacklightRegion[2]=5096
table.VideoInExposure[0][1].BacklightRegion[3]=5096
table.VideoInExposure[0][1].Compensation=60
table.VideoInExposure[0][1].DoubleExposure=0
table.VideoInExposure[0][1].Gain=1
table.VideoInExposure[0][1].GainMax=80
table.VideoInExposure[0][1].GainMin=0
table.VideoInExposure[0][1].GlareInhibition=0
table.VideoInExposure[0][1].Iris=50
table.VideoInExposure[0][1].IrisAuto=true
table.VideoInExposure[0][1].IrisMax=50
table.VideoInExposure[0][1].IrisMin=0
table.VideoInExposure[0][1].Mode=4
table.VideoInExposure[0][1].RecoveryTime=900
table.VideoInExposure[0][1].Rect[0]=0
table.VideoInExposure[0][1].Rect[1]=0
table.VideoInExposure[0][1].Rect[2]=0
table.VideoInExposure[0][1].Rect[3]=0
table.VideoInExposure[0][1].SlowAutoExposure=0
table.VideoInExposure[0][1].SlowShutter=false
table.VideoInExposure[0][1].SlowSpeed=25
table.VideoInExposure[0][1].Value1=0
table.VideoInExposure[0][1].Value2=10
table.VideoInExposure[0][1].WideDynamicRange=50
table.VideoInExposure[0][1].WideDynamicRangeMode=0
table.VideoInExposure[0][2].AntiFlicker=0
table.VideoInExposure[0][2].AutoGainMax=2
table.VideoInExposure[0][2].Backlight=0
table.VideoInExposure[0][2].BacklightRegion[0]=3096
table.VideoInExposure[0][2].BacklightRegion[1]=3096
table.VideoInExposure[0][2].BacklightRegion[2]=5096
table.VideoInExposure[0][2].BacklightRegion[3]=5096
table.VideoInExposure[0][2].Compensation=50
table.VideoInExposure[0][2].DoubleExposure=0
table.VideoInExposure[0][2].Gain=1
table.VideoInExposure[0][2].GainMax=50
table.VideoInExposure[0][2].GainMin=0
table.VideoInExposure[0][2].GlareInhibition=0
table.VideoInExposure[0][2].Iris=50
table.VideoInExposure[0][2].IrisAuto=true
table.VideoInExposure[0][2].IrisMax=50
table.VideoInExposure[0][2].IrisMin=0
table.VideoInExposure[0][2].Mode=8
table.VideoInExposure[0][2].RecoveryTime=900
table.VideoInExposure[0][2].Rect[0]=0
table.VideoInExposure[0][2].Rect[1]=0
table.VideoInExposure[0][2].Rect[2]=0
table.VideoInExposure[0][2].Rect[3]=0
table.VideoInExposure[0][2].SlowAutoExposure=0
table.VideoInExposure[0][2].SlowShutter=false
table.VideoInExposure[0][2].SlowSpeed=25
table.VideoInExposure[0][2].Value1=0
table.VideoInExposure[0][2].Value2=40
table.VideoInExposure[0][2].WideDynamicRange=50
table.VideoInExposure[0][2].WideDynamicRangeMode=0
 
  • Like
Reactions: looney2ns
Here's the API, attached. :cool:
 

Attachments

  • Like
Reactions: looney2ns and 105437
Yes, like the overall idea. It would be nice to be able to see what the exact parameters (settings) are when the camera takes a screen shot or for one frame of a video. If the exposure range is 0-8 was the exposure 1/10000, 1/500, 1/125 or something in between. Plus how much gain was used, etc.

However, did not see any indication of this type of video analysis available in the API. As indicated above, one can GET a set of parameters from the camera, but these are only a reflection of what was entered when setting up the camera. Or one can SET a camera parameter by using the API in place of using the GUI. It would appear that camera metadata is not available like it is for a Cannon or Nikon DLSR.
 
Last edited:
  • Like
Reactions: CanCuba
Alaska Country said:
Yes, like the overall idea. It would be nice to be able to see what the exact parameters (settings) are when the camera takes a screen shot or for one frame of a video. If the exposure range is 0-8 was the exposure 1/10000, 1/500, 1/125 or something in between. Plus how much gain was used, etc.

However, did not see any indication of this type of video analysis available in the API. As indicated above, one can GET a set of parameters from the camera, but these are only a reflection of what was entered when setting up the camera. Or one can SET a camera parameter by using the API in place of using the GUI. It would appear that camera metadata is not available like it is for a Cannon or Nikon DLSR.
Click to expand...

I second this. My pet peeve with Dahua is lack of a debug output. Why can't we see the shutter, gain, CPU/memory usage, etc as the camera is running? I think it would help dial in settings.
 
CanCuba said:
I second this. My pet peeve with Dahua is lack of a debug output. Why can't we see the shutter, gain, CPU/memory usage, etc as the camera is running? I think it would help dial in settings.
Click to expand...

So a few of my cheap cams have a system status screen, and they call it a CPU, so that is why I am calling it a CPU, but this shows this camera running at 8192 bitrate, H264, CBR, and 12 FPS is hitting the camera processor at 47% and jumps to 70% with motion. If I up the camera to 30 FPS, the usage is in the high 90% range, but then with motion, it maxes out and would get unstable.

Or if I keep it at 12 FPS and use the camera motion detection, the CPU in the camera goes to 60% idle.

This would be nice if all cams had this so we could see how our settings impact the performance of the camera. I think running these cams close to capacity is probably harder to overcome than a computer spike at 100% CPU. It would be nice is we knew if we were taxing the Dahua CPUs, but based on this, I try to run my cameras lean and not try to max out rated specs.

1673793771057.png
 
  • Like
Reactions: CanCuba
wittaj said:
So a few of my cheap cams have a system status screen, and they call it a CPU, so that is why I am calling it a CPU, but this shows this camera running at 8192 bitrate, H264, CBR, and 12 FPS is hitting the camera processor at 47% and jumps to 70% with motion. If I up the camera to 30 FPS, the usage is in the high 90% range, but then with motion, it maxes out and would get unstable.

Or if I keep it at 12 FPS and use the camera motion detection, the CPU in the camera goes to 60% idle.

This would be nice if all cams had this so we could see how our settings impact the performance of the camera. I think running these cams close to capacity is probably harder to overcome than a computer spike at 100% CPU. It would be nice is we knew if we were taxing the Dahua CPUs, but based on this, I try to run my cameras lean and not try to max out rated specs.

View attachment 150995
Click to expand...

Same. No higher than 15 FPS and an absolute minimum of BLC, WDR, etc.

I'd be more interested in seeing how the camera is setting the shutter and gain in the ranges I've set. This would make dialing in easier, especially for night recording.

But we can only dream as I don't see this happening.
 
You must log in or register to reply here.
Top Bottom