seydx
seydx
Quick (simplified) info on what the difference is to the recently implemented preload option. With preload, a constant connection to the camera is always maintained. This already significantly reduces the...
> In some formats, go2rtc begins transmission with an I-frame. This is mandatory for MSE/MP4. True, but the main problem is still that we need to wait for the I-frame...
Added a new function to automatically update the fmtp line with correct parameter sets... fixes: https://github.com/AlexxIT/go2rtc/issues/1634
https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#go2rtc-dev-version
> I have a fix. But I need to wait for [@seydx](https://github.com/seydx) to see if it works with broken TP-Link cameras. Unfortunately, I can no longer reproduce the "malformed response"...
@adriancable ```yaml streams: my_camera: - rtsp://127.0.0.1:1234/stream - ffmpeg:my_camera#audio=opus ```
This happens because go2rtc triggers a reconnect. When the second consumer wants different tracks than already established ones, go2rtc reconnects and this usually causes FFmpeg to throw errors like bad...
Oh, one more thing: if the second consumer also wants the backchannel, this will trigger a reconnect. go2rtc currently offers NO way for two or more consumers to share the...
hm it seems you have a video filter in your ffmpeg config? can you show me your config.yaml
can you try without `backchannel=1`