Please provide complete information as applicable to your setup.
• Hardware Platform (Jetson / GPU) GPU • DeepStream Version 6.4 • JetPack Version (valid for Jetson only) • TensorRT Version 8.6.1 • NVIDIA GPU Driver Version (valid for GPU only) 535 • Issue Type( questions, new requirements, bugs) Bug • How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing) deepstream_testsr sample app with bbox enabled • Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)
What happens is, when we use the smart record bin at the sink end of the pipeline, after the encoder, the resulting video is glitchy with randomly occurring gray/green dots. Interestingly enough, the first video is always fine, but from the second video on, this corrupted video starts to occur. The problem is probably not in the smart record, when it’s used before the decoder at the beginning of the pipeline, videos are all fine.
Another observation is, iframeinterval config for the encoder changes the result. With bigger values, the size of the gray dots and glitches are worse. Making it 1 eliminates these gray dots, but it’s not a good idea and reduces the overall video quality.
This was not happening in deepstream 6.1. What could be the problem here?
Thank you for the reply. Just run the sample app deepstream_testsr with bbox enabled. It should be something like this: ./deepstream-testsr-app rtsp:/source_url --sink-type=1 --bbox-enable=1
This test confirmed that the problem was not related to the encoder. As you said before, when add that before the decoder plugin, it works normally.
So you can do the following comparison test to remove some of the plugins to see if there are problems, like nvdsosd, etc…
No. That topic will cause the whole picture to be green screen. As you said, it’s just glitchy with randomly occurring gray/green dots. I don’t see any obvious problems on my side, can you narrow it down yourself to see which plugin might have problems? You can also attach the video generated.
I’ll get back to you with several tests on plugins to narrow it down. In the meantime, can I get your opinion on how iframeinterval config changes the behaviour, if it’s not related to the encoder plugin at all? What is your guess?
From this parameter alone, I initially guessed that it was related to the encoder. But as you said, after changing the enc_type, the result is still the same. This is a little weird. Can you double check that the result is the same after changing the enc_type?
There is no update from you for a period, assuming this is not an issue anymore. Hence we are closing this topic. If need further support, please open a new one. Thanks