8mbs Upload What Bitrate to Use Obs

This guide is specially for people with an upload-speed between around 700-1200 Kbit/s, because above this y'all shouldn't accept that much trouble at finding disarming settings (540p easily)!

Table of content: ​

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

How to calculate your bitrate: ​

Go to: www.testmy.net and perform a upload-speed-test.

You have to go along the bitrate for your game and your sound in mind, also some room for spiking.
You want to use around 70 % to eighty % of your bitrate, side by side steps give yous further advice.
I recommend ALWAYS using mono, unless you have a high enough upload speed for don't caring about the extra file size or y'all actually need to take the deviation between right and left aqueduct.
Note: Mono will requite you better quality than stereo at aforementioned bitrates, because there is just 1 channel to encode compared to the 2 channels of stereo.
And then y'all have to decrease the speed you want to condom for your game. Also you should accept a few bites left for when OBS spikes at the bitrate.

Example-calculation: ​

You accept, like me, an upload of i Mbit or roughly 1000 Kbit/southward. I recall audio quality below 64 Kbit/s is way too bad to heed to, so I took this for my stream. For me I found out, that I need around 100 Kbit/southward left for my game. Furthermore OBS' bandwidth usage varies around 35 Kbit/s above and beneath the targeted bitrate.
Then let's summate:

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

- 35 (Spikes)

801 (Bitrate) ​

This is the bitrate, yous desire to use for video-encoding.

In fact, that's pretty much exactly the bitrate I am using, which is 800 Kbit/s.
This might differ a little scrap for anybody, only it's definitely a good starting betoken. If you lot face up lags in your game, but lower the bitrate 50 Kbit/s. If it's okay, you can either keep that or try like 775 Kbit/southward and then on...

Tabular array with resolutions ​

The bitrate in the peak is the bitrate we just calculated higher up.
The slower the preset, the higher the CPU-usage.

As you lot tin can see in the "size in %"-section, presets beneath "veryfast" don't give a real advantage in the actual bitrate y'all need for a specific resolution, they will even need a slightly higher bitrate, but will give an increment in encoding-quality, even though the deviation might not exist worth it in some cases.

If you lot want to endeavor slower presets, proceed track of your CPU! ​

Yous should endeavour framerates like 24, 25, 30 and other mutual framerates.
Because I assumed a relatively high impact in bitrate for different framerates, y'all might be able to squeeze out a few more fps than in the tabular array (excepting veryfast 360p at 700 kbit/due south), merely going with higher framerates could crusade a more washed-out stream at move-scenes, so picking these settings should be condom to provide a relatively constant quality while moving.

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

Notation: Lanczos is often told to be the sharpening-filter, considering it kind of overshapens the images. In my personal opinion, at 540p the Bicubic looks better, merely this is merely 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, contour is set to high, residue is default.
I've added ultrafast, and so you tin can see, why you shouldn't use presets faster than veryfast.

The differences are minor, but you can notice an increment in detail and sharpness. (Yous can see the differences best, if you compare the workers.)
Peculiarly if you look at the right worker, you see the line on the basis being cut through for veryfast and faster.
An other good point to wait at is the outline of the building or the number in a higher place the building/ between the 1 worker and the building.

You tin notice, that the quality-differences between veryfast and faster as well as between faster and fast seem to exist 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 more: Keep rails of your CPU, while testing the slower presets! ​

Formulae: ​

If you want to summate on your own, you can either utilise my tabular array (I started at 360p with 30 FPS and a Bandwidth of 700 Kbit/due south with veryfast for a very skillful stability) or you have to figure out an own setting with a certain bandwidth, resolution and FPS, which looks fine to you lot.
However, here are the formulae:

nBW (when on the correct on the equality-sigh) = needed bandwidth
nBW (when in the formula) = new bandwidth (if yous take a faster connection than your starting signal)
nRes = new resolution
nFPS = new FPS
oBW = old bandwidth
oRes = old resolution
o FPS = old FPS

Like written in the table, these are settings for mid-motility games, like RTS. If you are playing a depression-move game, you lot might be able to get abroad with the settings for your calculated bitrate+100 Kbit/due south, for high-motion games the contrary.

Too I did cutting some resolutions and presets, because they are non every bit „good" equally the others. (They are not sufficient for these bitrates or take as well much performance) I tried to deliver a guide containing every bit much detail equally possible and needed, considering in that location are no sufficient guides out there for low bitrates in my opinion. All these is from testing, calculating and research. The formulae I mainly used are: qval, 3/four-dominion and principle of proportionality
(I tin can provide the open-role-canvass, if y'all want to calculate dissimilar bitrates and/or resolutions yourself.)

Final words:
​

I aimed to provide a relatively stable stream, rather than just a skilful looking stream at no motion!

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

Then after the couple of weeks of reading, testing and calculating, I decided to practice a curt guide on my own, which contains the most of import stuff for most users, not going likewise deep into the thing.

These settings might differ individualy, depending on your exact upload-speed, stability and your system (non only the hardware, only the software, too).

So yous might want to adjust a picayune bit here.

This should aid you, finding the correct settings rather then only tell you, what to use.

If there are any mistakes, also in content as in linguistic communication too, yous are welcome to send me a PM, so I can correct them.

I hope, this could help you guys.

curryeiver1954.blogspot.com

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

Share this post