---
title: Accidental NVENC Discoveries
category: Blog
tags: ["NVIDIA", "NVENC", "H264", "H265", 'WordPress Archive']
---

<p class="block">While testing new updates to the VES testing suite, I discovered some weird behavior in NVENC. Here's a list of them, maybe NVIDIA can shed some light on it:</p><!--more-->

<h2 class="block">G-Sync affects NVENC Encoding Speed</h2>

<p class="block">For unknown reasons G-Sync affects the rate of encoding provided by NVENC, no matter how you submit frames to it. So in case you're hitting "Encoding Overloaded" in OBS Studio for no actual reason, try disabling G-Sync globally.</p>

<h2 class="block">Constant Quality is a lie?</h2>

<p class="block">The "Constant Quality" encoding method often used for archival and also often mistaken for an alternative to x264 CRF has a default bitrate limit. For H.264/AVC the maximum bitrate it will pick is 135mbit/s, while for H.265/HEVC it will pick is 25mbit/s. You can affect these limits by explicitly setting the maxBitRate ("-maxrate" in FFmpeg) and vbvBufferSize ("-bufsize" in FFmpeg) to a higher value.</p>

<ul class="block">
	<li>H.264/AVC<ul>
			<li>6.2: <code>-maxrate 800000k -bufsize 800000k</code></li>
			<li>6.1: <code>-maxrate 480000k -bufsize 480000k</code></li>
			<li>6.0/5.2: <code>-maxrate 240000k -bufsize 240000k</code></li>
			<li>5.0: <code>-maxrate 135000k -bufsize 135000k</code> (Driver Default)</li>
		</ul>
	</li>
	<li>H.265/HEVC <ul>
			<li>6.2: <ul>
					<li>High: <code>-tier high -maxrate 800000k -bufsize 800000k</code></li>
					<li>Main: <code>-tier main -maxrate 240000k -bufsize 240000k</code></li>
				</ul>
			</li>
			<li>6.1:<ul>
					<li>High: <code>-tier high -maxrate 480000k -bufsize 480000k</code></li>
					<li>Main: <code>-tier main -maxrate 120000k -bufsize 120000k</code></li>
				</ul>
			</li>
			<li>6.0/5.2:<ul>
					<li>High: <code>-tier high -maxrate 240000k -bufsize 240000k</code></li>
					<li>Main: <code>-tier main -maxrate 60000k -bufsize 60000k</code></li>
				</ul>
			</li>
			<li>5.1:<ul>
					<li>High: <code>-tier high -maxrate 160000k -bufsize 160000k</code></li>
					<li>Main: <code>-tier main -maxrate 40000k -bufsize 40000k</code></li>
				</ul>
			</li>
			<li>5.0:<ul>
					<li>High: <code>-tier high -maxrate 100000k -bufsize 100000k</code></li>
					<li>Main: <code>-tier main -maxrate 25000k -bufsize 25000k</code> (Driver Default)</li>
				</ul>
			</li>
		</ul>
	</li>
</ul>

<p class="block">Please note that doing this means that you will need a more modern decoder to view or edit the footage. I still recommend to go with the highest possible maximum bitrate in order to get the best out of your footage.</p>

<h2 class="block">H.265/HEVC struggles representing Foliage</h2>

<p class="block">Even with the above maximum bitrate fix applied, the HEVC NVENC encoder has a weird affinity to just murder foliage for no actual reason. It seems that there is a noise pattern detection method that freaks out once the foliage gets too large, and fails to adapt to the fact that the foliage now has even more detail than before.</p>