starred/Radarr

Fork 0

mirror of https://github.com/Radarr/Radarr.git synced 2026-03-02 22:57:34 -05:00

Custom Formats do not apply before the Movie Year in release titles #4650

New issue

Open

opened 2026-02-19 22:47:56 -05:00 by deekerman · 15 comments

deekerman commented

2026-02-19 22:47:56 -05:00

Owner

Originally created by @imjuzcy on GitHub (Aug 12, 2020).

Describe the bug
The custom format is v3 is very weird ang buggy. It says it's regex, but it's performing very inconsistently.

For example, let's say the release title is "Vectronic Presents Native Daughter (2019) 1080p.AMZN.WEB-DL x264. NL Subs Ingebakken". If the regex is set to (without quotes):

"Vectronic Presents": no match
"Vectronic Presents.*": no match
"Vectronic.Presents.": no match
".*Vectronic.Presents.": no match
"native": no match
"daughter": no match
"2019": match
"amzn": match

Let's say if the release title is "A.Beautiful.Day.in.the.Apartment.2019.UHD.BluRay.2160p.DTS-X.7.1.HEVC.REMUX-FraMeSToR-Scrambled". If regex set to (without quotes):

"beautiful": no match
"apartment": no match
"2019": match
"uhd": match

Let's say if the release title is "Red.Lantern.3D.2011.MULTI.1080p.BluRay.x264-JASS". If regex set to (without quotes):

".(3d|sbs).": no match

But if the release title is "Blue.Lantern.3D.2011.1080p.BluRay.Full-SBS.DTS.x264-TruHD", then ".(3d|sbs)." gets a match.

From this, it seems that only the year and everything that proceeds are going to get matched with custom formats. If this is true, this might give some problem as mentioned in above examples, I would like to avoid 3D files and releases from "Vectronic Presents", but Radarr will still grab the first, third and forth releases in above given examples, which I'm actively trying to avoid.

To Reproduce
Steps to reproduce the behavior:
Do as mentioned in example.

Expected behavior
Custom formats should match everything including things that precede title.

Platform Information (please complete the following information):

OS: Ubuntu 20.04 Docker
Radarr Version: 3.0.0.3374-ls18 by linuxserver.io

AB#825

Originally created by @imjuzcy on GitHub (Aug 12, 2020). **Describe the bug** The custom format is v3 is very weird ang buggy. It says it's regex, but it's performing very inconsistently. For example, let's say the release title is "Vectronic Presents Native Daughter (2019) 1080p.AMZN.WEB-DL x264. NL Subs Ingebakken". If the regex is set to (without quotes): "Vectronic Presents": no match "Vectronic Presents.*": no match "Vectronic.*Presents.*": no match ".*Vectronic.*Presents.*": no match "native": no match "daughter": no match "2019": match "amzn": match Let's say if the release title is "A.Beautiful.Day.in.the.Apartment.2019.UHD.BluRay.2160p.DTS-X.7.1.HEVC.REMUX-FraMeSToR-Scrambled". If regex set to (without quotes): "beautiful": no match "apartment": no match "2019": match "uhd": match Let's say if the release title is "Red.Lantern.3D.2011.MULTI.1080p.BluRay.x264-JASS". If regex set to (without quotes): ".*(3d|sbs).*": no match But if the release title is "Blue.Lantern.3D.2011.1080p.BluRay.Full-SBS.DTS.x264-TruHD", then ".*(3d|sbs).*" gets a match. From this, it seems that only the year and everything that proceeds are going to get matched with custom formats. If this is true, this might give some problem as mentioned in above examples, I would like to avoid 3D files and releases from "Vectronic Presents", but Radarr will still grab the first, third and forth releases in above given examples, which I'm actively trying to avoid. **To Reproduce** Steps to reproduce the behavior: Do as mentioned in example. **Expected behavior** Custom formats should match everything including things that precede title. **Platform Information (please complete the following information):** - OS: Ubuntu 20.04 Docker - Radarr Version: 3.0.0.3374-ls18 by linuxserver.io [AB#825](https://dev.azure.com/Servarr/7ab38f4e-5a57-4d70-84f4-94dd9bc5d6df/_workitems/edit/825)

deekerman added the

Type: Bug

Status: Maybe One Day

labels

2026-02-19 22:47:56 -05:00

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@ta264 commented on GitHub (Aug 12, 2020):

As far as I am aware it uses the entire release title (hence the format name). I suspect you just have it set up wrong since we have so many other uses that would spot similar behaviour. Please join the discord channel for support

@ta264 commented on GitHub (Aug 12, 2020): As far as I am aware it uses the entire release title (hence the format name). I suspect you just have it set up wrong since we have so many other uses that would spot similar behaviour. Please join the discord channel for support

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@support[bot] commented on GitHub (Aug 12, 2020):

We use the issue tracker exclusively for bug reports and feature requests. However, this issue appears to be a support request. Please hop over onto our Discord or Subreddit

@support[bot] commented on GitHub (Aug 12, 2020): We use the issue tracker exclusively for bug reports and feature requests. However, this issue appears to be a support request. Please hop over onto our [Discord](https://discord.gg/ZDmT7qb) or [Subreddit](https://reddit.com/r/radarr)

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@ta264 commented on GitHub (Aug 12, 2020):

I apologize, you are correct.

At the moment this is by design but maybe it should be reviewed.

@ta264 commented on GitHub (Aug 12, 2020): I apologize, you are correct. At the moment this is by design but maybe it should be reviewed.

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@stale[bot] commented on GitHub (Oct 11, 2020):

This issue has been automatically marked as stale because it has not had recent activity. Please verify that this is still an issue with the latest version of Radarr and report back. Otherwise this issue will be closed.

@stale[bot] commented on GitHub (Oct 11, 2020): This issue has been automatically marked as stale because it has not had recent activity. Please verify that this is still an issue with the latest version of Radarr and report back. Otherwise this issue will be closed.

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Nov 14, 2020):

@ta264 @Qstick any plans to change?

@bakerboy448 commented on GitHub (Nov 14, 2020): @ta264 @Qstick any plans to change?

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@austinwbest commented on GitHub (Nov 14, 2020):

We discussed this the other day since 3d won't match if before the year. Thought was to possibly strip the title and do a check against what was left iirc

@austinwbest commented on GitHub (Nov 14, 2020): We discussed this the other day since 3d won't match if before the year. Thought was to possibly strip the title and do a check against what was left iirc

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@ItsME6969 commented on GitHub (Aug 17, 2022):

You can make regex do anything, match anything before the year, after the year, etc I really dont understand the need to filter the title and dumbing it down. Please rereview.

@ItsME6969 commented on GitHub (Aug 17, 2022): You can make regex do anything, match anything before the year, after the year, etc I really dont understand the need to filter the title and dumbing it down. Please rereview.

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@angrycuban13 commented on GitHub (Nov 2, 2022):

This is still happening.

@angrycuban13 commented on GitHub (Nov 2, 2022): This is still happening. ![img](https://sharex.angrycuban.xyz/haRe3/teKacEnO02.png/raw)

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@austinwbest commented on GitHub (Nov 3, 2022):

This is still happening.

This might be an exception as that is a valid movie title?

@austinwbest commented on GitHub (Nov 3, 2022): > This is still happening. > > ![img](https://sharex.angrycuban.xyz/haRe3/teKacEnO02.png/raw) This might be an exception as that is a valid movie title?

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@angrycuban13 commented on GitHub (Nov 3, 2022):

Yeah I guess this might be a poorly named release

@angrycuban13 commented on GitHub (Nov 3, 2022): Yeah I guess this might be a poorly named release

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@angrycuban13 commented on GitHub (Nov 3, 2022):

This is still happening.

To clarify since I shared the post-import screenshot. Here is the grab history

I think the release name is bad in this case so ignore me

@angrycuban13 commented on GitHub (Nov 3, 2022): > This is still happening. > > > > ![img](https://sharex.angrycuban.xyz/haRe3/teKacEnO02.png/raw) To clarify since I shared the post-import screenshot. Here is the grab history ![img](http://sharex.angrycuban.xyz/haRe3/xocetiPi94.png/raw) I think the release name is bad in this case so ignore me

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Nov 3, 2022):

There's a few similar GHI open for this.

CF perform materially differently between release name and file names as well.

@bakerboy448 commented on GitHub (Nov 3, 2022): There's a few similar GHI open for this. CF perform materially differently between release name and file names as well.

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@spkesDE commented on GitHub (Sep 26, 2024):

I encountered the same issue while trying to filter 3D movies with the current regex implementation:

(?i)\b(?:3D|SBS|HSBS|HOU|Half[ .-]SBS|Half[ .-]OU)\b

Non-Matching Example:

My.movie.release.3D.HOU.2015.German.AC3.Dubbed.DL.1080p.BluRay.x264-LameHD

Matching Example:

My.movie.release.HOU.2015.3D.German.AC3.Dubbed.DL.1080p.BluRay.x264-LameHD

The regex only seems to apply after the year, but not before it. This inconsistency makes it challenging to filter movies that are tagged with 3D before the year.

Could you please take another look at this issue? I believe addressing this regex behavior will greatly enhance the functionality of the filter. Thank you for your attention to this matter! 👍

@spkesDE commented on GitHub (Sep 26, 2024): I encountered the same issue while trying to filter 3D movies with the current regex implementation: `(?i)\b(?:3D|SBS|HSBS|HOU|Half[ .-]SBS|Half[ .-]OU)\b` Non-Matching Example: > My.movie.release.**3D**.HOU.2015.German.AC3.Dubbed.DL.1080p.BluRay.x264-LameHD Matching Example: > My.movie.release.HOU.2015.**3D**.German.AC3.Dubbed.DL.1080p.BluRay.x264-LameHD The regex only seems to apply after the year, but not before it. This inconsistency makes it challenging to filter movies that are tagged with 3D before the year. Could you please take another look at this issue? I believe addressing this regex behavior will greatly enhance the functionality of the filter. Thank you for your attention to this matter! 👍

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@wurst-hans commented on GitHub (Jun 13, 2025):

Exactly what @spkesDE said.

Currently I'm not able to run Radarr headless, because from time to time a 3D movie is grabbed which is not caught by custom formats. For sure, this is due to malformed release titles or whatever. But currently, we have no solution for this.

If we were able to do RegEx on whole (Usenet) filename additionally to the release title, this would solve many of users problems. (And there are much more movie attributes that would be helpful for writing more efficient custom formats)

@wurst-hans commented on GitHub (Jun 13, 2025): Exactly what @spkesDE said. Currently I'm not able to run Radarr headless, because from time to time a 3D movie is grabbed which is not caught by custom formats. For sure, this is due to malformed release titles or whatever. But currently, we have no solution for this. If we were able to do RegEx on whole (Usenet) filename additionally to the release title, this would solve many of users problems. (And there are much more movie attributes that would be helpful for writing more efficient custom formats)

deekerman commented

2026-02-19 22:47:56 -05:00

Author

Owner

@clemwo commented on GitHub (Dec 20, 2025):

I was pulling my hair out wondering why my Custom Format didn't work.
In the end this is obviously caused by inconsistent naming of uploads which I hate but can't change.
Would be great to give us users to override this default... please

@clemwo commented on GitHub (Dec 20, 2025): I was pulling my hair out wondering why my Custom Format didn't work. In the end this is obviously caused by inconsistent naming of uploads which I hate but can't change. Would be great to give us users to override this default... please

deekerman referenced this issue

2026-02-20 00:11:11 -05:00

Ignore some files when renaming or deleting due to an upgrade #9175

deekerman referenced this issue

2026-02-20 00:11:11 -05:00

Ignore some files when renaming or deleting due to an upgrade #9175