My stream cuts out without alert messages with OBS via Steam why ?

RayJefferson

New Member
Hello, for some time now I've had the unpleasant surprise that OBS has been cutting my live stream without warning me, which is very annoying, especially when I realize it an hour later.
I've attached a log file for this problem.
Thanks.
 

Attachments

The log shows the stream was stopped normally by you

Code:
01:35:49.410: [rtmp stream: 'simple_stream'] User stopped the stream
01:35:49.410: [rtmp stream: 'simple_stream'] Socket send buffer is 4194304 bytes
01:35:49.410: Output 'simple_stream': stopping
01:35:49.410: Output 'simple_stream': Total frames output: 49203
01:35:49.410: Output 'simple_stream': Total drawn frames: 49279 (49285 attempted)
01:35:49.410: Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 6 (0.0%)
01:35:49.411: Video stopped, number of skipped frames due to encoding lag: 6/49263 (0.0%)
01:35:49.412: ==== Streaming Stop ================================================
 
Here the solution to have a sound alert when stream down.

Anyone who streams knows the nightmare: the connection fluctuates, OBS goes into "Reconnecting..." mode , and the program continues playing—but nobody on the other end can see you. Often, the streamer only realizes this minutes later. The idea here is simple: when the transmission drops, the computer itself emits a loud alert sound , like an alarm, so you notice immediately and can take action.

The "Reconnecting..." message remains the same as the native OBS screen —nothing changes there. The script simply adds sound on top of it. Nothing is sent to the live stream (there is no transmission during the outage); the alert plays on your PC, for you, the operator.

OBS internally notifies you when the transmission to the platform fails. Sometimes it attempts to reconnect ; other times—depending on how the connection failed—it simply terminates the transmission with an error. The script covers both cases : it listens for both the reconnection signal ( reconnect) and the failure termination signal ( stopwith error code) from the transmission output, and triggers the sound in either case. As a reinforcement, it also checks the transmission status every second , so as not to depend on a single notification. When OBS manages to reconnect ( reconnect_success), the alert is reset for the next failure.

Complete in:
In Portuguese to English by google.
 
Back
Top