Mirrors/Radarr
1
0
Fork 0
mirror of https://github.com/Radarr/Radarr.git synced 2024-11-19 17:32:38 +01:00
Code Issues Releases Wiki Activity

Updated Custom Formats Aphrodite (markdown)

RhinoRhys 2020-05-09 08:30:48 +01:00
parent 1bfe8f2338
commit 1664c303b2
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Custom-Formats-Aphrodite.md

@ -3,16 +3,20 @@
Custom formats have been reworked significantly in Aphrodite. They are now calculated on-the-fly instead of being stored in the database, so they update as soon as you change the definitions. Custom formats have been reworked significantly in Aphrodite. They are now calculated on-the-fly instead of being stored in the database, so they update as soon as you change the definitions.
## Conditions ## Conditions
A custom format in v2 was made up of one or more Format Tags, defined using a special string format. These are replaced by 'Conditions' in Aphrodite which are specified in the UI. A custom format in v2 was made up of one or more Format Tags, defined using a special string format. These have been renamed to 'Conditions' in Aphrodite which are now created through a far more user-friendly menu in the UI, first selecting the Type (formerly indicated by the Prefix), then given checkboxes for Modifiers and a dropdown of possible Values or a text input field where applicable.
All conditions have two possible modifiers: All conditions have two possible modifiers:
- **Negate** means that the match is inverted, so the condition is satisfied if and only if the non-negated condition is not satisfied - **Negate** means that the match is inverted, so the condition is satisfied if and only if the non-negated condition is not satisfied
- **Required** means that this condition must be satisfied for the custom format to apply. If a custom format has multiple conditions of the same type then only one needs to match for the custom format to apply. Enabling this option means that in addition this specific condition must be satisfied for the custom format to apply. - **Required** only applies to formats with more than one condition of the same type and changes the matching rules for type groups. Enabling this option means that this specific condition must be satisfied for the whole custom format to apply regardless of if another condition of the same type would otherwise satisfy the type group.
More details on some of the conditions below: More details on some of the conditions below:
## Release Title ### Release Title
Replaces the 'Custom' format tag from v0.2. This is a regular expression matched against the release title and, after download, the filename on disk Replaces the 'Custom' format tag from v0.2. This is a regular expression matched against the release title and, after download, the filename on disk
## Edition ### Edition
Replaces the 'Editon' format tag from v0.2. This is a regular expression that matches against what Radarr parses as the movie edition (eg. Director's cut, Extended, etc) Replaces the 'Editon' format tag from v0.2. This is a regular expression that matches against what Radarr parses as the movie edition (eg. Director's cut, Extended, etc)
## Profile settings and Ranking
The overhaul has scrapped the linear ranking system in favor of a scoring system assigning points to releases to allow more multi-dimensional preferences. The cutoff has been replaced by a stopping score where upgrading stops once a release with this desired score has been downloaded. The "None" format is replaced simply with a score of zero while the checkboxes controlling rejection or acceptance of matched releases is now controlled by the Minimum Custom Format Score. Custom formats that match with undesirable attributes should be given a negative score to lower their appeal. Outright rejections should be given a negative score low enough that even if all of the other formats with positive scores were added, the score would still fall below the minimum.