Closed fgadaleta closed 2 years ago
Could you show me your OBS configuration GUI? I guess that your pushing configuration for RTMP app name and stream name are not "live" and "test"??
they seem to be
In OBS I set the server as rtmp://127.0.0.1:1935/live/test
with an empty Stream key
The server should be rtmp://127.0.0.1:1935/live and the stream key should be configured as test
ok it works now thanks! Just with a delay of ~5 secs (both OBS and the server are running locally)
Both compiled debug
and release
(still the 5 sec lag)
The latency is related to the push client GOP size and the play client buffer size.
The latency is related to the push client GOP size and the play client buffer size.
I have OBS set as low-latency encoder settings (3000kbs) and I am playing with
ffplay -i http://localhost:8081/live/test.flv
What about your rtmp stream latency?try to add the “-fflags nobuffer” parameter for ffplay
What's about your rtmp stream latency?try to add the “-fflags nobuffer” parameter for ffplay
even worse
Did the ffplay print errors or warnings?
Actually yes I get this in red
[h264 @ 0x7f806899e3c0] co located POCs unavailable
[h264 @ 0x7f8068b68380] co located POCs unavailable
Now the default RTMP implemantation will cache 1 GOP which may increase the latency. I will do some improvements in the future to add this as a configuration.Then you can control to open the cache or not yourself.
That would be a great fix indeed
Thank you
In my scenario OBS is streaming to
rtmp://127.0.0.1:1935/live/test
And connection is correctly establishedMy
config.toml
is simplyBut when I play the stream with any of the two below
I get 2 errors. One server side
and one client side