[Camera Support]: Dahua DH-IPC-HDW2531EMP-AS-S2 autotracking #15166
Unanswered
therokh
asked this question in
Camera Support
Replies: 7 comments 17 replies
-
|
Calibration is designed to help with scenarios like this, so you should definitely be running with The amount of time it takes to zoom is not part of this calculation though, which is a little problematic in your case because your initial zoom takes a fair amount of time. There are a few things you can do to help this. You'll want to set up Frigate to track a person and have autotracking lock on to it sooner. This could mean things like moving your zone to trigger autotracking closer to the edge of the frame or changing your As for objects close to the camera, there's really not a lot that can be done to improve it because an object is moving very quickly across the frame relative to an object that is further away. There is too much lag when sending ONVIF movement commands to the camera. This is why Frigate's autotracking will never be able to perform well for objects close to the frame like autotracking implemented in a camera's firmware. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I should also note that relative zooming has moved the pan/tilt and zoom motor together on the PTZs I have tested as I was writing the autotracking code. In your example, it does look like the firmware is moving them individually. The ONVIF standard sets no condition that they must move simultaneously, so I suppose this is just firmware-specific. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
As far as the Those bogus values will almost certainly cause issues when autotracking, so I'd uncomment the 2nd or 3rd one and go with that. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hey thanks for getting back so quickly. I've re-calibrated and have this now: My zoning setup for the camera is currently this: Here's a clip of the close up movement before adding the weights. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Motion masks on a PTZ are not ideal because the frame changes when the camera moves. If an object you're tracking ends up in a motion masked area, this may negatively affect Frigate's ability to continue tracking it. On my PTZ, the only thing I have masked is the timestamp. Your masks are not too close to the center of the frame, though - so you may be okay. Hard to know without watching debug view while it's actively autotracking. Calibration should certainly help with objects in the footpath zone. |
Beta Was this translation helpful? Give feedback.
-
|
There's a bit of weirdness still with some of the movements. Not sure why it swung down to the car. Is there any option to include the debug bounding boxes in a recording? front.mp4 |
Beta Was this translation helpful? Give feedback.
16 replies
-
|
Got some debug logs from an event. output3.mp4 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. What are your |
Beta Was this translation helpful? Give feedback.
-
|
Using this config, I wanted to test zooming again and recalibrated this morning: |
Beta Was this translation helpful? Give feedback.
-
|
And another with debug view: Screencast_20241204_111254.mp4
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks. Here's the portion of the log indicating where your issue lies. The way Frigate works in this situation is that when an object is moving and you have Right now, your movement weights are as such that Frigate thinks the camera is going to take about 40.1 seconds to move to its predicted location. That's why the predicted box is a nonsensical value. Calibration simply moves the camera to various locations and measures the time it takes for those movements. If the camera doesn't respond in a timely fashion, those values can be drastically skewed. Of course this is what we saw in your original config. There could be a few reasons for this, including something in the firmware, network traffic, high system activity, etc. For comparison, the 3rd and 4th values for my camera are between 1 and 2. Yours seem to vary greatly. If you comment out your |
Beta Was this translation helpful? Give feedback.
-
|
How did you figure out how to
|
Beta Was this translation helpful? Give feedback.
0 replies
-
This can be done by using some screen capture software.
Create a fake camera and provide a video clip as an input. See the docs for an example: https://docs.frigate.video/development/contributing/#2-modify-your-local-config-file-for-testing |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem you are having
Hi, I have a Dahua DH-IPC-HDW2531EMP-AS-S2 PTZ camera and have a mostly working autotracking setup. I have noticed though that often the tracker will detect a person, pan/tilt and then zoom to them and in the time it takes to zoom, the person moves out of frame and the tracker loses them. I have relative zooming enabled but it seems like it's doing a separate zoom movement. I've tried changing the zoom_factor and can't say that it made a noticeable difference. The video attached shows the behaviour.
The other issue is that the tracker often over-corrects on close objects and moves them out of frame, and then loses them. I've tried with and without movement weights and I can't say I've noticed it being any better. This happens mostly with people walking by a path at the bottom of frame, which is probably 5m away from the camera.
Version
0.15.0-33825f6
What browser(s) are you using?
No response
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
No response
Operating system
Other Linux
Install method
Docker Compose
Object Detector
OpenVino
Network connection
Wired
Camera make and model
Dahua DH-IPC-HDW2531EMP-AS-S2
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
front_ptz_r367gy.mp4
Beta Was this translation helpful? Give feedback.
All reactions