OBS dropping 2/3s of frames, but only on YouTube.

[T1GlistenerElf]

First of all, thank you in advance for your help.

Previously, I had this same issue, and I was not able to get a solution to my issue. You can find that post here: https://obsproject.com/forum/threads/obs-dropping-2-3s-of-frames-but-only-on-youtube.176292/

Long story short, I was able to "fix" the problem by reverting to a previous version of OBS: 2.1.3, the last version before 3.0.

Unfortunately, I made the mistake of updating to the most recent version of OBS again, and of course the problem came back. Basically, the stream is dropping so many frames that the stream is unwatchable at best and ends due to no data for too long at worst. As with last time, I found that I could stream smoothly to Twitch, at least in Bandwidth Test Mode, but going back to YouTube did not work, neither for the primary nor the backup YouTube ingest servers, including the legacy RTMP. This also occurs even if no non-background program is running aside from OBS.

I have attached the log files from the streams in question.

P.S. Last time, I tested with both Restream and StreamlabsOBS, with both being able to stream to YouTube without issue, so it is an issue with OBS that has something to do with the 3.X updates.

 

[PaiSand]

Please use the Analyzer to fix common issues.

Analyzer | OBS

OBS (Open Broadcaster Software) is free and open source software for video recording and live streaming. Stream to Twitch, YouTube and many other providers or record your own videos with high quality H264 / AAC encoding.

obsproject.com

You're using a 100mbps network connection when you should be using a 1000mbps (1Gbps) or higher if your motherboard allows it. In your previous post this wasn't an issue.
This may be due to an issue on the network adapter driver, the network adapter itself, an old network cable that only allows 100mbps, a router or modem not capable of 1Gbps. You need to check on all this.
Killer's Software Suite is known for its poor performance and issues when trying to stream.

 

[T1GlistenerElf]

I'm sorry, but as with last time, my house is on fire and you offered to fix my car. I'll use the Analyzer, as you suggested, but that doesn't explain why
1) It didn't happen until I updated to 3.X, then stopped happening when I went back to 2.1.3 (both then and now;)
2) Why it didn't happen with software other than OBS; and
3) Why it didn't happen on Twitch.

With all respect, it's clearly an issue with OBS, specifically the updates starting with 3.X, not my network. If that's because Killer's Software Suite is a part of my OBS, as you suggest, then I will need to rectify that. In the meantime, I would like to update to 3.X, but until I find out what the malfunction is, then I cannot do that without it dropping frames like crazy.

 

[PaiSand]

Actual OBS version is 31.x.x not 3.x
If you want to fix you're actual issues you need to check yourself for the problems you have. If OBS detects a 100mbps instead of a 1gbps network connection is because you have an issue on the network adapter, cable or other hardware on your local network.
If it were an issue on OBS this will happen to everyone else, not just you.
I don't suggest the Killer suit is part of OBS, I state that killer software suit is known for its poor performance and issues when trying to stream. Taking it out of the equation will help.
Your problem isn't your house on fire, and less your car. You have a network issue. It's up to you to fix the issues you face.

Start wit the suggestions and recommendations on the analyzer, which have explanations on why some issues happens and how to proceed.

 

[T1GlistenerElf]

When I say 3.X, I'm sure that you know that I mean "all versions starting with 3."
If Killer Suite is not part of OBS, and if I cannot find it in the log files, then I have no idea what you're talking about. It seems as if you brought that up out of nowhere. To my knowledge, I've never downloaded anything like that. If you're referring to Killer E5000, it doesn't give me issues on 2.1.3.
My house being on fire is OBS chugging when I use 3.X, but not when I go back to using the 2.X versions. It's obviously not my internet, as it is perfectly fine with the same internet speed, but on a previous update. (This includes my having downpatched right after trying it on the most recent version and it working perfectly fine right away.) Because it only happens on 3.X, it looks to be an issue with OBS. That doesn't mean that it is just OBS: after all, it could be interacting with something else on my computer because, like you said, it would be happening with everyone else earlier.
I know that you're trying to help, but it seems like you made up your mind as to what it was and stopped trying to help afterwards.

That said, as you recommended, I did run the analyzer, and I did turn off HAGS, as it strongly recommended (calling it a critical issue.) I can update again and try an unlisted stream to see if that's the issue.

 

[rockbottom]

OBS isn't the issue, fix your rig/network.

As a former owner of a Killer NIC, they suck. Make sure the Killer Suite is not installed & find generic driver for it.

19:05:58.372: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmps://b.rtmps.youtube.com:443/live2?backup=1...
19:05:58.376: [rtmp stream: 'simple_stream'] Interface: Killer E5000 5 Gigabit Ethernet Controller (ethernet, 100↓/100↑ mbps)
19:05:58.731: [rtmp stream: 'simple_stream'] Connection to rtmps://b.rtmps.youtube.com:443/live2?backup=1 (2607:f8b0:4023:403::86) successful

19:10:09.924: Output 'simple_stream': Number of dropped frames due to insufficient bandwidth/connection stalls: 9910 (65.8%)

Stream Connection Troubleshooting | OBS

OBS Knowledge Base. Dropped frames? Your stream is disconnecting? This guide will help you troubleshoot common connection issues.

obsproject.com

 

[T1GlistenerElf]

Update:
I just tried it again with both the most recent version (31.0.3) and with 29.1.3, done minutes apart, in that order, and I have log files for each.
The first, 31.0.3, says
"21:36:10.803: Output 'simple_stream': Total frames output: 1872 (5420 attempted)
21:36:10.803: Output 'simple_stream': Total drawn frames: 5462"
The second says
"21:39:19.825: Output 'simple_stream': Total frames output: 4314
21:39:19.825: Output 'simple_stream': Total drawn frames: 4342"
Both feature the same "(Interface: Killer E5000 5 Gigabit Ethernet Controller (ethernet, 100↓/100↑ mbps)".
As suggested by the Analyzer tool, HAGS was turned off for both. No other changes were made.

Hopefully, this side-by-side comparison lets you see what might actually be the case. Because these were unlisted YouTube streams, I can even send the links, if that would provide any useful data. (The former is only showing the first 14 seconds of a 91-second recording, i.e. 5462 frames at 60fps.)

 

[T1GlistenerElf]

Edit: My apologies, as those are from the wrong day. My bad. I would edit it if I were not past the ten-minute limit. I am attaching the correct ones here. The above quotes are, however, correct.
Thank you for your patience with me, and I hope that this helps us get to the bottom of the issue.

 

[T1GlistenerElf]

New update: I followed the instructions in the OBS Log Analyzer regarding Killer NIC.
"Please download the package from the vendor's page, completely uninstall all Killer NIC items and run the installer, choosing to only install the Hardware Drivers." (I can try again without even the hardware drivers if necessary.)
Once again, I ran two unlisted test streams on YouTube, firstly in 31.0.3, then in 29.1.3, minutes apart, with the same internet connection, HAGS off for both, and no other changes.
31.0.3
"22:23:47.343: Output 'simple_stream': Total frames output: 1866 (5410 attempted)
22:23:47.343: Output 'simple_stream': Total drawn frames: 5450"
29.1.3
"22:27:04.325: Output 'simple_stream': Total frames output: 3709
22:27:04.325: Output 'simple_stream': Total drawn frames: 3735"

I appreciate your patience and help.

P.S. The reason for the discrepancy between total drawn frames is that I tried to stop both streams at about 1:00, but the 31.0.3 said "stopping stream…" for about 30 seconds thereafter.

 

[rockbottom]

I'm not updating OBS to test but it really doesn't matter anyway, your set-up needs attention. Get your ethernet working correctly & test again. Probably just a bad cable somewhere in the works but only you can to the troubleshooting.

 

[rockbottom]

I don't use YT but v31.0.3 log has some stuff that's not in the v29.1.3 log. Check the Websocket too.
.
21:34:04.565: YT: InitYTUserUrl() User is not signed
21:34:04.565: YT: InitYTUserUrl() User is not signed

21:34:39.765: [rtmp stream: 'simple_stream'] Connecting to RTMP URL rtmps://b.rtmps.youtube.com:443/live2?backup=1...
21:34:39.788: [rtmp stream: 'simple_stream'] Interface: Killer E5000 5 Gigabit Ethernet Controller (ethernet, 100↓/100↑ mbps)
21:34:40.170: [rtmp stream: 'simple_stream'] Connection to rtmps://b.rtmps.youtube.com:443/live2?backup=1 (2607:f8b0:4023:403::86) successful
21:34:40.171: [rtmp stream: 'simple_stream'] Socket send buffer is 65536 bytes
21:34:40.178: YT: GetYTApi() Failed to get Auth
21:34:40.178: ==== Streaming Start ===============================================

21:34:03.037: [obs-websocket] [obs_module_load] you can haz websockets (Version: 5.5.6 | RPC Version: 1)
21:34:03.037: [obs-websocket] [obs_module_load] Qt version (compile-time): 6.6.3 | Qt version (run-time): 6.6.3
21:34:03.037: [obs-websocket] [obs_module_load] Linked ASIO Version: 103100
21:34:03.038: DEPRECATION: obs_frontend_get_global_config is deprecated. Read from global or user configuration explicitly instead.
21:34:03.038: [obs-websocket] [MigrateGlobalConfigData] Some configurations have been migrated from old config
21:34:03.047: [obs-websocket] [obs_module_load] Module loaded.


21:37:36.030: [obs-websocket] [obs_module_load] you can haz websockets (Version: 5.2.3 | RPC Version: 1)
21:37:36.030: [obs-websocket] [obs_module_load] Qt version (compile-time): 6.4.3 | Qt version (run-time): 6.4.3
21:37:36.030: [obs-websocket] [obs_module_load] Linked ASIO Version: 101201
21:37:36.030: [obs-websocket] [Config::Load] (FirstLoad) Generating new server password.
21:37:36.035: [obs-websocket] [obs_module_load] Module loaded.

 

[prgmitchell]

New update: I followed the instructions in the OBS Log Analyzer regarding Killer NIC.
"Please download the package from the vendor's page, completely uninstall all Killer NIC items and run the installer, choosing to only install the Hardware Drivers." (I can try again without even the hardware drivers if necessary.)
Once again, I ran two unlisted test streams on YouTube, firstly in 31.0.3, then in 29.1.3, minutes apart, with the same internet connection, HAGS off for both, and no other changes.
31.0.3
"22:23:47.343: Output 'simple_stream': Total frames output: 1866 (5410 attempted)
22:23:47.343: Output 'simple_stream': Total drawn frames: 5450"
29.1.3
"22:27:04.325: Output 'simple_stream': Total frames output: 3709
22:27:04.325: Output 'simple_stream': Total drawn frames: 3735"

I appreciate your patience and help.

P.S. The reason for the discrepancy between total drawn frames is that I tried to stop both streams at about 1:00, but the 31.0.3 said "stopping stream…" for about 30 seconds thereafter.

Go to Settings>Advanced in OBS and try setting your IP family to IPv4 only.

 

[T1GlistenerElf]

Thank you very much for the updates, you two. I'll try those out after my stream today, although I'm going to have to look into what websocket is. I'll be sure to let you know how it goes.

I do love how it says "you can haz websockets". I adore little unnecessary-but-flavorful touches like that.

 

[qhobbes]

Configure the stream output to manually stream to the rtmp server (not RTMPS). Then Settings, Advanced, Enable Dynamic Bitrate.

You shouldn't drop any frames unless you have less than 50 kbps (+ audio bitrate) of bandwidth available.