Deployed 408ce3c0 with MkDocs version: 1.4.2

gh-pages
2 years ago
parent 25e15cf9a2
commit dbc16bb941

@ -997,9 +997,10 @@ it gets imported correctly and isn't incorrectly matched as HDTV or WEB-DL etc.<
</details> </details>
<hr/> <hr/>
<h2 id="original-title-vs-original-filename">Original Title vs Original Filename<a class="headerlink" href="#original-title-vs-original-filename" title="Permanent link"></a></h2> <h2 id="original-title-vs-original-filename">Original Title vs Original Filename<a class="headerlink" href="#original-title-vs-original-filename" title="Permanent link"></a></h2>
<p>If you want to keep the original release name that holds all the info of the file then I suggest to use <code>{Original Title}</code> over <code>{Original Filename}</code></p> <p>Another option is to use <code>{Original Title}</code> rather than the recommeneded naming scheme outlined aboove. <code>{Original Title}</code> will use the title of the release which will contain all of the information included in the release itself. The benefit of this naming scheme is to prevent download loops which can occur on import when there is a discrepancy in the release title compared to the contents of the file itself (for example, if the release title says DTS-ES but the contents are actually DTS). The downside is less flexibility with how the files are named.</p>
<p>If using this alternate naming scheme I suggest using <code>{Original Title}</code> over <code>{Original Filename}</code></p>
<p>Why?</p> <p>Why?</p>
<p>The filename can be Obscured where the Release naming isn't. Especially when you use Usenet.</p> <p>The filename can be Obscured where the Release naming isn't, especially when you use Usenet.</p>
<p><code>{Original Title}</code> =&gt; <code>The.Movie.Title.2010.REMASTERED.1080p.BluRay.x264-GROUP</code></p> <p><code>{Original Title}</code> =&gt; <code>The.Movie.Title.2010.REMASTERED.1080p.BluRay.x264-GROUP</code></p>
<p><code>{Original Filename}</code> =&gt; <code>group-karatekid-1080p</code> or <code>lchd-tkk1080p</code> or <code>t1i0p3s7i8yuti</code></p> <p><code>{Original Filename}</code> =&gt; <code>group-karatekid-1080p</code> or <code>lchd-tkk1080p</code> or <code>t1i0p3s7i8yuti</code></p>
<hr/> <hr/>
@ -1041,7 +1042,7 @@ it gets imported correctly and isn't incorrectly matched as HDTV or WEB-DL etc.<
<small> <small>
Last update: Last update:
<span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">October 1, 2022 12:41:02</span> <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">December 28, 2022 21:20:58</span>
</small> </small>
</div> </div>
<footer class="sponsorship"> <footer class="sponsorship">

@ -1106,9 +1106,10 @@ it gets imported correctly and isn't incorrectly matched as HDTV or WEB-DL etc.<
<p><a class="glightbox" data-desc-position="bottom" data-height="auto" data-width="100%" href="../images/results.png"><img alt="results" src="../images/results.png"/></a></p> <p><a class="glightbox" data-desc-position="bottom" data-height="auto" data-width="100%" href="../images/results.png"><img alt="results" src="../images/results.png"/></a></p>
<hr/> <hr/>
<h2 id="original-title-vs-original-filename">Original Title vs Original Filename<a class="headerlink" href="#original-title-vs-original-filename" title="Permanent link"></a></h2> <h2 id="original-title-vs-original-filename">Original Title vs Original Filename<a class="headerlink" href="#original-title-vs-original-filename" title="Permanent link"></a></h2>
<p>If you want to keep the original release name that holds all the info of the file then I suggest to use <code>{Original Title}</code> over <code>{Original Filename}</code></p> <p>Another option is to use <code>{Original Title}</code> rather than the recommeneded naming scheme outlined aboove. <code>{Original Title}</code> will use the title of the release which will contain all of the information included in the release itself. The benefit of this naming scheme is to prevent download loops which can occur on import when there is a discrepancy in the release title compared to the contents of the file itself (for example, if the release title says DTS-ES but the contents are actually DTS). The downside is less flexibility with how the files are named.</p>
<p>If using this alternate naming scheme I suggest using <code>{Original Title}</code> over <code>{Original Filename}</code></p>
<p>Why?</p> <p>Why?</p>
<p>The filename can be Obscured where the Release naming isn't. Especially when you use Usenet.</p> <p>The filename can be Obscured where the Release naming isn't, especially when you use Usenet.</p>
<p><code>{Original Title}</code> =&gt; <code>The.Series.Title.S01E01.Episode.Title.1080p.AMZN.WEB-DL.DDP5.1.H.264-RlsGrp</code></p> <p><code>{Original Title}</code> =&gt; <code>The.Series.Title.S01E01.Episode.Title.1080p.AMZN.WEB-DL.DDP5.1.H.264-RlsGrp</code></p>
<p><code>{Original Filename}</code> =&gt; <code>show episode 1-1080p</code> or <code>lchd-tkk1080p</code> or <code>t1i0p3s7i8yuti</code></p> <p><code>{Original Filename}</code> =&gt; <code>show episode 1-1080p</code> or <code>lchd-tkk1080p</code> or <code>t1i0p3s7i8yuti</code></p>
<hr/> <hr/>
@ -1128,7 +1129,7 @@ it gets imported correctly and isn't incorrectly matched as HDTV or WEB-DL etc.<
<small> <small>
Last update: Last update:
<span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">December 10, 2022 00:25:33</span> <span class="git-revision-date-localized-plugin git-revision-date-localized-plugin-datetime">December 28, 2022 21:21:46</span>
</small> </small>
</div> </div>
<footer class="sponsorship"> <footer class="sponsorship">

File diff suppressed because one or more lines are too long

Binary file not shown.
Loading…
Cancel
Save