starred/Lidarr

Fork 0

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

Custom format(s) arent being applied to names #2918

New issue

Open

opened 2026-02-20 02:13:04 -05:00 by deekerman · 11 comments

deekerman commented

2026-02-20 02:13:04 -05:00

Owner

Originally created by @klepp0906 on GitHub (May 14, 2023).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

I'm attempting to use this

[{Custom Formats }{Quality Full}]

however it seems to be not taking the {Custom Formats } bit into account whatsoever. It still leaves me with just [FLAC] as opposed to [CD FLAC] for example.

Expected Behavior

using [{Custom Formats }{Quality Full}] in your track naming should append the quality with whatever custom format(s) youve enabled

include in {Custom Formats} renaming format

with.

Steps To Reproduce

1 using lidarr nightly, create a custom format for CD for example, be sure to enable it to be used in naming.
2 under media management add {Custom Formats} somewhere in your track naming.
3 attempt to rename your track(s) and notice it seems to be entirely ignored

Environment

- OS: Windows 11 
- Lidarr: 1.2.1.3193
- Database: Sqlite 3.36.0

What branch are you running?

Nightly

Trace Logs?

https://0bin.net/paste/zJsHjueP#Azzr9FMkM+fsN9uycI8OVhrRN2PYKZlzcEhhYuLhQhW

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have followed the steps in the wiki link above and provided the required trace logs that are relevant and show this issue.

Originally created by @klepp0906 on GitHub (May 14, 2023). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior I'm attempting to use this > [{Custom Formats }{Quality Full}] however it seems to be not taking the {Custom Formats } bit into account whatsoever. It still leaves me with just [FLAC] as opposed to [CD FLAC] for example. ### Expected Behavior using [{Custom Formats }{Quality Full}] in your track naming should append the quality with whatever custom format(s) youve enabled > include in {Custom Formats} renaming format with. ### Steps To Reproduce 1 using lidarr nightly, create a custom format for CD for example, be sure to enable it to be used in naming. 2 under media management add {Custom Formats} somewhere in your track naming. 3 attempt to rename your track(s) and notice it seems to be entirely ignored ### Environment ```markdown - OS: Windows 11 - Lidarr: 1.2.1.3193 - Database: Sqlite 3.36.0 ``` ### What branch are you running? Nightly ### Trace Logs? https://0bin.net/paste/zJsHjueP#Azzr9FMkM+fsN9uycI8OVhrRN2PYKZlzcEhhYuLhQhW ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [X] I have followed the steps in the wiki link above and provided the required trace logs that are relevant and show this issue.

deekerman added the

labels

2026-02-20 02:13:04 -05:00

deekerman commented

2026-02-20 02:13:05 -05:00

Author

Owner

@Davo1624 commented on GitHub (May 14, 2023):

nothing to add other than this would be great to have

@Davo1624 commented on GitHub (May 14, 2023): nothing to add other than this would be great to have

deekerman commented

2026-02-20 02:13:05 -05:00

Author

Owner

@bakerboy448 commented on GitHub (May 15, 2023):

Logs don't exist?

@bakerboy448 commented on GitHub (May 15, 2023): Logs don't exist?

deekerman commented

2026-02-20 02:13:05 -05:00

Author

Owner

@klepp0906 commented on GitHub (May 15, 2023):

yea i deleted em and closed the issue as it turned out to be a regex problem. forward slashes and not backslashes, yay ;p
someone re-opened it, unsure why.

only behavior im seeing now is the custom format naming isnt retroactive when doing a rename. I can only assume this is due to the database not seeing it in the original filename during the original grab.

in this particular instance I was just trying to have it display CD or WEB which makes me wonder how the {medium format} is working retroactively and discerning between digital and cd if not original filename but thats off-topic.

@klepp0906 commented on GitHub (May 15, 2023): yea i deleted em and closed the issue as it turned out to be a regex problem. forward slashes and not backslashes, yay ;p someone re-opened it, unsure why. only behavior im seeing now is the custom format naming isnt retroactive when doing a rename. I can only assume this is due to the database not seeing it in the original filename during the original grab. in this particular instance I was just trying to have it display CD or WEB which makes me wonder how the {medium format} is working retroactively and discerning between digital and cd if not original filename but thats off-topic.

deekerman commented

2026-02-20 02:13:05 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (May 15, 2023):

only behavior im seeing now is the custom format naming isnt retroactive when doing a rename. I can only assume this is due to the database not seeing it in the original filename during the original grab.

This is why I reopened it. Feel free to close it again if it doesn't bother you.

@mynameisbogdan commented on GitHub (May 15, 2023): > only behavior im seeing now is the custom format naming isnt retroactive when doing a rename. I can only assume this is due to the database not seeing it in the original filename during the original grab. This is why I reopened it. Feel free to close it again if it doesn't bother you.

deekerman commented

2026-02-20 02:13:05 -05:00

Author

Owner

@klepp0906 commented on GitHub (May 15, 2023):

oh no, having it retroactively applied would certainly be the ideal/preferential behavior. open it is then. I just wasnt sure if thats how it was expected/intended to function or not.

@klepp0906 commented on GitHub (May 15, 2023): oh no, having it retroactively applied would certainly be the ideal/preferential behavior. open it is then. I just wasnt sure if thats how it was expected/intended to function or not.

deekerman commented

2026-02-20 02:13:05 -05:00

Author

Owner

@klepp0906 commented on GitHub (May 20, 2023):

just to add to this, as ive still been working to get naming the way i want and running into all kinds of walls. Seems its only sometimes applying the CF naming to new imports.

sometimes its working, sometimes its not, and i cant ascertain what the differing variable is.

I just grabbed 2 CD releases, never been in my library before, folders were created without the CF name. one album is being misidentified as digital media even though i grabbed a CD release via interactive search (which is one thing preventing me from just using {medium format} instead of {custom formats}). even when trying to force it to the CD via album > edit > release, it just... doesnt work. ignores me when i hit save and retains the current format.

if someone can test and confirm the latter i'll open a new issue

@klepp0906 commented on GitHub (May 20, 2023): just to add to this, as ive still been working to get naming the way i want and running into all kinds of walls. Seems its only sometimes applying the CF naming to new imports. sometimes its working, sometimes its not, and i cant ascertain what the differing variable is. I just grabbed 2 CD releases, never been in my library before, folders were created without the CF name. one album is being misidentified as digital media even though i grabbed a CD release via interactive search (which is one thing preventing me from just using {medium format} instead of {custom formats}). even when trying to force it to the CD via album > edit > release, it just... doesnt work. ignores me when i hit save and retains the current format. if someone can test and confirm the latter i'll open a new issue

deekerman commented

2026-02-20 02:13:06 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Jan 21, 2024):

Nightly has better logging to debug this github.com/Lidarr/Lidarr@2cf2ebcbb2 for release title conditions

@bakerboy448 commented on GitHub (Jan 21, 2024): Nightly has better logging to debug this https://github.com/Lidarr/Lidarr/commit/2cf2ebcbb28a59537533f36e4433349dbd76b473 for release title conditions

deekerman commented

2026-02-20 02:13:06 -05:00

Author

Owner

@ehula commented on GitHub (Feb 6, 2025):

Any update on this? Sure would be nice to have.

@ehula commented on GitHub (Feb 6, 2025): Any update on this? Sure would be nice to have.

deekerman commented

2026-02-20 02:13:06 -05:00

Author

Owner

@MaddyTP commented on GitHub (Mar 6, 2025):

I'm running into this same issue. It seems the custom formats work fine when searching for media, but once downloaded it parses the file name instead of the original grab title. Additionally, the renaming function looks at the file name instead of the original grab title.

@MaddyTP commented on GitHub (Mar 6, 2025): I'm running into this same issue. It seems the custom formats work fine when searching for media, but once downloaded it parses the file name instead of the original grab title. Additionally, the renaming function looks at the file name instead of the original grab title.

deekerman commented

2026-02-20 02:13:07 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Mar 6, 2025):

I'm running into this same issue. It seems the custom formats work fine when searching for media, but once downloaded it parses the file name instead of the original grab title. Additionally, the renaming function looks at the file name instead of the original grab title.

This is by design and intentional

Release Parsing is always disconnected from On Disk Import Parsing

@bakerboy448 commented on GitHub (Mar 6, 2025): > I'm running into this same issue. It seems the custom formats work fine when searching for media, but once downloaded it parses the file name instead of the original grab title. Additionally, the renaming function looks at the file name instead of the original grab title. This is by design and intentional Release Parsing is always disconnected from On Disk Import Parsing

deekerman commented

2026-02-20 02:13:07 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 9, 2025):

👋 @klepp0906, In order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our troubleshooting guide.

@github-actions[bot] commented on GitHub (Jun 9, 2025): :wave: @klepp0906, In order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our [troubleshooting guide](https://wiki.servarr.com/lidarr/troubleshooting#logging-and-log-files).