@@ -2929,8 +2929,8 @@ <h2>Video</h2>
29292929 support this, then it will be treated as <tt class="docutils literal">cpu</tt>, regardless of the setting.
29302930 Currently, only <tt class="docutils literal"><span class="pre">gpu-next</span></tt> supports film grain application.</p>
29312931 </dd>
2932- <dt><tt class="docutils literal"><span class="pre">--vd-lavc-dr=<yes|no></span></tt></dt>
2933- <dd><p class="first">Enable direct rendering (default: yes ). If this is set to <tt class="docutils literal">yes</tt>, the
2932+ <dt><tt class="docutils literal"><span class="pre">--vd-lavc-dr=<auto| yes|no></span></tt></dt>
2933+ <dd><p class="first">Enable direct rendering (default: auto ). If this is set to <tt class="docutils literal">yes</tt>, the
29342934 video will be decoded directly to GPU video memory (or staging buffers).
29352935 This can speed up video upload, and may help with large resolutions or
29362936 slow hardware. This works only with the following VOs:</p>
@@ -2940,6 +2940,9 @@ <h2>Video</h2>
29402940 <li><tt class="docutils literal">libmpv</tt>: The libmpv render API has optional support.</li>
29412941 </ul>
29422942 </blockquote>
2943+ <p>The <tt class="docutils literal">auto</tt> option will try to guess whether DR can improve performance
2944+ on your particular hardware. Currently this enables it on AMD or NVIDIA
2945+ if using OpenGL or unconditionally if using Vulkan.</p>
29432946 <p class="last">Using video filters of any kind that write to the image data (or output
29442947 newly allocated frames) will silently disable the DR code path.</p>
29452948 </dd>
0 commit comments