Livestream stops at random, 45 minutes of log missing

[Roel SmuldersAV]

Hi all
We use OBS to livestream events on Vimeo. The last couple of times our stream stops at random and the livestream in vimeo is stopt and put in the video folder. If we want to set up a new livestream, we now have to make a new event, put a new streamkey in obs and give our client a new embedcode. This has happend a couple of times now and we want to figure out what is wrong.

So we looked up the OBS log file and during the time of the crash, 45 minutes of log file is missing. It stops at a random camera switch and start again when i've pressed stop stream to put in a new streamkey.

13:47:56.912: User switched to scene 'PIP'
13:47:59.372: User switched to scene 'Totaal Camera'
14:36:36.785: [rtmp stream: 'simple_stream'] User stopped the stream
14:36:36.785: [rtmp stream: 'simple_stream'] Socket send buffer is 1048576 bytes
14:36:36.785: Output 'simple_stream': stopping
14:36:36.786: Output 'simple_stream': Total frames output: 607827
14:36:36.786: Output 'simple_stream': Total drawn frames: 607877 (607878 attempted)
14:36:36.786: Output 'simple_stream': Number of lagged frames due to rendering lag/stalls: 1 (0.0%)
14:36:36.786: Video stopped, number of skipped frames due to encoding lag: 1/607850 (0.0%)
14:36:36.789: ==== Streaming Stop ================================================
14:36:36.956: warning: 2 frames left in the queue on closing
14:37:31.066: Settings changed (stream 1)
14:37:31.066: ------------------------------------------------
14:37:38.700: [jim-nvenc: 'simple_video_stream'] settings:
14:37:38.700: codec: H264
14:37:38.700: rate_control: CBR
14:37:38.700: bitrate: 3000
14:37:38.700: cqp: 20
14:37:38.700: keyint: 250
14:37:38.700: preset: p6
14:37:38.700: tuning: hq
14:37:38.700: multipass: qres
14:37:38.700: profile: high
14:37:38.700: width: 1920
14:37:38.700: height: 1080
14:37:38.700: b-frames: 2
14:37:38.700: lookahead: true
14:37:38.700: psycho_aq: true
14:37:38.700:
14:37:38.789: ---------------------------------
14:37:38.789: [FFmpeg aac encoder: 'simple_aac'] bitrate: 192, channels: 2, channel_layout: 3
14:37:38.789:
14:37:38.790: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmp://rtmp.cloud.vimeo.com/live...
14:37:38.818: [rtmp stream: 'simple_stream'] Interface: Realtek PCIe GbE Family Controller (ethernet, 1000 mbps)
14:37:44.090: [rtmp stream: 'simple_stream'] Connection to rtmp://rtmp.cloud.vimeo.com/live successful
14:37:44.091: [rtmp stream: 'simple_stream'] Socket send buffer is 65536 bytes
14:37:44.104: ==== Streaming Start ===============================================
14:39:26.221: User switched to scene 'Totaal PowerPiont'
14:39:28.672: User switched to scene 'PIP'
14:39:40.072: User switched to scene 'Totaal PowerPiont'
14:39:42.897: User switched to scene 'Totaal Camera'

Our livestream stopt at 14:31. So we are also missing a lot of scene switches.

Is there anyone who have had this same problem or knows the solution?

Kind regards

Roel Smulders AV

 

[Lawrence_SoCal]

It is RARELY random... more often, just triggered by things you aren't seeing/watching
what are you doing for real-time hardware resource monitoring (or are you doing the equivalent of driving blind-folded)?
Oh, and real-time network monitoring including WAN connection?

With only a partial OBS log, I can't say... and even with a full log, nothing guaranteed... lots can happen on a PC outside OBS (background processes not disabled, etc).

Scene switches themselves rarely an issue
your sources, filters, effects, plugins and changes to those across scenes... those can definitely have an impact. Typically, issues with scene changes come down to an interaction between sources and plugins.

So your livestreamed stopped at a certain time, but you didn't include the log from that timeframe??

13:47:59.372: User switched to scene 'Totaal Camera'​

14:36:36.785: [rtmp stream: 'simple_stream'] User stopped the stream​

or were log entries missing for almost 50 minutes? or were there no scene or other OBS changes during that time window?
if there were scene changes after 13:47 and before 14:31... then I'm guessing OBS was in an unstable state (or CPU completely overloaded?)

 

[Roel SmuldersAV]

It is RARELY random... more often, just triggered by things you aren't seeing/watching
what are you doing forg real-time hardware resource monitorin (or are you doing the equivalent of driving blind-folded)?
Oh, and real-time network monitoring including WAN connection?

With only a partial OBS log, I can't say... and even with a full log, nothing guaranteed... lots can happen on a PC outside OBS (background processes not disabled, etc).

Scene switches themselves rarely an issue
your sources, filters, effects, plugins and changes to those across scenes... those can definitely have an impact. Typically, issues with scene changes come down to an interaction between sources and plugins.

So your livestreamed stopped at a certain time, but you didn't include the log from that timeframe??

13:47:59.372: User switched to scene 'Totaal Camera'​

14:36:36.785: [rtmp stream: 'simple_stream'] User stopped the stream​

or were log entries missing for almost 50 minutes? or were there no scene or other OBS changes during that time window?
if there were scene changes after 13:47 and before 14:31... then I'm guessing OBS was in an unstable state (or CPU completely overloaded?)

Hi Lawrence
First of all, let me thank you for taking the time to help me! Maybe Random wasn't the best word i could have used. It stopt and i don't know why. We always do a speedtest before starting the stream and we always use a cable. Vimeo shows a graph of how stable the network is. To be honest, we do not have much hardware to begin with. So we monitor it in real live. We set up small temperary setups with 1 camera and a beamer, hows laptop is pluged in the computer using a atem mini along side the camera.

There are almost 50 minutes of log files missing and during this time the stream stopt. There were defitnetly scene changes during this time. Can you tell me more about OBS being in an unstable state and/or CPU completely overloaded?

Roel

 

[Lawrence_SoCal]

Thinking trying to tow a large boat with a Yugo (or Smart car)... that is overloaded.

See my .sig for link to article on posting full OBS log (it is just a text file... so if you feel it appropriate, you can always open and edit out any names/labels, etc that you consider sensitive [but use a 1:1 replacement, ex. if Scene name is sensitive, make sure log uniquely identifies Scene A vs B vs C, etc]

real-tiem video rendering is computationally intensive work. Certain plugins add even more (to a lot) of CPU load. And then there are background Operating System processes and user installed software that can cause resource demands leading to contention/conflict. So, it responsibility of end-user to monitor hardware resource utilization (otherwise you are doing equivalent of driving blindfolded). Now is overload the CPU, GOU, disk I/O (especially possible with HDD vs SSD)? can't say without more info
And an OBS log only shows OBS, it does NOT show all the other processes running at the Operating System level