Deployed 1a8e633 with MkDocs version: 1.6.1

guide/downloading/index.html

@@ -3297,6 +3297,40 @@ either enum <strong>names</strong> or their <strong>values</strong>, comma-separ
 </table>
 <div class="language-shell highlight"><span class="filename">Grab HDR10 and Dolby Vision in one run</span><pre><span></span><code><span id="__span-7-1"><a id="__codelineno-7-1" name="__codelineno-7-1" href="#__codelineno-7-1"></a>unshackle<span class="w"> </span>dl<span class="w"> </span>-q<span class="w"> </span><span class="m">2160</span><span class="w"> </span>-r<span class="w"> </span>HDR10,DV<span class="w"> </span>EXAMPLE<span class="w"> </span><span class="s1">'...'</span>
 </span></code></pre></div>
+<p><code>--list</code> labels a track that carries a second format as <code>&lt;range&gt;+&lt;format&gt;</code>:</p>
+<ul>
+<li>The first part is the range that <code>-r</code> selects the track by.</li>
+<li>The second part is the format that the track also carries.</li>
+<li>The <code>+</code> only joins the two parts. unshackle writes HDR10+ as <code>HDR10P</code>, so <code>HDR10+DV</code> is HDR10 with
+  Dolby Vision, not HDR10+ with Dolby Vision.</li>
+</ul>
+<table>
+<thead>
+<tr>
+<th>Label</th>
+<th>Track</th>
+<th>Selected by</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><code>DV+HDR10P</code></td>
+<td>A Dolby Vision track that also carries HDR10+</td>
+<td><code>-r DV</code></td>
+</tr>
+<tr>
+<td><code>HDR10+DV</code></td>
+<td>An HDR10 track whose frames also carry a Dolby Vision profile 8 RPU</td>
+<td><code>-r HDR10</code></td>
+</tr>
+<tr>
+<td><code>HDR10P+DV</code></td>
+<td>An HDR10+ track whose frames also carry a Dolby Vision profile 8 RPU</td>
+<td><code>-r HDR10P</code></td>
+</tr>
+</tbody>
+</table>
+<p>The output file of a track with a Dolby Vision profile 8 RPU plays as Dolby Vision on a DV screen.</p>
 <div class="admonition warning">
 <p class="admonition-title">HYBRID requires dovi_tool</p>
 <p><code>-r HYBRID</code> makes a single hybrid track by injecting the Dolby Vision RPU
@@ -3309,10 +3343,11 @@ HEVC; a title whose HDR10/HDR10+ tracks are all in another codec fails before it
 If the hybrid step fails for one resolution, unshackle logs an error, skips that resolution
 and goes on with the other resolutions of the title. When no hybrid file at all was made,
 the title fails.</p>
-<p>A DV track that carries HDR10+ (<code>DV+HDR10P</code> in <code>--list</code>) is already a hybrid. At a resolution
-that has one, <code>-r HYBRID</code> selects the DV+HDR10P track with the highest bitrate (the lowest with
-<code>--worst</code>) and muxes it as it is, with no base track and no dovi_tool step. The other
-resolutions get a hybrid that unshackle makes.</p>
+<p>A track that is <code>DV+HDR10P</code>, <code>HDR10+DV</code> or <code>HDR10P+DV</code> in <code>--list</code> already carries Dolby Vision and an HDR10
+or HDR10+ base, so it is already a hybrid. At a resolution that has one, <code>-r HYBRID</code> selects it
+and muxes it as it is, with no base track and no dovi_tool step. A track that carries HDR10+
+comes first, then the highest bitrate (the lowest with <code>--worst</code>). The other resolutions get a
+hybrid that unshackle makes.</p>
 <p>To keep an HDR10+ deliverable <em>alongside</em> the hybrid, request both ranges:
 <code>-r HYBRID,HDR10P</code>. <code>-r HYBRID</code> on its own muxes only the merged hybrid.</p>
 </div>