Dropped Frames (Network)

[c0bbo]

Hello kind souls of the OBS forum!

I'm making this post because I think I've tried everything... I know I haven't, somehow, so I've come for help;
I've been streaming for about 6 years now and I've been preparing for a streamthon soon.
However, I got unlucky and have been experiencing heavy dropped frames and connection loss due to network pretty much every day since the start of this week.
I've read the stickied threads, tried a lot of tools and slight nudges, but nothing seems to be working great.
I saw another thread with a similar issue, so I decided to single out that part in my OBS logs before posting.

20:27:54.013: Output 'rtmp multitrack video': Total frames output: 37446 (107334 attempted)
20:27:54.013: Output 'rtmp multitrack video': Total drawn frames: 57716 (57828 attempted)
20:27:54.013: Output 'rtmp multitrack video': Number of lagged frames due to rendering lag/stalls: 112 (0.2%)
20:27:54.013: Output 'rtmp multitrack video': Number of dropped frames due to insufficient bandwidth/connection stalls: 69888 (65.1%)
20:27:54.030: [rtmp stream: 'rtmp multitrack video'] Freeing 59229 remaining packets
20:27:54.042: Video stopped, number of skipped frames due to encoding lag: 20074/50845 (39.5%)

I'm going to try a few things in that thread too, but I'm posting this now just in case there's something I've missed.
I usually use the Enhanced Broadcasting setting with no issues, but due to these issues I've turned on dynamic (Beta) and it's sort of working, not well.
Logs are below, I really appreciate the help.

 

[c0bbo]

Hello, quick update;
I ran some network drivers for my mobo,
LAN relatek pcielan + Wifi drivers (using ethernet, figured I'd just update them both)
updated them / repaired them, and the issue still persists.

I'm trying some fixes from the OBS log analyzer.
Additionally, I've also tried to reduce GPU overhead, I was using too much GPU.
So I lowered the GPU priority of those tools (in taskm and their native settings),
set OBS to perfer IPv4,
checked to my make sure my cable wasn't coming loose,
uninstalled Warudo cams, and VTS virtual cam,
and restarted the computer.

Currently it seems to be performing well.
Doing another OBS log analyzer, seems to be running okay...
Hopefully it doesn't fail the second I hit submit on this.
Thanks for the stickied post and having the OBS log analyzer.

One question I have is under my "Stats" window, it says my bitrate is 13 Mb/s,
but in the bottom right where my netcode bar is, it says 12800 kbps.
Which one is my current bitrate?
Thanks!

 

[Lawrence_SoCal]

Coming from a general desktop support perspective
- if you aren't using IPv6, I'd disable it at OS layer (basic security approach.. disable what isn't in use)
- as for bitrate... there is time averaging and 1,024 vs 1k maths.. eye roll... not sure if this is related or not... but small variances I wouldn't concern myself with
- streamlabs timeouts have long been highly correlated with network issues ... if you'd argue that PoS streamlabs web code and or plugin shouldn't impact network throughput, I'd agree... BUT it is truly far more complicated than that, so ...
A heavily loaded system, with lots of OBS Studio CPU impactful filters/effects and an error log full of streamlabs errors... easily see how an occassional network frame would drop

but 65% - what else is going on with your LAN? what are you doing for real-time network monitoring?

As for an easy way to to test if network or yoru PC/OBS Studio settings/config
- set up real time monitoring on your WAN/LAN - so you can see if actually hitting local bottleneck, or unexpected traffic, etc. if you don't do this, you are doing the equivalent of flying/driving blindfolded, and it will be very hard to know for sure and you'll spend a lot of timing simply guessing
then
- disable unnecessary OS autostart processes & reboot OS, let OS settle (monitoring via Task Mgr or similar)
- set up a OBS Studio portable install... keep it super clean, no filters/effects, plugins, browser sources, etc. now test stream... if that works fine, then focus for troubleshooting becomes your PC and its OBS Studio setup.

that's what I'd do