---
layout: default
title: "High Quality Streaming with NVIDIA® NVENC (in OBS® Studio)"
---

{% capture content %}Streaming with more than one PC has been the leader in H.264 encoding for years, but NVIDIAs Turing and Ampere generation has put a significant dent into that lead. The new generation of GPUs with the brand new encoder brought comparable quality x264 medium – if you can find a GPU that is. Let’s take a look at what’s needed to set up your stream for massively improved quality.{% endcapture %}{% include blocks/paragraph.liquid content=content %}

{% capture content %}<b>The guide has been updated for:</b><br/>
StreamFX v0.11 and OBS Studio 27.0{% endcapture %}{% include blocks/paragraph.liquid align="center" content=content %}

{% capture content %}Setting up NVENC (for Streaming){% endcapture %}{% include blocks/heading.liquid content=content level=1 %}
{% capture content %}Modern OBS Studio has two ways to achieve the expected quality: the built-in NVENC H.264 (new) and the addition from StreamFX called NVIDIA NVENC H.264/AVC (via FFmpeg). Both Options can achieve similar quality to x264 medium, but the latter is able to exceed that and rival x264 medium/slow in various situations. Whichever you pick, both of them support zero-copy encoding, and they’re both valid options for streaming.{% endcapture %}{% include blocks/paragraph.liquid content=content %}

{% capture content %}Built-In: OBS Studio NVENC H.264 (new){% endcapture %}{% include blocks/heading.liquid content=content level=3 %}
{% capture content %}The built-in NVENC option in OBS Studio is by far the simplest option and will give you almost identical quality on Maxwell, Pascal, Turing and Ampere, though Turing and Ampere will make use of the new improvements of the NVENC chip. Maxwell and Pascal users can expect to reach x264 veryfast/faster-like quality, while Turing and Ampere users can expect to hit fast/medium-like quality. Below are the settings you need to set:{% endcapture %}{% include blocks/paragraph.liquid content=content %}
{% capture content %}
<thead><tr>
	<th>Option</th>
	<th>Kepler, Maxwell & Pascal</th>
	<th>Turing & Ampere</th>
</tr></thead>
<tr>
	<td>Preset</td>
	<td>Quality</td>
	<td>Max Quality<br/><b>or:</b> Quality</td>
</tr>
<tr>
	<td>Profile</td>
	<td>high</td>
	<td>high</td>
</tr>
<tr>
	<td>Look-ahead</td>
	<td>Enabled/Checked</td>
	<td>Enabled/checked</td>
</tr>
<tr>
	<td>Psycho-Visual Tuning</td>
	<td>Enabled/Checked</td>
	<td>Enabled/Checked</td>
</tr>
<tr>
	<td>Max B-Frames</td>
	<td>1 or 2</td>
	<td>3 or 4</td>
</tr>
{% endcapture %}{% include blocks/table.liquid content=content caption="Best built-in NVENC settings." %}

{% capture content %}StreamFX: NVIDIA NVENC H.264/AVC (via FFmpeg){% endcapture %}{% include blocks/heading.liquid content=content level=3 %}
{% capture content %}If you’re new to StreamFX’s NVENC integration, it will most likely overwhelm you with the settings it offers. But thanks to all those settings, you can actually go above the default quality by quite a significant amount. Note that I will only cover critical settings, as other settings like Bitrate, Buffer Size and Key Frame Interval are explained elsewhere. {% endcapture %}{% include blocks/paragraph.liquid content=content %}
{% capture content %}
<thead><tr>
	<th>Option</th>
	<th>Kepler, Maxwell & Pascal</th>
	<th>Turing & Ampere</th>
</tr></thead>
<tr>
	<td>Preset</td>
	<td colspan=2>High Quality</td>
</tr>
<tr>
	<td><b>H264</b></td>
	<td></td>
	<td></td>
</tr>
<tr>
	<td>► Profile</td>
	<td colspan=2>High</td>
</tr>
<tr>
	<td>► Level</td>
	<td colspan=2>Automatic</td>
</tr>
<tr>
	<td><b>Rate Control Options</b></td>
	<td></td>
	<td></td>
</tr>
<tr>
	<td>► Mode</td>
	<td colspan=2>High Quality Constant Bitrate</td>
</tr>
<tr>
	<td>► Two Pass</td>
	<td>Disabled</td>
	<td>Enabled</td>
</tr>
<tr>
	<td>► Look Ahead</td>
	<td>8 - 12</td>
	<td>16 - 32</td>
</tr>
<tr>
	<td>► Adaptive I-Frames</td>
	<td colspan=2>Enabled</td>
</tr>
<tr>
	<td>► Adaptive B-Frames</td>
	<td colspan=2>Enabled</td>
</tr>
<tr>
	<td><b>Adaptive Quantization</b></td>
	<td></td>
	<td></td>
</tr>
<tr>
	<td>► Spatial (AQ)</td>
	<td colspan=2>Enabled</td>
</tr>
<tr>
	<td>► Spatial (AQ) Strength</td>
	<td colspan=2>&lt;Any&gt;</td>
</tr>
<tr>
	<td>► Temporal (AQ)</td>
	<td colspan=2>Enabled</td>
</tr>
<tr>
	<td><b>Other Options</b></td>
	<td></td>
	<td></td>
</tr>
<tr>
	<td>► Maximum B-Frames</td>
	<td>1 or 2</td>
	<td>3 or 4</td>
</tr>
<tr>
	<td>► B-Frame References</td>
	<td colspan=2>"middle"</td>
</tr>
<tr>
	<td>► Zero Latency</td>
	<td colspan=2>Disabled</td>
</tr>
<tr>
	<td>► Weighted Prediction</td>
	<td colspan=2>Disabled</td>
</tr>
<tr>
	<td>► Non-reference P-Frames</td>
	<td colspan=2>Enabled</td>
</tr>
<tr>
	<td>► Reference Frames</td>
	<td colspan=2>-1 (Automatic)</td>
</tr>
<tr>
	<td><b>FFmpeg Options</b> (Optional)</td>
	<td></td>
	<td></td>
</tr>
<tr>
	<td>► Custom Settings</td>
	<td></td>
	<td></td>
</tr>
{% endcapture %}{% include blocks/table.liquid content=content caption="Ideal NVENC Settings for StreamFX's NVENC." %}
{% capture content %}For certain platforms it may be necessary to turn off Adaptive I-Frames due to how their internal processing works, such as Twitch. This has a drastic quality impact and should only be done if you rely on that platform alone to reach your audience.{% endcapture %}{% include blocks/paragraph.liquid content=content %}

{% capture content %}Setting up Resolution and Framerate to match the Bitrate{% endcapture %}{% include blocks/heading.liquid content=content level=1 %}
{% capture content %}It is no secret than H.264/AVC is an outdated codec and that platforms should have paved the way for better codecs a long time ago, but it is the solution that we are stuck with until AV1 is adopted by the masses. So in order to get the best quality out of our stream, we should aim to also set up our stream according to the bitrate and codec we use. Below is the average result of a few hundred thousand tests at various resolutions and bitrates, according to PSNR and VMAF (weighted PSNR 30:70 VMAF):{% endcapture %}{% include blocks/paragraph.liquid content=content %}
{% capture content %}
<thead><tr>
	<th>Resolution</th>
	<th>3.5mbit<br/>30 FPS</th>
	<th>3.5mbit<br/>60 FPS</th>
	<th>6.0mbit<br/>30 FPS</th>
	<th>6.0mbit<br/>60 FPS</th>
	<th>8.5mbit<br/>30 FPS</th>
	<th>8.5mbit<br/>60 FPS</th>
</tr></thead>
<tr>
	<td>640x360</td>
	<td>6</td>
	<td>6</td>
	<td>8</td>
	<td>7</td>
	<td>9</td>
	<td>8</td>
</tr>
<tr>
	<td>960x540</td>
	<td>5</td>
	<td>4</td>
	<td>6</td>
	<td>5</td>
	<td>7</td>
	<td>7</td>
</tr>
<tr>
	<td>1280x720</td>
	<td>4</td>
	<td>3</td>
	<td>4</td>
	<td>3</td>
	<td>5</td>
	<td>4</td>
</tr>
<tr>
	<td>1536x864</td>
	<td>3</td>
	<td>2</td>
	<td>4</td>
	<td>3</td>
	<td>4</td>
	<td>4</td>
</tr>
<tr>
	<td>1600x900</td>
	<td>3</td>
	<td>2</td>
	<td>3</td>
	<td>2</td>
	<td>4</td>
	<td>3</td>
</tr>
<tr>
	<td>1920x1080</td>
	<td>2</td>
	<td>1</td>
	<td>2</td>
	<td>2</td>
	<td>3</td>
	<td>3</td>
</tr>
{% endcapture %}{% include blocks/table.liquid content=content caption="Rating from 1 to 10 based on VMAF and PSNR, weighted towards producing useful ranges. Tests performed with x264 slow.<br/>A 10 is perfect, 9 is near lossless, 8 is indistinguishable, 7 is high quality, 5 is acceptable quality and 3 is watchable." %}
{% capture content %}Please note that watchable in video encoding means that you can decode information within it with reasonable accuracy, instead of it having turned to full garbage. Higher resolutions than 1920×1080 were omitted from the table as the rows would be filled with values between 0 and 1, which just are not very useful to us.{% endcapture %}{% include blocks/paragraph.liquid content=content %}
{% capture content %}This means that at 3.5mbit, the highest resolution and framerate for a variety streamer is 1280×720 at 30 FPS, or 960×540 at 60 FPS. The equation shifts slightly for 6.0mbit, where you can either go for 1536×864 at 30 FPS or 1280×720 at 60 FPS. Finally at 8.5mbit you are looking at a maximum resolution and framerate of 1920×1080 at 30 FPS or 1536×864 at 60 FPS.{% endcapture %}{% include blocks/paragraph.liquid content=content %}

{% capture content %}Final Words{% endcapture %}{% include blocks/heading.liquid content=content level=3 %}
{% capture content %}In the past few years NVIDIA has made massive improvements to their encoder, which has evened the playing field far beyond what was expected. With no need to transfer frames from the GPU to the CPU, and quality comparable to x264 medium (or better), NVIDIAs Turing NVENC is pushing the boundaries of what is possible in a single consumer PC.{% endcapture %}{% include blocks/paragraph.liquid content=content %}
{% capture content %}Whether you use it or not is entirely up to you however. If you already have a working Dual-PC setup that can achieve x264 medium (or better) quality, then you don’t gain much from moving to Turing NVENC. But if you’re currently stuck on anything below x264 medium, or have a Turing GPU ready to test it out – why not give it a shot?{% endcapture %}{% include blocks/paragraph.liquid content=content %}

{% capture content %}Video Examples{% endcapture %}{% include blocks/heading.liquid content=content level=1 %}
