Replies: 1 comment 1 reply
-
Sorry but what you provided makes impossible to replicate the issue. You provided logs of anything except for the only thing you needed to, which is MediaMTX, which contains clear indications on how the stream is encoded. If you still have issues, open a bug report (not a discussion) and provide relevant data and ways to replicate. If you think this is the same as #4879, provide information there. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Question
I ran into an issue trying to set up mediamtx on a Raspberry Pi 3B+ with a Camera Module 3 to serve an RTSP stream to feed to an instance of go2rtc (via Frigate) hosted on another server (on the same LAN).
What Works
Frigate reading mediamtx's RTSP stream directly; i.e., with the following config:
Reading the mediamtx RTSP stream with ffplay (though with ~8s startup latency)
Re-streaming RTSP streams from another IP camera in go2rtc. (The only other IP camera I have to test is an Android phone running the IP Webcam app.)
What Doesn't Work
Reading the mediamtx RTSP stream in go2rtc. I first encountered this issue from the embedded go2rtc process inside the Frigate container, but am seeing the same results with go2rtc running on my development machine.
mediamtx YAML config
DEBUG log output of mediamtx
go2rtc YAML config
Trace log output of go2rtc
Setup
mediamtx server: Raspberry Pi 3B+ running dietpi
mediamtx version: 1.14.0
Thanks in advance for your time and help.
Beta Was this translation helpful? Give feedback.
All reactions