The WORST stream in the 14 years I've been doing shows

J

jsolomonster

Member
So last night was a complete disaster for my livestream. I apparently went the first 25 minutes without looking at the chat and not knowing that my audio was screwed and video was lagging like crazy. Reason being, my CPU usage spiked to near 50 percent, which has never happened to me before. No settings were changed, everything was as it was for my previous streams. I stopped the stream within OBS and re-connected, was fine for about three minutes and then BOOM, right back up near 50 percent again. I closed out any background antivirus software, I even closed the web browser, yet it persisted. I shut down the computer, restarted and then r-connected -- rinse/repeat, to no avail. Now I'm terrified this is going to keep happening.

Here is the last log file, but I don't know what it will show you as I started/stopped streaming from within OBS so many times. Any input would be greatly appreciated.

 
Difficult. You have very complex setup with streamelements too. So your OBS universe depends on foreign sources and services during runtime. I believe that you didn't change anything. But every change in webservice, due to windows updates or vst-plugins may introduce such worse. Sometimes just a small hidden "we changed the default behaviour of XXXX" is sufficient for that.

We can see at least in your log that (audio alone) your audio thread maxes out by 330ms. This is way to much. You've alot of filters set including external vst-plugins in multiple instances. Thats errorprone (at least). Even though it worked till now. *sigh*

Your hotkey thread is well overload (93% runtime over their 25msec spec, so almost ever delayed due to something).
Your graphics thread then maxes out at 4.9 seconds. Even if that happens just once, its HUGE.

So only a silent hint can be given (at least from me): Try to trim/reduce your setup to a more slim setup. Thats just my humble opinion. There might be other folks here with more knowledge to debugging of such setups.
 
konsolenritter said:
Difficult. You have very complex setup with streamelements too. So your OBS universe depends on foreign sources and services during runtime. I believe that you didn't change anything. But every change in webservice, due to windows updates or vst-plugins may introduce such worse. Sometimes just a small hidden "we changed the default behaviour of XXXX" is sufficient for that.

We can see at least in your log that (audio alone) your audio thread maxes out by 330ms. This is way to much. You've alot of filters set including external vst-plugins in multiple instances. Thats errorprone (at least). Even though it worked till now. *sigh*

Your hotkey thread is well overload (93% runtime over their 25msec spec, so almost ever delayed due to something).
Your graphics thread then maxes out at 4.9 seconds. Even if that happens just once, its HUGE.

So only a silent hint can be given (at least from me): Try to trim/reduce your setup to a more slim setup. Thats just my humble opinion. There might be other folks here with more knowledge to debugging of such setups.
Click to expand...

Thank you, I do wish I had more knowledge of what these "threads" indicate and how to change them, like the graphics thread you mentioned. I did also consider downgrading to 30fps, if you thought that might help, but from what you're saying, that likely isn't enough.
 
1. One of your audio devices has a sample rate that doesn't match the rest. This can result in audio drift over time or sound distortion. Check your audio devices in Windows settings (both Playback and Recording) and ensure the Default Format (under Advanced) is consistent. 48000 Hz is recommended.
OBS Sample Rate: 48000 Hz
Speakers (Yeti Stereo Microphone): 48000 Hz
Microphone (HD Pro Webcam C920): 16000 Hz
Microphone (Yeti Stereo Microphone): 48000 Hz
Speakers / Headphones (Realtek Audio): 48000 Hz
2. Uncheck the box Psycho Visual Tuning.
 
You must log in or register to reply here.
Back
Top