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
SRS responsed the onStatus(NetStream.Publish.Start) message before close the TCP connection when hooks failed, which cause the OBS reconnecting again and again.
…6.0.123 (#4038)
Fix#4037 SRS should not send the publish start message
`onStatus(NetStream.Publish.Start)` if hooks fail, which causes OBS to
repeatedly reconnect.
Note that this fix does not send an RTMP error message when publishing
fails, because neither OBS nor FFmpeg process this specific error
message; they only display a general error.
Apart from the order of messages, nothing else has been changed.
Previously, we sent the publish start message
`onStatus(NetStream.Publish.Start)` before the HTTP hook `on_publish`;
now, we have modified it to send this message after the HTTP hook.
…4038)
Fix#4037 SRS should not send the publish start message
`onStatus(NetStream.Publish.Start)` if hooks fail, which causes OBS to
repeatedly reconnect.
Note that this fix does not send an RTMP error message when publishing
fails, because neither OBS nor FFmpeg process this specific error
message; they only display a general error.
Apart from the order of messages, nothing else has been changed.
Previously, we sent the publish start message
`onStatus(NetStream.Publish.Start)` before the HTTP hook `on_publish`;
now, we have modified it to send this message after the HTTP hook.
alexanderh5453:
Same error is present when trying to stream to a Twitch server
If use invalid key publishing to twitch.tv, failed with message:
No special error message sent from twitch.tv to OBS:
twitch-obs-fail.pcapng.zip
twitch-obs-ok.pcapng.zip
SRS responsed the
onStatus(NetStream.Publish.Start)
message before close the TCP connection when hooks failed, which cause the OBS reconnecting again and again.srs.obs.fail.pcapng.zip
But please note that twitch.tv never response error message, and OBS/FFmpeg never handle the error message.
The text was updated successfully, but these errors were encountered: