Obs Good Upload Speed but Unstable 30 Fps

This guide is especially for people with an upload-speed between effectually 700-1200 Kbit/s, because above this you shouldn't take that much trouble at finding convincing settings (540p easily)!

Table of content: ​

• How to summate your bitrate
• Case-calculation
• Table of different upload-speeds with resolutions and presets
• Presets: Screenshot-comparison
• Formulae
• Some notes
• Final words

How to calculate your bitrate: ​

Become to: www.testmy.cyberspace and perform a upload-speed-test.

You have to keep the bitrate for your game and your audio in mind, too some room for spiking.
You want to use around 70 % to 80 % of your bitrate, next steps give you further communication.
I recommend E'er using mono, unless you accept a high enough upload speed for don't caring about the extra file size or y'all actually need to have the difference betwixt right and left channel.
Note: Mono will give you better quality than stereo at same bitrates, because at that place is only 1 aqueduct to encode compared to the 2 channels of stereo.
And then you accept to subtract the speed y'all want to rubber for your game. Besides yous should have a few bites left for when OBS spikes at the bitrate.

Instance-adding: ​

You lot take, similar me, an upload of 1 Mbit or roughly yard Kbit/s. I think audio quality below 64 Kbit/southward is way too bad to listen to, so I took this for my stream. For me I institute out, that I need around 100 Kbit/southward left for my game. Furthermore OBS' bandwidth usage varies around 35 Kbit/south above and below the targeted bitrate.
So let'southward calculate:

1000 (Upload.speed)
- 100 (Game/Internet)
- 64 (Audio)

- 35 (Spikes)

801 (Bitrate) ​

This is the bitrate, you desire to utilise for video-encoding.

In fact, that'south pretty much exactly the bitrate I am using, which is 800 Kbit/s.
This might differ a piffling bit for anybody, but information technology's definitely a practiced starting point. If you lot face up lags in your game, just lower the bitrate l Kbit/s. If information technology'southward okay, you tin either go on that or try like 775 Kbit/s and and so on...

Table with resolutions ​

The bitrate in the acme is the bitrate we just calculated above.
The slower the preset, the college the CPU-usage.

As you tin can come across in the "size in %"-section, presets beneath "veryfast" don't give a real advantage in the actual bitrate you lot need for a specific resolution, they will fifty-fifty demand a slightly higher bitrate, merely volition requite an increase in encoding-quality, even though the difference might not be worth it in some cases.

If you desire to try slower presets, continue track of your CPU! ​

You should endeavour framerates similar 24, 25, 30 and other common framerates.
Because I assumed a relatively high bear on in bitrate for different framerates, you might be able to squeeze out a few more fps than in the table (excepting veryfast 360p at 700 kbit/south), but going with higher framerates could crusade a more washed-out stream at motion-scenes, and so picking these settings should exist rubber to provide a relatively constant quality while moving.

Also try to use Lanczos or Bicubic filter for downscaling if possible, because it will provide much more sharpness for low performance cost! ​

Annotation: Lanczos is often told to be the sharpening-filter, because it kind of overshapens the images. In my personal opinion, at 540p the Bicubic looks better, but this is just a preference!

Presets: Screenshot-Comparison ​

Here are some screenshots. They are all at exactly the same settings except the preset.
These are all 432p @ 30 fps and 800 Kbit/s video-bitrate, profile is set to loftier, residual is default.
I've added ultrafast, and then you tin can meet, why y'all shouldn't use presets faster than veryfast.

The differences are minor, merely you tin notice an increase in detail and sharpness. (You tin see the differences best, if you compare the workers.)
Especially if you look at the right worker, yous see the line on the ground being cut through for veryfast and faster.
An other skilful indicate to look at is the outline of the edifice or the number above the edifice/ between the ane worker and the building.

You can notice, that the quality-differences between veryfast and faster as well every bit between faster and fast seem to be the biggest
.

Therefore I do recommend using faster or fast.

​

(most of your systems should be able to handle this, due to the low resolution we are using.)

But once again: Continue track of your CPU, while testing the slower presets! ​

Formulae: ​

If y'all want to calculate on your own, you tin can either use my tabular array (I started at 360p with 30 FPS and a Bandwidth of 700 Kbit/south with veryfast for a very good stability) or yous take to figure out an ain setting with a certain bandwidth, resolution and FPS, which looks fine to you.
However, hither are the formulae:

nBW (when on the right on the equality-sigh) = needed bandwidth
nBW (when in the formula) = new bandwidth (if you accept a faster connectedness than your starting point)
nRes = new resolution
nFPS = new FPS
oBW = old bandwidth
oRes = old resolution
o FPS = old FPS

Similar written in the tabular array, these are settings for mid-motion games, like RTS. If yous are playing a depression-motility game, y'all might be able to get abroad with the settings for your calculated bitrate+100 Kbit/south, for high-motion games the opposite.

Also I did cut some resolutions and presets, considering they are non equally „skillful" as the others. (They are not sufficient for these bitrates or have too much performance) I tried to deliver a guide containing equally much detail as possible and needed, because there are no sufficient guides out at that place for low bitrates in my opinion. All these is from testing, calculating and research. The formulae I mainly used are: qval, three/4-dominion and principle of proportionality
(I can provide the open-office-sail, if yous desire to calculate different bitrates and/or resolutions yourself.)

Last words:
​

I aimed to provide a relatively stable stream, rather than merely a good looking stream at no motility!

I was struggling, finding the right settings for my stream and nearly of the "guides" on the internet for my low upload speed didn't convince me at all.

And so subsequently the couple of weeks of reading, testing and calculating, I decided to do a brusk guide on my own, which contains the well-nigh important stuff for almost users, not going as well deep into the matter.

These settings might differ individualy, depending on your exact upload-speed, stability and your arrangement (not only the hardware, but the software, as well).

So you might want to suit a little fleck here.

This should assist you, finding the right settings rather and then just tell you, what to use.

If in that location are any mistakes, equally well in content as in linguistic communication too, you are welcome to send me a PM, so I can correct them.

I hope, this could help yous guys.

marchandannital.blogspot.com

Source: https://obsproject.com/forum/resources/low-upload-speed-how-to-find-the-right-settings.185/

Share this post