Question / Help KB/S mismatch....

[Brano11]

Good evening all, I have been using OBS for about a month now to stream with Twitch. I have gone through all the settings, output, video, etc etc but I am still having issues with the KB/S. I have it set for 2500 bitrate with a custom buffer of 5000 currently, but I am seeing spikes up to 6000 kb/s and RIGHT after it does that it will drop to the low triple digits and cause massive dropped frames, even sometimes dropping all the way to 0. I have tried multiple bitrate numbers with and without custom buffers, different FPS values, 1080 and 720HD, different twitch streaming servers but still having a major issue it suddenly tanking.

ISP wise I run business fiber optics 200 down / 20 up and speed tests show those numbers with 8 MS ping. I have contacted the ISP and they are putting my modem on "modem watch" where it will ping the ISP servers once a minute and they can monitor how much packet loss is happening, if any, which going back a day or so it seems the only packet loss occurs when I begin using OBS studio. I have uploaded ALL the log files I have so far, if anybody could take a look at them and see if you notice anything in settings that could be causing this issue.

Forgive me if im not explaining it very clear, as i have already taken my sleep aid medicine and am typing this now lol. If it needs more explanation, I will write it more clear when I wake up in the morning =).

CURRENT LOG: https://gist.github.com/f5e0bf0949d95d42f97f1bd02b4fd69d (already dropped 39008 frames from 26 minute run time)

LAST LOG https://gist.github.com/0e6ba8a5505d1ccd980abb5e4a2c7aab

 

[RytoEX]

I'm pretty sure custom buffer size is known to cause bitrate spikes. I know you said it happens without, but you should probably disable it anyway. Try running the Twitch Bandwith Test tool using a Medium Test Duration for your region with a 64k TCP Window Size, and post a screenshot of the results here.

Also, you're trying to stream 1080p@48f on 2500 Kbps? I don't think that'll work very well. You'll probably need to try 1080p@30f or 720p@60f, depending on which is more important to you (resolution or framerate).

 

[Beardedbob]

Hi,

in the log its showing "Number of dropped frames due to insufficient bandwidth/connection stalls: 5194 (60.4%)" though given your on "ISP wise I run business fiber optics 200 down / 20 up" then this should be fine.

Do you have Lan drop outs?

Have you run the twitch bandwidth test tool? if not it can be located here http://twitch-tv-tips.blogspot.co.uk/2016/05/bandwidth-testing-tool.html

also have you tried using a different twitch server?

 

[Brano11]

I'm pretty sure custom buffer size is known to cause bitrate spikes. I know you said it happens without, but you should probably disable it anyway. Try running the Twitch Bandwith Test tool using a Medium Test Duration for your region with a 64k TCP Window Size, and post a screenshot of the results here.

Also, you're trying to stream 1080p@48f on 2500 Kbps? I don't think that'll work very well. You'll probably need to try 1080p@30f or 720p@60f, depending on which is more important to you (resolution or framerate).

So after trying the medium test with 64k TCP window size I got MUCH better bandwidth from the twitch test. How do I go about changing the TCP size in OBS?

http://imgur.com/a/uJ1on

 

[RytoEX]

You can't change it. OBS Studio uses 64k anyway, which is why I said to use that for the test. It's in the post I linked:

Try using TwitchTest with a 64kb TCP Window. This is currently what Studio uses, it doesn't have dynamic tuning like Classic yet.

You're already using the Dallas server, which should be the best choice for you, unless you have some service disruptions along that route (which you'd likely never know about). You can try Chicago or San Francisco as a temporary test, but Dallas should give you the best service.