Multi-Streaming kills bitrate and in-game framerate

[TeeJayH]

I hope this is the right forum thread to post this but please tell me otherwise and I can change it!

I have been attempting to multi-stream for a few months now to youtube and twitch using both the multi-stream obs plugin and the Aitum multi-stream plugin (currently using) and whenever I attempt to start out the second stream my bitrate suddenly becomes incredibly unstable and I can't play any game involving the internet without huge lag/framerate issues. I added a SS of my OBS settings and internet speed test. If anyone has any suggestions or notices what I'm doing wrong please let me know! I would love to keep trying to multi-stream at 1080p 60fps instead of single stream on twitch. I added three OBS log from my last stream on Friday November 11 that was giving me bad bitrate issues.

OBS and Aitum multi-streaming plugin Settings:

Here's a picture of my pc specs too:

 

[rockbottom]

Start by disabling HAGS.

Then head over to the support page for your mobo & update the driver for your Network Adapter, this should get rid of those zero counter errors. After that's done run another test/post log, there's more crap that needs to be flushed.

19:19:28.548: HAGS Status: Enabled (Default: No, Driver status: Supported)

20:39:40.825: [rtmp stream: 'aitum_multi_output_YouTube Output'] Connecting to RTMP URL rtmps://a.rtmps.youtube.com:443/live2...
20:39:40.877: [rtmp stream: 'aitum_multi_output_YouTube Output'] Interface: Intel(R) I211 Gigabit Network Connection (ethernet, 1000↓/1000↑ mbps)
20:39:40.877: [rtmp stream: 'aitum_multi_output_YouTube Output'] Interface has non-zero error counters (422/0 errors, 844/0 discards)
20:39:41.217: [rtmp stream: 'aitum_multi_output_YouTube Output'] Connection to rtmps://a.rtmps.youtube.com:443/live2 (142.251.35.172) successful
20:39:41.217: [rtmp stream: 'aitum_multi_output_YouTube Output'] Socket send buffer is 64512 bytes
20:40:46.234: User switched to scene 'Desktop'
20:41:58.871: [Aitum Multistream] stop stream clicked 'YouTube Output'
20:41:59.117: [rtmp stream: 'aitum_multi_output_YouTube Output'] User stopped the stream
20:41:59.117: [rtmp stream: 'aitum_multi_output_YouTube Output'] Socket send buffer is 262144 bytes
20:41:59.117: Output 'aitum_multi_output_YouTube Output': stopping
20:41:59.117: Output 'aitum_multi_output_YouTube Output': Total frames output: 6584 (8262 attempted)
20:41:59.117: Output 'aitum_multi_output_YouTube Output': Total drawn frames: 8298
20:41:59.117: Output 'aitum_multi_output_YouTube Output': Number of dropped frames due to insufficient bandwidth/connection stalls: 1678 (20.3%)
20:41:59.170: warning: 2 frames left in the queue on closing
20:42:06.600: Output 'Replay Buffer': stopping
20:42:06.600: Output 'Replay Buffer': Total frames output: 125601
20:42:06.600: Output 'Replay Buffer': Total drawn frames: 125621 (125627 attempted)
20:42:06.600: [rtmp stream: 'adv_stream'] User stopped the stream
20:42:06.601: Output 'Replay Buffer': Number of lagged frames due to rendering lag/stalls: 6 (0.0%)
20:42:06.601: [rtmp stream: 'adv_stream'] Socket send buffer is 1048576 bytes
20:42:06.601: Output 'adv_stream': stopping
20:42:06.601: Output 'adv_stream': Total frames output: 118294 (125481 attempted)
20:42:06.601: Output 'adv_stream': Total drawn frames: 125622 (125628 attempted)
20:42:06.601: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 6 (0.0%)
20:42:06.601: Output 'adv_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 7187 (5.7%)
20:42:06.601: ==== Replay Buffer Stop ============================================
20:42:06.605: ==== Streaming Stop ================================================
20:42:06.615: Video stopped, number of skipped frames due to encoding lag: 6/125625 (0.0%)

 

[TeeJayH]

Start by disabling HAGS.

Then head over to the support page for your mobo & update the driver for your Network Adapter, this should get rid of those zero counter errors. After that's done run another test/post log, there's more crap that needs to be flushed.

19:19:28.548: HAGS Status: Enabled (Default: No, Driver status: Supported)

20:39:40.825: [rtmp stream: 'aitum_multi_output_YouTube Output'] Connecting to RTMP URL rtmps://a.rtmps.youtube.com:443/live2...
20:39:40.877: [rtmp stream: 'aitum_multi_output_YouTube Output'] Interface: Intel(R) I211 Gigabit Network Connection (ethernet, 1000↓/1000↑ mbps)
20:39:40.877: [rtmp stream: 'aitum_multi_output_YouTube Output'] Interface has non-zero error counters (422/0 errors, 844/0 discards)
20:39:41.217: [rtmp stream: 'aitum_multi_output_YouTube Output'] Connection to rtmps://a.rtmps.youtube.com:443/live2 (142.251.35.172) successful
20:39:41.217: [rtmp stream: 'aitum_multi_output_YouTube Output'] Socket send buffer is 64512 bytes
20:40:46.234: User switched to scene 'Desktop'
20:41:58.871: [Aitum Multistream] stop stream clicked 'YouTube Output'
20:41:59.117: [rtmp stream: 'aitum_multi_output_YouTube Output'] User stopped the stream
20:41:59.117: [rtmp stream: 'aitum_multi_output_YouTube Output'] Socket send buffer is 262144 bytes
20:41:59.117: Output 'aitum_multi_output_YouTube Output': stopping
20:41:59.117: Output 'aitum_multi_output_YouTube Output': Total frames output: 6584 (8262 attempted)
20:41:59.117: Output 'aitum_multi_output_YouTube Output': Total drawn frames: 8298
20:41:59.117: Output 'aitum_multi_output_YouTube Output': Number of dropped frames due to insufficient bandwidth/connection stalls: 1678 (20.3%)
20:41:59.170: warning: 2 frames left in the queue on closing
20:42:06.600: Output 'Replay Buffer': stopping
20:42:06.600: Output 'Replay Buffer': Total frames output: 125601
20:42:06.600: Output 'Replay Buffer': Total drawn frames: 125621 (125627 attempted)
20:42:06.600: [rtmp stream: 'adv_stream'] User stopped the stream
20:42:06.601: Output 'Replay Buffer': Number of lagged frames due to rendering lag/stalls: 6 (0.0%)
20:42:06.601: [rtmp stream: 'adv_stream'] Socket send buffer is 1048576 bytes
20:42:06.601: Output 'adv_stream': stopping
20:42:06.601: Output 'adv_stream': Total frames output: 118294 (125481 attempted)
20:42:06.601: Output 'adv_stream': Total drawn frames: 125622 (125628 attempted)
20:42:06.601: Output 'adv_stream': Number of lagged frames due to rendering lag/stalls: 6 (0.0%)
20:42:06.601: Output 'adv_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 7187 (5.7%)
20:42:06.601: ==== Replay Buffer Stop ============================================
20:42:06.605: ==== Streaming Stop ================================================
20:42:06.615: Video stopped, number of skipped frames due to encoding lag: 6/125625 (0.0%)

Thanks for the reply! I disabled HAGS, updated internet drivers, and went through and also removed the Aitum multi-stream tool and supplemented it with the rtmp-multi-stream plugin for more customizability (linked in my original post). I did a test stream of just my camera using the multi-stream plugin (YouTube stream SS attached of those settings) and regular OBS (twitch).

I uploaded all logs from my test streams that I have done today. I didn't get any dropped frames from network connection but if there's anything else you see in my logs I will be happy to take more advice to run my OBS as efficiently as possible to avoid crashes in the future :)

 

[rockbottom]

Much better, your Network Adapter EEE settings have been updated with the new driver so those zero counter errors are now history.

Some suggestions

When using OBS run your main monitor @ 120HZ & the other monitors that your not capturing from @ 60HZ. This will reduce load on your system & make your recordings & streams look much better.

Check your Scenes, there are a few that contain multiple Display, Game or Window captures. There should only be (1) per Scene to avoid interference.

Your have (5) Source Audio Inputs & you're using "Use Device Timing" for all of them. Only your Main Audio should be using device timing, disable it for the other (4).
1:36:34.081: [win-wasapi: '02 - Gamer'] update settings:
11:36:34.081: device id: {0.0.0.00000000}.{55109220-721a-4406-a316-bcd0d9c604cc}
11:36:34.081: use device timing: 1
11:36:34.081: [win-wasapi: '01 - Discord'] update settings:
11:36:34.081: device id: {0.0.0.00000000}.{f472b7c7-290a-4c0e-836b-60d0d51ee006}
11:36:34.081: use device timing: 1
11:36:34.082: [win-wasapi: '04 - Music'] update settings:
11:36:34.082: device id: {0.0.0.00000000}.{511bf86b-d373-483e-a517-1453393d19b9}
11:36:34.082: use device timing: 1
11:36:34.083: [win-wasapi: '03 - Browser'] update settings:
11:36:34.083: device id: {0.0.0.00000000}.{fd0cd413-23b8-46a9-ac78-e04d8ac44025}
11:36:34.083: use device timing: 1
11:36:35.202: [win-wasapi: '05 - Truffle'] update settings:
11:36:35.202: device id: {0.0.0.00000000}.{e23a348c-ede3-4097-b1bd-95931bdd86dc}
11:36:35.202: use device timing: 1

There's lots of Stream Elements & Java Script errors in your log, best to eliminate or fix them, they waste resouces. This is just a small sample.
11:36:36.941: [obs-browser: 'SE Alerts Twitch'] Error: zaraz is loaded twice (https://streamelements.com/overlay/...KjyEbAALk26j3oONaO7oURf4Jz4kamuTlInz7c3I57p:4)
11:36:37.096: [obs-browser: 'YouTube Alerts'] Error: zaraz is loaded twice (https://streamelements.com/overlay/...643-oXweDOj7bTXccMijaY1F9T5NzZe4fiLqfcepDV-:4)
11:36:37.167: [obs-browser: 'Overlay'] Error: [OPTIMIZELY] - ERROR 2024-11-13T16:36:37.166Z PROJECT_CONFIG_MANAGER: You must provide at least one of sdkKey or datafile. Cannot start Optimizely (https://site-assets.tiltify.com/overlay-suite/assets/index-B2V1vie6.js:74)
11:36:37.203: [obs-browser: 'Charity Alert Box'] Error: [OPTIMIZELY] - ERROR 2024-11-13T16:36:37.203Z PROJECT_CONFIG_MANAGER: You must provide at least one of sdkKey or datafile. Cannot start Optimizely (https://site-assets.tiltify.com/overlay-suite/assets/index-B2V1vie6.js:74)
11:36:37.352: [obs-browser: 'Socials'] Error: zaraz is loaded twice (https://streamelements.com/overlay/...643-oXweDOj7bTXccMijaY1F9T5NzZe4fiLqfcepDV-:4)
11:36:38.585: [obs-browser: 'Discord Face'] Error: WS Closed: [object CloseEvent] (https://streamkit.discord.com/static/js/main.daa4bcc9.js:2)
11:36:40.622: [obs-browser: 'Discord Face'] Error: WS Closed: [object CloseEvent] (https://streamkit.discord.com/static/js/main.daa4bcc9.js:2)
11:36:42.643: [obs-browser: 'Discord Face'] Error: WS Closed: [object CloseEvent] (https://streamkit.discord.com/static/js/main.daa4bcc9.js:2)

 

[TeeJayH]

Much better, your Network Adapter EEE settings have been updated with the new driver so those zero counter errors are now history.

Some suggestions

When using OBS run your main monitor @ 120HZ & the other monitors that your not capturing from @ 60HZ. This will reduce load on your system & make your recordings & streams look much better.

Check your Scenes, there are a few that contain multiple Display, Game or Window captures. There should only be (1) per Scene to avoid interference.

Your have (5) Source Audio Inputs & you're using "Use Device Timing" for all of them. Only your Main Audio should be using device timing, disable it for the other (4).
1:36:34.081: [win-wasapi: '02 - Gamer'] update settings:
11:36:34.081: device id: {0.0.0.00000000}.{55109220-721a-4406-a316-bcd0d9c604cc}
11:36:34.081: use device timing: 1
11:36:34.081: [win-wasapi: '01 - Discord'] update settings:
11:36:34.081: device id: {0.0.0.00000000}.{f472b7c7-290a-4c0e-836b-60d0d51ee006}
11:36:34.081: use device timing: 1
11:36:34.082: [win-wasapi: '04 - Music'] update settings:
11:36:34.082: device id: {0.0.0.00000000}.{511bf86b-d373-483e-a517-1453393d19b9}
11:36:34.082: use device timing: 1
11:36:34.083: [win-wasapi: '03 - Browser'] update settings:
11:36:34.083: device id: {0.0.0.00000000}.{fd0cd413-23b8-46a9-ac78-e04d8ac44025}
11:36:34.083: use device timing: 1
11:36:35.202: [win-wasapi: '05 - Truffle'] update settings:
11:36:35.202: device id: {0.0.0.00000000}.{e23a348c-ede3-4097-b1bd-95931bdd86dc}
11:36:35.202: use device timing: 1

There's lots of Stream Elements & Java Script errors in your log, best to eliminate or fix them, they waste resouces. This is just a small sample.
11:36:36.941: [obs-browser: 'SE Alerts Twitch'] Error: zaraz is loaded twice (https://streamelements.com/overlay/...KjyEbAALk26j3oONaO7oURf4Jz4kamuTlInz7c3I57p:4)
11:36:37.096: [obs-browser: 'YouTube Alerts'] Error: zaraz is loaded twice (https://streamelements.com/overlay/...643-oXweDOj7bTXccMijaY1F9T5NzZe4fiLqfcepDV-:4)
11:36:37.167: [obs-browser: 'Overlay'] Error: [OPTIMIZELY] - ERROR 2024-11-13T16:36:37.166Z PROJECT_CONFIG_MANAGER: You must provide at least one of sdkKey or datafile. Cannot start Optimizely (https://site-assets.tiltify.com/overlay-suite/assets/index-B2V1vie6.js:74)
11:36:37.203: [obs-browser: 'Charity Alert Box'] Error: [OPTIMIZELY] - ERROR 2024-11-13T16:36:37.203Z PROJECT_CONFIG_MANAGER: You must provide at least one of sdkKey or datafile. Cannot start Optimizely (https://site-assets.tiltify.com/overlay-suite/assets/index-B2V1vie6.js:74)
11:36:37.352: [obs-browser: 'Socials'] Error: zaraz is loaded twice (https://streamelements.com/overlay/...643-oXweDOj7bTXccMijaY1F9T5NzZe4fiLqfcepDV-:4)
11:36:38.585: [obs-browser: 'Discord Face'] Error: WS Closed: [object CloseEvent] (https://streamkit.discord.com/static/js/main.daa4bcc9.js:2)
11:36:40.622: [obs-browser: 'Discord Face'] Error: WS Closed: [object CloseEvent] (https://streamkit.discord.com/static/js/main.daa4bcc9.js:2)
11:36:42.643: [obs-browser: 'Discord Face'] Error: WS Closed: [object CloseEvent] (https://streamkit.discord.com/static/js/main.daa4bcc9.js:2)

If I'm gaming for livestreams, should I still reduce Hz on main monitor? Also, I have split audio for different applications for me to help control my audio through my wave link. Does that make a difference for the "device timing" you mentioned? I just want to make sure before changing those. I can clean slate my scenes and make sure those are good to go too. Thanks again for all the help!

 

[rockbottom]

I personally only run my monitors @ 60HZ, 120, 240 or 360. I don't own & never will purchase a monitor that is limited to 144 or 165. Running @ 144 or 165 screws up the frame timing & if you run v-sync, forgetaboutit, it isn't going to work correctly.

There's no way all those different audio sources are arriving at OBS at the same exact time so just use the main audio for timing purposes, this is most likely your game audio.

 

[TeeJayH]

I personally only run my monitors @ 60HZ, 120, 240 or 360. I don't own & never will purchase a monitor that is limited to 144 or 165. Running @ 144 or 165 screws up the frame timing & if you run v-sync, forgetaboutit, it isn't going to work correctly.

There's no way all those different audio sources are arriving at OBS at the same exact time so just use the main audio for timing purposes, this is most likely your game audio.

Okay I'll do 120 then! I removed timestamps and I believe I either fixed or removed the sources you called out. I ran a youtube and twitch test stream and it all seemed alright! Only question is that I'm curious for more resource intense games (overwatch/call of duty) proper in-game settings to make the quality not drop drastically. The test I ran I played a game of call of duty for these logs too FYI.

Here's the link to the test youtube stream if you want to look at the quality of the VOD too. I'm seeing some more failures for plugins. I might just go through and wipe those out too.

 

[rockbottom]

Odd, you're still getting those zero counter errors, but there's no dropped frames. Are you running on a power saving plan?

Overall, not too bad but there's room for improvement. The main monitor was still @ 144 & there's still have a ton of SE/Java Script errors.

Desktop & Melee scenes have Game/Monitor/Window captures.

Nvidia updated the Audio FX, new version is 1.3.22.0, there's no release notes so no idea what was updated in the latest version.

I would kick this plugin to the curb....
18:35:23.303: Failed to load 'en-US' text for module: 'win-capture-audio.dll'
18:35:23.303: [win-capture-audio] Version 2.2.3 (74323e6)

 

[TeeJayH]

Odd, you're still getting those zero counter errors, but there's no dropped frames. Are you running on a power saving plan?

Overall, not too bad but there's room for improvement. The main monitor was still @ 144 & there's still have a ton of SE/Java Script errors.

Desktop & Melee scenes have Game/Monitor/Window captures.

Nvidia updated the Audio FX, new version is 1.3.22.0, there's no release notes so no idea what was updated in the latest version.

I would kick this plugin to the curb....
18:35:23.303: Failed to load 'en-US' text for module: 'win-capture-audio.dll'
18:35:23.303: [win-capture-audio] Version 2.2.3 (74323e6)

I don't know why it's reading 144 after reading this I went into my monitor settings in windows and confirmed it stayed changed from 144 to 120. I removed the extra captures and the audio I think was fixed because I chose to download the CoreAudio.msi file and use that since I saw that was failing too. Would it be wise to eliminate the SE plugins I have to (maybe?) get rid of those SE/JS errors? I can run another test today after work and send logs.

 

[rockbottom]

If OBS was open when you made the change from 144 to 120, it wouldn't be updated until OBS is closed.

I don't see the SE plugin in the log, are you sure it was installed? The errors just appear to be browser sources.