Custom formats not same on import and search. Causing import/grab loop for the same release

tenfire commented 1 year ago

Is there an existing issue for this?

[X] I have searched the existing open and closed issues

Current Behavior

The title of a release of a search is sometimes different than the filename. I think I have also seen cases where the title is updated with more details but, the filename stays the same.

The problem is that the custom formats is not calculated the same on search and on import. This seems to be causing the same release being grabbed over and over in a loop when the score is higher on search than on import.

Expected Behavior

Not sure, but a suggestion could be that indexers have an option to "trust" the search result rather than analyzing the imported file when calculating custom formats.

Steps To Reproduce

Have a custom format that appear in the search title of a release but not in the actual file.
Movie was monitored and set to upgrade past the quality/score post import.

Environment

- OS: Ubuntu
- Radarr: Radarr 4.3.2.6857
- Docker Install: Yes
- Using Reverse Proxy: Yes
- Browser: Brave
- Database: Sqlite

What branch are you running?

Master

Trace Logs?

No logs

bakerboy448 commented 1 year ago

For Movie Title or custom formats within/before the movie title? - Duplicate of https://github.com/Radarr/Radarr/issues/4859
Logs are not optional
Examples and the custom format jsons are needed as well

tenfire commented 1 year ago

I think this differs from the other issue.

Sorry for not posting any logs, I did not know what to post. If there is any moment you would like me to post log from, I can try to find it. After looking at the issue you just mentioned I realize that I could post a screenshot instead, hope that is sufficient as a start.

Example movie history: brave_sTlYk5XEka

HDR:

{
  "name": "HDR",
  "includeCustomFormatWhenRenaming": true,
  "specifications": [
    {
      "name": "HDR",
      "implementation": "ReleaseTitleSpecification",
      "negate": false,
      "required": true,
      "fields": {
        "value": "\\bHDR.*\\b"
      }
    }
  ]
}

HDR10Plus:

{
  "name": "HDR10Plus",
  "includeCustomFormatWhenRenaming": true,
  "specifications": [
    {
      "name": "HDR10Plus",
      "implementation": "ReleaseTitleSpecification",
      "negate": false,
      "required": true,
      "fields": {
        "value": "\\bHDR10Plus|(HDR10\\+)"
      }
    }
  ]
}

bakerboy448 commented 1 year ago

See TRaSH's Guides and his discord for related custom format support questions

This behavior is expected and your filenames are using the custom format names that the imported file matched for naming which then no longer match the CF when imported as your Custom Formats' regex do not match the Custom Format Name - nor would one expect them to. You need to fix your naming scheme to support how you want your custom formats to work....TRaSH's guides detail this all out

Radarr / Radarr