|Camera Model||D435 / D455 / T265|
|Operating System & Version||Ubuntu 18.04|
|Kernel Version (Linux Only)||4.9.201-tegra|
I have a system where I have three shared objects loaded dynamically at run time. One is handling all of our realsense interaction, one is an RTSP gstreamer server and the other is an RTSP gstreamer client (on the same device).
The reason for the keep alive client is that when the gstreamer server goes from 1 or more clients to no clients there was a 10 second reset period that would cause re-connection errors. Our solution to this problem was a on-device keep-alive client that would connect via loop back to the server such that there would always be 1 or more clients. This keep-alive client would just sink to a “
fakesink” and not make use of the incoming video stream data.
For the longest time, using different combinations of SDK versions and D435/D455 firmware versions, we have been getting these UVC errors off and on when setting up the RGB stream OR depth stream on the D4XX cameras.
We have recently come to find that when we disable this keep alive gstreamer module we do not have any UVC errors from librealsense.
So my question is: Does anyone know how a gstreamer RTSP “
fakesink” client could cause UVC errors in the realsense side of things?