-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pylonsrc for deepstream on Jetson: high latency on high fps #79
Comments
Hi @pabsan-0, have you tried using the plug-in with deepstream yet? I can get it to work with GStreamer but deepstream cannot build pylonsrc |
@ghazalehtrb Hey, yeah I've been using it. This issue has been my only trouble regarding pylonsrc+deepstream, for now I'm simply setting a lower framerate and avoiding the high-latency scenario altogether. Could you give me more details about your issue, perhaps some sample pipelines? Also I do not fully understand the "deepstream cannot build pylonsrc" part, so details on your setup (jetson, docker, newly-set env variables...) would also be helpful. |
@pabsan-0 could share the script regarding how the above mentioned pipeline works for deepstream ?I am not able to run it with deepstream. |
@jetsonnx2107 I run those pipelines as is in a bash terminal. Mind that there are no spaces after the Else show me your output and I'll try to help from there :) |
Hello! I'm trying to get a real-time object detection inference pipeline on a Jetson Xavier NX using a Basler camera through
pylonsrc
, using the inference pipeline show below. However, I'm experiencing significant latency at higher fps requests.My idea is to retrieve images at high fps from the camera and leave the speed bottleneck to lay somewhere else in the pipeline (I do not have a final target fps). I'm using two reference framerates for comparison:
pylonsrc config-file=* fps=20
, yields ~20 fps as expected, low latency (almost negligible).pylonsrc config-file=* fps=90
, yields ~30 fps as expected, very high latency (about ~2 sec).After some testing I've seen that the autovideosink pipeline (also shown below) runs on almost zero latency without regard to the
pylonsrc
fps, so my guess lies that the delay has to do with computer resources.Any suggestion to keep an "uncapped" framerate in the Basler without increasing latency by modifying the pipeline/config-file?
Inference pipeline
Autovideosink pipeline
Basler configuration file
Basler.pfs
The text was updated successfully, but these errors were encountered: