You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are leveraging rtsp-simple-server to proxy USB and RPi camera streams to a RTSP h264 encoded stream. The latter can than be leveraged as a traditional IP camera stream, and connect with the Kerberos Agent. For more information have a look at the camera-to-rtsp repository.
For the moment, we cannot make this approach working in a balena deployment. We cannot have rtsp-simple-server connecting with both a RPI or USB camera.
We need some help tweaking the docker-compose.yml file, so we can properly setup the rtsp-simple-server and connect the RTSP urls to the Kerberos Agent.
The current situation is that the Kerberos Agent is properly deployed, and can be configured with an available RTSP stream, however we cannot leverage the RTSP stream from the rtsp-simple-server, as the onboard device is not recognised in the current configuration.
The text was updated successfully, but these errors were encountered:
We managed to get the USB camera working, after installing ffmpeg in a sub image of rtsp-simple-server. We now have a new issue where the stream reading is too slow, compared to the encoding speed (inside the container). #2
We are leveraging rtsp-simple-server to proxy USB and RPi camera streams to a RTSP h264 encoded stream. The latter can than be leveraged as a traditional IP camera stream, and connect with the Kerberos Agent. For more information have a look at the camera-to-rtsp repository.
For the moment, we cannot make this approach working in a balena deployment. We cannot have rtsp-simple-server connecting with both a RPI or USB camera.
We need some help tweaking the
docker-compose.yml
file, so we can properly setup the rtsp-simple-server and connect the RTSP urls to the Kerberos Agent.The current situation is that the Kerberos Agent is properly deployed, and can be configured with an available RTSP stream, however we cannot leverage the RTSP stream from the rtsp-simple-server, as the onboard device is not recognised in the current configuration.
The text was updated successfully, but these errors were encountered: