You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
recyclarr/wiki/Configuration-Examples.md

11 KiB

Various scenarios supported using flexible configuration structure:

Update as much as possible in both Sonarr and Radarr with a single config

Create a single configuration file (use the default recyclarr.yml if you want to simplify your CLI usage by not being required to specify --config) and put all of the configuration in there, like this:

sonarr:
  - base_url: http://localhost:8989
    api_key: f7e74ba6c80046e39e076a27af5a8444
    quality_definition: hybrid
    release_profiles:
      - trash_ids:
          - EBC725268D687D588A20CBC5F97E538B # Low Quality Groups
          - 1B018E0C53EC825085DD911102E2CA36 # Release Sources (Streaming Service)
          - 71899E6C303A07AF0E4746EFF9873532 # P2P Groups + Repack/Proper
        strict_negative_scores: false
        tags: [tv]

radarr:
  - base_url: http://localhost:7878
    api_key: bf99da49d0b0488ea34e4464aa63a0e5
    quality_definition:
      type: movie
      preferred_ratio: 0.5

Even though it's all in one file, Radarr settings are ignored when you run recyclarr sonarr and vice versa. To update both, just chain them together in your terminal, like so:

recyclarr sonarr && recyclarr radarr

This scenario is pretty ideal for a cron job you have running regularly and you want it to update everything possible in one go.

Selectively update different parts of Sonarr

Say you want to update Sonarr release profiles from the guide, but not the quality definitions. There's no command line option to control this, so how do you do it?

Simply create two YAML files:

sonarr-release-profiles.yml:

sonarr:
  - base_url: http://localhost:8989
    api_key: f7e74ba6c80046e39e076a27af5a8444
    release_profiles:
      - trash_ids:
          - d428eda85af1df8904b4bbe4fc2f537c # Anime - First release profile
          - 6cd9e10bb5bb4c63d2d7cd3279924c7b # Anime - Second release profile
        tags: [anime]

sonarr-quality-definition.yml:

sonarr:
  - base_url: http://localhost:8989
    api_key: f7e74ba6c80046e39e076a27af5a8444
    quality_definition: hybrid

Then run the following command:

recyclarr sonarr --config sonarr-release-profiles.yml

This will only update release profiles since you have essentially moved the quality_definition property to its own file. When you want to update both, you just specify both files the next time you run the program:

recyclarr sonarr --config sonarr-release-profiles.yml sonarr-quality-definition.yml

Update multiple Sonarr instances in a single YAML config

If you have two instances of Sonarr that you'd like to update from a single run of the updater using one YAML file, you can do that by simply specifying both in the list under the sonarr property:

sonarr:
  - base_url: http://instance_one:8989
    api_key: f7e74ba6c80046e39e076a27af5a8444
    quality_definition: anime
    release_profiles:
      - trash_ids:
          - d428eda85af1df8904b4bbe4fc2f537c # Anime - First release profile
          - 6cd9e10bb5bb4c63d2d7cd3279924c7b # Anime - Second release profile
  - base_url: http://instance_two:8989
    api_key: bf99da49d0b0488ea34e4464aa63a0e5
    quality_definition: series
    release_profiles:
      - trash_ids:
          - EBC725268D687D588A20CBC5F97E538B # Low Quality Groups
          - 1B018E0C53EC825085DD911102E2CA36 # Release Sources (Streaming Service)
          - 71899E6C303A07AF0E4746EFF9873532 # P2P Groups + Repack/Proper

In the example above, two separate instances, each with its own API key, will be updated. One instance is for Anime only. The other is for Series (TV) only. And since I'm using two instances, I don't bother with tags, so I am able to leave those elements out.

When you run recyclarr sonarr (specify --config if you aren't using the default recyclarr.yml) it will update both instances.

You can also split theses two instances across different YAML files if you do not want both to update at the same time. There's an example of how to do that in a different section of this page.

Synchronize a lot of custom formats for a single quality profile

Scenario: "I want to be able to synchronize a list of custom formats to Radarr. In addition, I want the scores in the guide to be applied to a single quality profile."

Solution:

radarr:
  - base_url: http://localhost:7878
    api_key: 87674e2c316645ed85696a91a3d41988

    custom_formats:
      # Advanced Audio from the guide
      - names:
          - TrueHD ATMOS
          - DTS X
          - ATMOS (undefined)
          - DD+ ATMOS
          - TrueHD
          - DTS-HD MA
          - FLAC
          - PCM
          - DTS-HD HRA
          - DD+
          - DTS-ES
          - DTS
          - AAC
          - DD
        quality_profiles:
          - name: SD

Manually assign different scores to multiple custom formats

Scenario: "I want to synchronize custom formats to Radarr. I also do not want to use the scores in the guide. Instead, I want to assign my own distinct score to each custom format in a single quality profile."

Solution:

radarr:
  - base_url: http://localhost:7878
    api_key: 87674e2c316645ed85696a91a3d41988

    custom_formats:
      - names: [TrueHD ATMOS]
        quality_profiles:
          - name: SD
            score: 100
      - names: [DTS X]
        quality_profiles:
          - name: SD
            score: 200
      - names: [ATMOS (undefined)]
        quality_profiles:
          - name: SD
            score: 300
      - names: [TrueHD]
        quality_profiles:
          - name: SD
            score: 400
      - names: [DTS-HD MA]
        quality_profiles:
          - name: SD
            score: 500
      - names: [FLAC]
        quality_profiles:
          - name: SD
            score: 600

The configuration is structured around assigning multiple custom formats the same way to just a few quality profiles. It starts to look more redundant and ugly when you want fine-grained control over the scores, especially if its on a per-single-custom-format basis.

Assign custom format scores the same way to multiple quality profiles

You can assign custom format scores (from the guide) to multiple profiles (all the same way):

radarr:
  - base_url: http://localhost:7878
    api_key: 87674e2c316645ed85696a91a3d41988

    custom_formats:
      - names:
          - TrueHD ATMOS
          - DTS X
          - ATMOS (undefined)
          - DD+ ATMOS
          - TrueHD
        quality_profiles:
          - name: SD
          - name: Ultra-HD

Quality profiles named HD and Ultra-HD will all receive the same scores for the same custom formats.

You can also choose to override the score (for all custom formats!) in one profile:

radarr:
  - base_url: http://localhost:7878
    api_key: 87674e2c316645ed85696a91a3d41988

    custom_formats:
      - names:
          - TrueHD ATMOS
          - DTS X
          - ATMOS (undefined)
          - DD+ ATMOS
          - TrueHD
        quality_profiles:
          - name: SD
            score: 100 # This score is assigned to all 5 CFs in this profile
          - name: Ultra-HD # Still uses scores from the guide

Resolving ambiguity between custom formats with the same name

Normally when you want a custom format, you list it by name under the names property, like so:

radarr:
  - base_url: http://localhost:7878
    api_key: 87674e2c316645ed85696a91a3d41988

    custom_formats:
      - names:
          - FLAC
          - DoVi

However, especially in the case of DoVi, there are actually two custom formats with this name in the guide. You'll get a warning from Recyclarr stating that it couldn't pick which one you wanted, so it was skipped. To fix this, simply use trash_ids and refer to it by an ID. IDs are never duplicated in the guide and also never change, so it's a robust and effective way to identify custom formats. The downside is that they are less readable than a name, but using comments can help with that. The example below demonstrates how to do this.

radarr:
  - base_url: http://localhost:7878
    api_key: 87674e2c316645ed85696a91a3d41988

    custom_formats:
      - names:
          - FLAC
      - trash_ids:
          - 5d96ce331b98e077abb8ceb60553aa16 # DoVi

Where do you get the Trash ID? That's from the "trash_id" property of the actual JSON for the custom format in the guide.

Scores in a quality profile should be set to zero if it wasn't listed in config

Scenario: "I completely rely on Recyclarr to set scores on my quality profiles. I never plan to manually set scores on those profiles. If I alter which custom format scores get assigned to a quality profile, the old scores should be set back to 0 automatically for me."

radarr:
  - base_url: http://localhost:7878
    api_key: 87674e2c316645ed85696a91a3d41988

    custom_formats:
      - names:
          - DTS X
          - TrueHD
        quality_profiles:
          - name: SD
            reset_unmatched_scores: true
          - name: Ultra-HD

Let's say you have three custom formats added to Radarr: "DTS X", "TrueHD", and "DoVi". Since only the first two are listed in the names array, what happens to "DoVi"? Since two quality profiles are specified above, each with a different setting for reset_unmatched_scores, the behavior will be different:

  • The SD profile will always have the score for "DoVi" set to zero (0).
  • The Ultra-HD profile's score for "DoVi" will never be altered.

The reset_unmatched_scores setting basically determines how scores are handled for custom formats that exist in Radarr but are not in the list of names in config. As shown in the example above, you set it to true which results in unmatched scores being set to 0, or you can set it to false (or leave it omitted) in which case Recyclarr will not alter the value.

Which one should you use? That depends on how much control you want Recyclarr to have. If you use Recyclarr to supplement manual changes to your profiles, you probably want it set to false so it doesn't clobber your manual edits. Otherwise, set it to true so that scores aren't left over when you add/remove custom formats from a profile.