Table of Contents
Summary
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
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:
- Negate means that the match is inverted, so the condition is satisfied if and only if the non-negated condition is not satisfied
- 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:
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
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)
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.
Getting Started
Troubleshooting
- AppData Directory
- Clear Cache Cookies and Local Storage
- Common Problems
- Health Checks
- Remote Path Mappings explained
- How to make sure Radarr doesn't snatch full Blu-Rays
Additional Configuration
- AppData Directory
- Custom Post Processing Scripts
- Built In Qualities
- Custom Formats
- Installing Multiple Instances of Radarr on Windows
- Supported NetImports
- Supported Notifications
- Reverse Proxy
- Release Branches
- Sorting and Renaming
- Twitter Notifications
- Webhook
- Webhook Schema