Please provide complete information as applicable to your setup.
• GPU) • v5 • 440.64.00
Thanks for supporting this community with Deepstream SDK , it really makes things smooth . Also thanks to contributors for making it available to others.
I am trying to process real time feed from RTSP ip camera at 25FPS , when I use gst-dsexample to save detected object into my disk , I tend to get blurred image most of the times. To my surprise when I play 25 FPS images are very sharp. Wanted to understand what could be wrong here.
Captured using gst-dsexample
Captured directly from camera
These are my source and sink settings if it helps :
[source1]
enable=1
#Type - 1=CameraV4L2 2=URI 3=MultiURI 4=RTSP
type=4
latency=500
uri=rtsp://admin:@192.168.1.12:554/mode=real&idc=1&ids=1
num-sources=1
#drop-frame-interval=2
camera-id=1
gpu-id=0
# (0): memtype_device - Memory type Device
# (1): memtype_pinned - Memory type Host Pinned
# (2): memtype_unified - Memory type Unified
cudadec-memtype=0
[sink1]
enable=1
#Type - 1=FakeSink 2=EglSink 3=File
type=0
sync=1
qos=0
source-id=1
gpu-id=0
nvbuf-memory-type=0
[streammux]
gpu-id=0
##Boolean property to inform muxer that sources are live
live-source=1
batch-size=8
##time out in usec, to wait after the first buffer is available
##to push the batch even if the complete batch is not formed
batched-push-timeout=40000
## Set muxer output width and height
width=1920
height=1080
##Enable to maintain aspect ratio wrt source, and allow black borders, works
##along with width, height properties
enable-padding=0
nvbuf-memory-type=0
I just remember when I was toying with the dsexample code for my own purposes (motion detection) that it scales the frame when creating the cv::Mat and in some circumstances calls guassian blur.
Check the source for the detail - its only a small file. ;-)
Yes already checked that file cant find anything related to guassian blur , also scale is set to 1 so there is no scaling issue either. Let me go line by line and try to figure this out , thank you for your response
Hopefully someone from nvidia can take a look as I’ve run out of ideas… Last thing would be to test your config with full_frame=1 and see what happens. When full-frame is 0 I thought it just cropped out the image inside the bounding box.
A few months back when DS5.0dp first came out I was creating a motion detection using dsexample as a base and when I dumped images to full they were full resolutions so I’m not sure whats wrong with your test.
Hopefully someone from nvidia can take a look for you…
Turns out saving entire frame and then cropping is bad for run time and performance especially when you have 10 streams running in parallel , although I tried that one and still poor results