From 36f61ddf665d25264b4b74587b6a0c2b23fea757 Mon Sep 17 00:00:00 2001 From: yammes08 <111231042+yammes08@users.noreply.github.com> Date: Sun, 8 Jan 2023 16:50:20 +0000 Subject: [PATCH 1/4] Update to match Sonarr Word boundary added before (Blu[-_. ]?ray|BD|HD[-_. ]?DVD) --- docs/json/radarr/cf/br-disk.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/json/radarr/cf/br-disk.json b/docs/json/radarr/cf/br-disk.json index 965f3472c..ff62e4ecf 100644 --- a/docs/json/radarr/cf/br-disk.json +++ b/docs/json/radarr/cf/br-disk.json @@ -10,7 +10,7 @@ "negate": false, "required": true, "fields": { - "value": "^(?!.*\\b((? Date: Sun, 8 Jan 2023 16:51:25 +0000 Subject: [PATCH 2/4] Add note re: preferred score for file sizes --- docs/Sonarr/Sonarr-Quality-Settings-File-Size.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/Sonarr/Sonarr-Quality-Settings-File-Size.md b/docs/Sonarr/Sonarr-Quality-Settings-File-Size.md index 6e8ef990e..35c542a22 100644 --- a/docs/Sonarr/Sonarr-Quality-Settings-File-Size.md +++ b/docs/Sonarr/Sonarr-Quality-Settings-File-Size.md @@ -80,4 +80,11 @@ I only do WEB-DL myself for TV shows because in my opinion WEB-DL is the sweet s | {{ sonarr['quality-size']['anime']['qualities'][17]['quality'] }} | {{ sonarr['quality-size']['anime']['qualities'][17]['min'] }} | {{ sonarr['quality-size']['anime']['qualities'][17]['max'] }} | | {{ sonarr['quality-size']['anime']['qualities'][18]['quality'] }} | {{ sonarr['quality-size']['anime']['qualities'][18]['min'] }} | {{ sonarr['quality-size']['anime']['qualities'][18]['max'] }} | +!!! note + The reason why you don't see the `Preferred` score in the table above is because we want max quality anyway. So set it as high as possible. + + The highest preferred quality you can manually enter is 1 less than the Maximum quality. If you use the slider, the preferred quality can be up to 5 lesser than the Maximum quality. + + Make sure you have enabled 'Show Advanced' in Sonarr, if you don't see a provision to enter the scores, under the Quality settings. + --8<-- "includes/support.md" From 801a4e1fdf982d157036eeae7944f2809558fa4a Mon Sep 17 00:00:00 2001 From: yammes08 <111231042+yammes08@users.noreply.github.com> Date: Mon, 9 Jan 2023 01:02:46 +0000 Subject: [PATCH 3/4] Fix 'aboove' typo --- docs/Radarr/Radarr-recommended-naming-scheme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Radarr/Radarr-recommended-naming-scheme.md b/docs/Radarr/Radarr-recommended-naming-scheme.md index 662e0e415..c7cb9838c 100644 --- a/docs/Radarr/Radarr-recommended-naming-scheme.md +++ b/docs/Radarr/Radarr-recommended-naming-scheme.md @@ -65,7 +65,7 @@ For Jellyfin/Emby: ## Original Title vs 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. +Another option is to use `{Original Title}` rather than the recommeneded naming scheme outlined above. `{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}` From ead6ae434f86a0dec8d78693e37956fbb3dcee4c Mon Sep 17 00:00:00 2001 From: yammes08 <111231042+yammes08@users.noreply.github.com> Date: Mon, 9 Jan 2023 01:03:22 +0000 Subject: [PATCH 4/4] Fix typo ('aboove') --- docs/Sonarr/Sonarr-recommended-naming-scheme.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Sonarr/Sonarr-recommended-naming-scheme.md b/docs/Sonarr/Sonarr-recommended-naming-scheme.md index da743ac6a..7974270f1 100644 --- a/docs/Sonarr/Sonarr-recommended-naming-scheme.md +++ b/docs/Sonarr/Sonarr-recommended-naming-scheme.md @@ -146,7 +146,7 @@ RESULTS: ## Original Title vs 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. +Another option is to use `{Original Title}` rather than the recommeneded naming scheme outlined above. `{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}`