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
I would like to know if it would be possible to add UDP MPEG-TS output for the video/audio stream, which could be sent via TCP already.
I'm looking to reduce the overall load on the pi, by trying to get rid of all "publishing" services, like node-rtsp-rtmp and just sending the stream to another host, where it could be restreamed either viat rtsp or directly into webrtc like with https://github.com/aler9/mediamtx (previously known as rtsp-simple-server). unfortunately the mediamtx does not accept TCP MPEG-TS streams as it seems.
If there is any other option to reduce the load/keep up high framerates on a Pi3+ or PiZero and to publish the stream via rtsp, I'm also happy to hear about that.
The text was updated successfully, but these errors were encountered:
Actually, it is possible to use UDP with the --tcpout option. Sorry the option name is confusing.
For example: picam --tcpout udp://192.168.1.2:8181
There is a trade-off between frame rate and resolution. If you want to increase the frame rate, you have to decrease the width and height of the video.
Hi
I would like to know if it would be possible to add UDP MPEG-TS output for the video/audio stream, which could be sent via TCP already.
I'm looking to reduce the overall load on the pi, by trying to get rid of all "publishing" services, like node-rtsp-rtmp and just sending the stream to another host, where it could be restreamed either viat rtsp or directly into webrtc like with https://github.com/aler9/mediamtx (previously known as rtsp-simple-server). unfortunately the mediamtx does not accept TCP MPEG-TS streams as it seems.
If there is any other option to reduce the load/keep up high framerates on a Pi3+ or PiZero and to publish the stream via rtsp, I'm also happy to hear about that.
The text was updated successfully, but these errors were encountered: