Heavily Throttled Upload Rate after 24H2 update

rayhunt

New Member
I attempted to stream after running the Windows 24H2 feature update and had a major issue uploading. My upload rate was typically ranging from 200 to 500 kbps and stayed that way until I stopped streaming. Stopping stream also was very slow and took about 30+ seconds to disconnect. After I rolled back to Windows 23H2 OBS performance returned as expected. I've noticed there are many conflict reports regarding 24H2 on the forums but wanted to share this as well.

My setup is a Dell XPS 8950 with an i7-12700, 64 GB RAM, GeForce RTX 3060 Ti, and Killer E3100G Ethernet.
 

Vaesive

Member
Curious, I've also experienced throttled upload speeds in OBS for about the past month as well; OBS starts dropping frames due to network if I go above 3000kbps when I've consistenyly have been pushing 6000kbps for years. Restarted router and everything I could think of on my end regarding networking but it's only affecting OBS uploads.
 

Lawrence_SoCal

Active Member
but it's only affecting OBS uploads.
what other high-volume jitter and latency sensitive upload traffic do you have? for the vast majority of users, their livestream traffic is the ONLY upload traffic of similar volume that is real-time sensitive.

I say this meaning for most users the ONLY application they use that generates this volume of jitter & latency sensitive traffic is streaming, and you could easily see the same with OBS Studio and any other streaming software. The other historically consistent issue has been the streamelements plugin causing issues at times (whether plugin code, user mis-config, or streamelements/streamlabs back-end servers I never bothered to track down)
Have you tested with OBS Studio portable mode with a completely clean install (no plugins whatsoever, nor filters/effects, etc.)?

And Windows 11 is typical Microsoft every-other desktop OS release for last 25+ years (complete PoS). So don't exclude possible conflict with some driver, plugin, or other code with some new MS code [don't mistake correlation of running OBS Studio with causation]
 

rayhunt

New Member
Decided to give 24H2 another shot last night. This time I ran OBS studio and ONLY OBS studio. Ran it in normal mode first with all 3rd party plugins then ran it in safe mode. Same result both times, more than 60% dropped frames sluggish performance disconnecting from Twitch as well. It is NOT my internet connection either as I tested with speedtest.net and got ~250 mbps DL and 60 mbps UL. There's definitely something gone sideways with my PC, 24H2, and OBS

 

rayhunt

New Member
Decided to give 24H2 another shot last night. This time I ran OBS studio and ONLY OBS studio. Ran it in normal mode first with all 3rd party plugins then ran it in safe mode. Same result both times, more than 60% dropped frames sluggish performance disconnecting from Twitch as well. It is NOT my internet connection either as I tested with speedtest.net and got ~250 mbps DL and 60 mbps UL. There's definitely something gone sideways with my PC, 24H2, and OBS

I finally discovered the source of my OBS issues. Apparently when the 24H2 update ran it updated all the Killer NIC drivers and services and restarted all those services that break OBS. Once I went back into services and set them all to manual, OBS has performed well
1739051811351.png
 

AaronD

Active Member
I finally discovered the source of my OBS issues. Apparently when the 24H2 update ran it updated all the Killer NIC drivers and services and restarted all those services that break OBS. Once I went back into services and set them all to manual, OBS has performed well View attachment 111288
Looks like Windoze tried to be shmart again and ended up in another faceplant. It does that.

Seems to be increasing too. If you want to do anything outside of what M$ intended (like OBS is), then you kinda have to be another engineer yourself, and continue to monitor, repeatedly correct, and almost redesign some parts of their product to make it do what YOU want.

Have you thought about jumping ship yet? A lot of people are, because they refuse to touch Win11.
 

Lawrence_SoCal

Active Member
I finally discovered the source of my OBS issues. Apparently when the 24H2 update ran it updated all the Killer NIC drivers and services and restarted all those services that break OBS. Once I went back into services and set them all to manual, OBS has performed well
Killer network software/drivers have been associated with livestreaming issues for YEARS...
the brute force solution being to disable. I suspect the issue being an assumption Killer developers are using which conflicts with livestreaming... and its a matter of adjusting the right the setting(s)... but could be bad code... fortunately, I haven't had to deal with it directly.

And Aaron, I'm considering moving a bunch of my older systems to Linux as that will work fine... but the Linux eco-system takes more end-user attention than Windows, which takes more than MacOS.. like OBS Studio, with power and flexibility, comes end-user self-service responsibility..
I really know my way around Windows (more than knee deep for 35 years] ... not looking forward at my age to learning a new OS and getting even close to my level of expertise in WinNT .. but pick your poison... [I'm reminded of Linus's comments on end-user desktop Linux] vs Win11.. not looking forward to either. shrug ... the joy of 'progress' ;^)
 

AaronD

Active Member
...the Linux eco-system takes more end-user attention than Windows, which takes more than MacOS...
Depends a LOT on which distro you pick:
  • Slackware, for example, makes you build absolutely *everything* yourself! So you end up with a system that is *exactly* how YOU want it to be, because YOU made all of it and know it inside and out. Not for the feint of heart at all!
  • Ubuntu has pretty much become "the standard" for casual consumer use. It covers pretty much everything that a non-techie might need, and has a well-stocked app store that works like it's supposed to, for things that it doesn't come preinstalled with. And it has a HUGE support community. Lots of places to ask for and get help.
    • Lubuntu is a resource-light version of Ubuntu, so it runs well on older hardware, and still has all of that support.
    • Ubuntu Studio is a media- and creativity-centered version of Ubuntu. It comes with a TON of things preinstalled and already working, to support serious creative types, and also has all of that support.
  • Manjaro (I believe) has continuous updates with no periodic steps, so you always have the latest version of everything.
  • Debian has discrete steps, so things stay the same until the next step. I consider this to be important for anything live. Nothing like having it work perfectly in rehearsal, and then an update kills the show!
    • Ubuntu and all of its versions are derived from Debian, and continue to pull from it.
    • Raspberry Pi OS is also derived from Debian, with the same meaning.
For OBS, I strongly recommend Ubuntu Studio.

...like OBS Studio, with power and flexibility, comes end-user self-service responsibility...
Yes, regardless of what it runs on. Windows, Mac, and Linux all have that. Any time you set up a new rig, you need to look through ALL the settings, EVERYWHERE, figure out what they do, and make it work for you and not the other way around. For me, I:
  • Auto-login.
    • Crew's panicked power-on at the last minute, and go straight into a show. Yes, it should have been on sooner, but things happen...
    • Plus, I grew up on Windows 98 and XP, that were single-user systems and had that behavior by default.
      • Yes, I know XP (sorta) supported multiple users, but not really...
  • Turn off all of the power saving, screen saving, auto-lock from inactivity, etc.
    • If I forget and let it sit while I go on vacation, I want it to burn my desktop into the physical screen.
    • Don't lock out the crew just before a show, and don't take away a live audience's display.
  • Turn off all automatic updating, and replace it with a script that I optionally run on shutdown. If I still have some show to do later, I don't. If I'm done for a while, I do. And I train the crew that way: don't after rehearsal, do after service.
I haven't really needed anything else on Ubuntu and its derivatives, or the Raspberry Pi.

...Linus's comments on end-user desktop Linux...
If you're talking about this video:
Yeah, he does have a bunch of valid points. But I think the better way to think of it, is to define an OS by how broadly the same binary package can run. So if something works on Ubuntu, then it can probably be used as-is on Lubuntu, Ubuntu Studio, Raspberry Pi, and a bunch more that are all based on Debian. (with the ISA being the only reason to recompile a different binary: x86, ARM, etc.) Manjaro and Arch are distinct operating systems from that, even if they use the same kernel.

So the "Linux" subforum here, actually supports a wide variety of operating systems, while the Mac and Windows subforums only support one each.

If you're going to learn something beyond the big two, I'd recommend sticking with Debian, in the form of Ubuntu and Pi. Don't have Arch on one, SUSE on another, Red Hat somewhere else, etc., because they're practically all different *operating systems* and require different understandings and packages on *that* level.
 
Last edited:

AaronD

Active Member
I really know my way around Windows (more than knee deep for 35 years] ... not looking forward at my age to learning a new OS and getting even close to my level of expertise in WinNT .. but pick your poison... [I'm reminded of Linus's comments on end-user desktop Linux] vs Win11.. not looking forward to either. shrug ... the joy of 'progress' ;^)
I'm not that old yet, but I've still seen what happens when you get used to something, become an expert at it, and then have to abandon all of it in favor of something new that does the same thing in a completely different way. It's a pretty steep learning curve, but well worth it! Not looking forward to that process becoming more difficult...
  • Analog sound to digital sound.
    • I'm actually in the process of building a wheeled rack for a bunch of analog gear that I inherited from various church upgrades. Medium to large format, pure analog, except for the multitrack recorder to a hard drive. No digital processing whatsoever: just storage and regurgitation as-is.
      Something tells me I'm going to use it somewhere, but I won't know where until the need is immediate. So I'm building it now, to be ready for that.
    • And I seem to run circles around the older analog guy, on the new digital board at church.
      • I think it was exactly the right way to learn, at the right time too, to start with analog in junior high and make it sing over the next few years, and *then* switch to digital with the knowledge that it works the same way. You just have lots of toys built-in, that all work the same way as they do in analog (or they *would* if the analog rig had a lot more money behind it), and lots of pages to reach all of it...
  • Windows to Ubuntu and Raspberry Pi.
    • Like I said, I grew up on Windows 98 and XP, and didn't know anything else. I first saw Linux in college, from a Linux activist group giving out free Ubuntu CD's. Since then, I wavered back and forth, usually dual-booting but not really using the other boot very much. Then when Win10 refused to update, I finally became single-boot again.
    • And I have some casual desktop systems in various places, that run on Raspberry Pi's.
      • Originally because they were cheap. (not so much anymore, by the time you make it work *well*)
      • Also because they're physically small and easy to power.
  • Etc.
 
Top