I've been doing a "Monday In The Studio" YouTube live stream for a few months now. For the most part, it's gone well but there are nights, like last night, where it all falls apart. I started the live stream and noticed right away that the quality indicator was red and it showed me that 62% of the frames were being dropped. I did a speed test and found download to be 200mb and upload was 11mb. That should be plenty fast enough for 30fps @ 4500kbps, but it wasn't. These same settings almost always work just fine. I've only had one other occasion when it was this bad. I ended up having to apologize and end the show early. I did more testing and it kept having the same problem. Then I waited 90 minutes and tried again around 9:30pm CST. All was fine with zero dropped frames. Not a single problem. Same settings, nothing changed on my end.
Question: Is it possible that YouTube Live is the source of the problems? Can their servers just be overloaded?
BTW: I'm running the latest OBS build that came out last week and my Nvidia drivers are up to date as well.
I know this is fairly off-topic but I'm sure some others are using OBS or are doing live streaming.
Disclaimer: not a pro or expert on this level, but have had to troubleshoot some similar intermittent issues with clients in the past.
The first thing I would note is that OBS in particular seems to have some issues if the computer was asleep at some point before starting OBS or starting to stream (Resetting fixes that issue). Other times, I know to youtube, OBS can have some odd behaviors very rarely with horrible performance that can be corrected just by stopping and starting the stream again. Putting aside the generic IT "restart it" solutions...
I think far more people deal with issues on stable upload than not, but for the majority of ISP customers, you would hardly notice it outside of some web apps behaving a little more erratically than normal.
I'd first look into whether you're dealing with pocket loss when the issue is occurring. The issue will often not display itself until you're actually having these upload issues, so it can be hard to troubleshoot the other 95% of the time when your connection is good. I don't have the exact instructions, but you can use command prompt on windows to ping whatever public DNS you see fit* to see if there's any issue on that front -- but again, if it's like what I've encountered, nothing will look abnormal until the unstable upload issue is actually happening again. There are other "test" sites out there that will measure these metrics, but I don't recall which ones off the top of my head.
In any case, if you can document reported packet-loss, it might give you a little more to work with your ISP; if you're on a business account and paying that bloody premium, it tends to be a little easier to twist your ISP's arms to get an actual tech out to check out what's going on, but this can be an ordeal - depending on the tech, if they come out when everything is working fine, they could fail to comment the complexity of the situation on the support ticket, leave and you're back to square one.
There is a possibility that what you're dealing with is more related to node or hub issues, something local, but I wouldn't think this is OBS-related if the problem doesn't occur consistently and seems to come and go without any drastic changes to your OBS settings.
My sympathies, network issues can be a bit of a headache.
I don't have the answers, but have experienced some of the same issues. However, I'm running an older PC that is still using Windows 7, so I chalked it up to my machine more than the connection. I did a livestream Christmas concert in 2020 and pulled it off, but for 2021's concert I just recorded locally using OBS and then streamed it as a "live" concert, which seemed to eliminate a lot of those issues. Not ideal, but a "safer" bet for me.
What is important is seldom urgent and what is urgent is seldom important. - Dwight Eisenhower
I've been thinking of just doing a prerecorded version but there's something about the live interaction that is appealing to me.
Enlav, I work in IT during the day (to pay the bills). This is an odd one. I had checked for bottlenecks in the local network but didn't find any. That's why I started wondering about YouTube itself as being a source of the issue. Seems hard to believe but I couldn't come up with any other workable theory.
I had checked for bottlenecks in the local network but didn't find any.
This probably wouldn't be a LAN issue but more likely something everyone on your node is experiencing (worse yet if it's a large portion of customers). Though as weird as it sounds, I'd be hoping it's something like the cable going into your building, or a problem at the junction box. Something that's actually addressable instead of something else outside of your property or control.
But sorry for the delay on the reply and follow up- the next time it happens (if you decide to keep streaming; no shame in pre-recording as Teejay suggests), open up a command prompt and just ping a suitable domain.
ping 188.8.131.52 -n 10
184.108.40.206 is just a google DNS and the "-n #" at the end determines how many echos will be issued. Technically, from what I remember reading on this, the google domains aren't actually the best or most suitable addresses to use for troubleshooting (apparently?) - but I've always used that or some other public DNS without any issue.
(example - this would be a normal instance)
Ping statistics for 220.127.116.11: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 23ms, Average = 13ms
Your ISP doin' traffic shaping could be a problem.
This city only has one ISP for large portions of the denser commercial and residential areas, but in one case, I just suggested my client to switch ISP's and the problem went away once they got on fiber. The cost was also mucher lower in comparison, but I think that's just due to the other ISP being the new-kids in town.
I will do a few more test sessions and see if anything becomes apparent. I do think I will try at least one more time to do it live. It's just a bit puzzling. I have a feeling it's going to be something out of my control. When it happens, I will do a ping test and see what the latency is.