From dbc16bb9419287e6492b2477ae54f34c3e18eddc Mon Sep 17 00:00:00 2001 From: <> Date: Wed, 28 Dec 2022 21:28:31 +0000 Subject: [PATCH] Deployed 408ce3c0 with MkDocs version: 1.4.2 --- .../index.html | 7 ++++--- .../index.html | 7 ++++--- search/search_index.json | 2 +- sitemap.xml.gz | Bin 1032 -> 1032 bytes 4 files changed, 9 insertions(+), 7 deletions(-) diff --git a/Radarr/Radarr-recommended-naming-scheme/index.html b/Radarr/Radarr-recommended-naming-scheme/index.html index ebaa3f2d7..90829b816 100644 --- a/Radarr/Radarr-recommended-naming-scheme/index.html +++ b/Radarr/Radarr-recommended-naming-scheme/index.html @@ -997,9 +997,10 @@ it gets imported correctly and isn't incorrectly matched as HDTV or WEB-DL etc.<
If you want to keep the original release name that holds all the info of the file then I suggest to use {Original Title}
over {Original Filename}
Another option is to use {Original Title}
rather than the recommeneded naming scheme outlined aboove. {Original Title}
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.
If using this alternate naming scheme I suggest using {Original Title}
over {Original Filename}
Why?
-The filename can be Obscured where the Release naming isn't. Especially when you use Usenet.
+The filename can be Obscured where the Release naming isn't, especially when you use Usenet.
{Original Title}
=> The.Movie.Title.2010.REMASTERED.1080p.BluRay.x264-GROUP
{Original Filename}
=> group-karatekid-1080p
or lchd-tkk1080p
or t1i0p3s7i8yuti