starred/Lidarr

Fork 0

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

Rejected: Unable to parse albums from release name #3301

New issue

Open

opened 2026-02-20 02:16:40 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 02:16:40 -05:00

Owner

Originally created by @rogales on GitHub (Oct 27, 2023).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

Hello there,

after talking with one of Your donators on discord channel, He told me that I should create a BUG REPORT, which I'm doint right now.

So autobrr sent two releases to lidarr, and asked if it fits with rules I've prepared earlier.
My rules are mainly FLAC, and thats it. (Was just waiting for this album).
Okey, so autobrr asked lidarr these two releases:

Sofia Kourtesis - Madres - [2023] [Album] WEB/FLAC/Lossless
Sofia Kourtesis - Madres [2023] [Album] - FLAC / Lossless / WEB

and lidarr in both of these rejected it with a reason of "Unable to parse albums from release name"

as far as I know from my knowledge, my conversation with user nicknamed B (on discord), and after checking releases in #parse-testing, lidarr SHOULD grab one of these torrents.

here are images of this problem;

I've add torrent mannualy to my client with lidarr label, and after that it hadn't non issues of attaching it to proper artist and album name;

any kind of help would be appreciated.

Expected Behavior

Lidarr will be able to recognise and grab torrent.

Steps To Reproduce

No response

Environment

- OS: Unraid 6.12.4
- Lidarr: 1.4.5.3639
- Docker Install: binhex-lidarr
- Using Reverse Proxy: no
- Browser: Google Chrome 118.0.5993.117
- Database: 3.41

What branch are you running?

Master

Trace Logs?

do not have log

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

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

Originally created by @rogales on GitHub (Oct 27, 2023). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior Hello there, after talking with one of Your donators on discord channel, He told me that I should create a BUG REPORT, which I'm doint right now. So autobrr sent two releases to lidarr, and asked if it fits with rules I've prepared earlier. My rules are mainly FLAC, and thats it. (Was just waiting for this album). Okey, so autobrr asked lidarr these two releases: 1. Sofia Kourtesis - Madres - [2023] [Album] WEB/FLAC/Lossless 2. Sofia Kourtesis - Madres [2023] [Album] - FLAC / Lossless / WEB and lidarr in both of these rejected it with a reason of "Unable to parse albums from release name" as far as I know from my knowledge, my conversation with user nicknamed B (on discord), and after checking releases in #parse-testing, lidarr SHOULD grab one of these torrents. here are images of this problem; 1. ![image](https://github.com/Lidarr/Lidarr/assets/93039918/121d3268-07db-4eb2-893e-00c1c586142e) 2. ![image](https://github.com/Lidarr/Lidarr/assets/93039918/ca508dcf-c015-44e9-be0e-3be3c105f9b0) I've add torrent mannualy to my client with lidarr label, and after that it hadn't non issues of attaching it to proper artist and album name; ![image](https://github.com/Lidarr/Lidarr/assets/93039918/457328d7-fa34-4626-aca3-330c506ccc17) any kind of help would be appreciated. ### Expected Behavior Lidarr will be able to recognise and grab torrent. ### Steps To Reproduce _No response_ ### Environment ```markdown - OS: Unraid 6.12.4 - Lidarr: 1.4.5.3639 - Docker Install: binhex-lidarr - Using Reverse Proxy: no - Browser: Google Chrome 118.0.5993.117 - Database: 3.41 ``` ### What branch are you running? Master ### Trace Logs? do not have log ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [X] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman added the

labels

2026-02-20 02:16:40 -05:00

deekerman commented

2026-02-20 02:16:40 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 27, 2023):

👋 @rogales, 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 (Oct 27, 2023): :wave: @rogales, 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).

deekerman commented

2026-02-20 02:16:40 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Feb 27, 2024):

@mynameisbogdan we never got any logs is this still valid in v2? Do you have enough info to work on this without any other info?

@bakerboy448 commented on GitHub (Feb 27, 2024): @mynameisbogdan we never got any logs is this still valid in v2? Do you have enough info to work on this without any other info?

deekerman commented

2026-02-20 02:16:40 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 6, 2025):

@github-actions[bot] commented on GitHub (Sep 6, 2025): :wave: @rogales, 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).