Without object detection enabled, the pipeline achieves 30 FPS. However, enabling object detection reduces the FPS to 15.
If sync=true is set:
The FPS drops to 2, with dropped frames = 14.
If sync=false is used:
The FPS is capped at 15, with dropped frames = 0, despite setting camera-fps=30.
Questions:
Why does enabling object detection result in reduced FPS, even when camera-fps=30 is specified? Is there a way to optimize this pipeline for higher FPS with object detection enabled, what have to do in order to get 30 ?
In your documentation, it is stated that camera-resolution=2 corresponds to HD720. However, during my testing, I achieved HD720 resolution with camera-resolution=3. Could you please clarify this discrepancy?
camera-resolution : Camera Resolution
flags: readable, writable
Enum “GstZedsrcResolution” Default: 7, “Default value for the camera model”
(1): HD2K (USB3) - 2208x1242
(3): HD1200 (GMSL2) - 1920x1200
(2): HD1080 (USB3/GMSL2) - 1920x1080
(4): HD720 (USB3) - 1280x720
(5): SVGA (GMSL2) - 960x600
(6): VGA (USB3) - 672x376
(7): Default value for the camera
*** also I want to ask u, because I’m new with zed gstreamer. Can I make the detection only for persons and ignore any other objects direct with gstreamer pipeline ?
[/quote]
Please add more information, a log, video. It’s not easy to solve this with no information.
[/quote]
Once I go to the office, I will provide u all info.
I have another question , when use th object detection, the depth mode must be neural ?