starred/Radarr

Fork 0

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

Inconsistent parsing when dashes used as separators #9233

New issue

Closed

opened 2026-02-20 00:11:49 -05:00 by deekerman · 7 comments

deekerman commented

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

Owner

Originally created by @pl98 on GitHub (Jul 24, 2025).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

When releases use dashes as separators instead of periods, the parsing result for quality is inconsistent.

Expected Behavior

They should report the same result after parsing.

Steps To Reproduce

No response

Environment

- OS: Unraid 7.1.4 
- Radarr: 5.26.2.10099 
- Docker Install: Yes
- Using Reverse Proxy: No
- Browser: 
- Database:

What branch are you running?

Master

Trace Logs? Not Optional

Trace Logs

Trace Logs have been provided as applicable. Reports will 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 @pl98 on GitHub (Jul 24, 2025). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Current Behavior When releases use dashes as separators instead of periods, the parsing result for quality is inconsistent. <img width="1052" height="812" alt="Image" src="https://github.com/user-attachments/assets/4fca238e-3cda-41ff-9426-317a9efae0e3" /> <img width="1049" height="807" alt="Image" src="https://github.com/user-attachments/assets/2a077efe-7a65-4a36-aa8e-8de2b9ee5527" /> ### Expected Behavior They should report the same result after parsing. ### Steps To Reproduce _No response_ ### Environment ```markdown - OS: Unraid 7.1.4 - Radarr: 5.26.2.10099 - Docker Install: Yes - Using Reverse Proxy: No - Browser: - Database: ``` ### What branch are you running? Master ### Trace Logs? **Not Optional** [Trace Logs](https://gist.github.com/pl98/a5fec3e597753a40571105e1ffe26c12) ### Trace Logs have been provided as applicable. Reports will 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

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

closed this issue
added the
Type: Bug

Status: Won't Fix

Area: Organizer
labels

deekerman commented

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

Author

Owner

@bakerboy448 commented on GitHub (Jul 24, 2025):

Are there releases in the wild that actually have that quality naming?

Simply creating an arbitrary naming format that has not been seen in the wild does not mean a bug exists....a valid real releases usecase needs to existz

@bakerboy448 commented on GitHub (Jul 24, 2025): Are there releases in the wild that actually have that quality naming? Simply creating an arbitrary naming format that has not been seen in the wild does not mean a bug exists....a valid real releases usecase needs to existz

deekerman commented

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

Author

Owner

@pl98 commented on GitHub (Jul 24, 2025):

Yes, I noticed this bug because I had a release that was grabbed even though I do not have Remux 2160p selected in my quality profile. I can link the release if necessary but I wasn't sure if that was allowed here.

@pl98 commented on GitHub (Jul 24, 2025): Yes, I noticed this bug because I had a release that was grabbed even though I do not have Remux 2160p selected in my quality profile. I can link the release if necessary but I wasn't sure if that was allowed here.

deekerman commented

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

Author

Owner

@pl98 commented on GitHub (Jul 24, 2025):

Another thing is that it was listed as Bluray-2160p in the history but Remux-2160p in the Activity section.

@pl98 commented on GitHub (Jul 24, 2025): Another thing is that it was listed as Bluray-2160p in the history but Remux-2160p in the Activity section. <img width="3006" height="946" alt="Image" src="https://github.com/user-attachments/assets/a29ba69f-dc10-4693-aaa9-0fd36e630ea8" /> <img width="2980" height="938" alt="Image" src="https://github.com/user-attachments/assets/cc6bacab-4ca9-42ad-b74a-7f3a3bcb1f47" />

deekerman commented

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

Author

Owner

@nuxencs commented on GitHub (Jul 24, 2025):

Another thing is that it was listed as Bluray-2160p in the history but Remux-2160p in the Activity section.

that's most likely due to file and release on the tracker being named differently

@nuxencs commented on GitHub (Jul 24, 2025): > Another thing is that it was listed as Bluray-2160p in the history but Remux-2160p in the Activity section. > <img alt="Image" width="2000" height="946" src="https://private-user-images.githubusercontent.com/29090662/470331437-a29ba69f-dc10-4693-aaa9-0fd36e630ea8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTMzNjYyMjQsIm5iZiI6MTc1MzM2NTkyNCwicGF0aCI6Ii8yOTA5MDY2Mi80NzAzMzE0MzctYTI5YmE2OWYtZGMxMC00NjkzLWFhYTktMGZkMzZlNjMwZWE4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA3MjQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNzI0VDE0MDUyNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTZiM2ZmOTU2OWY4MzM5NjRlNzE4MjViYWI5ZWVlZjBmYWIzOTUyZjYwOWFlNWJiNzFhMmFhY2U2YjFmMjRiNzUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.bkAHQHwrBaWVLPWy36-mSPKF1MDMZgdR9o2BUUsM3kE"> <img alt="Image" width="2000" height="938" src="https://private-user-images.githubusercontent.com/29090662/470331306-cc6bacab-4ca9-42ad-b74a-7f3a3bcb1f47.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTMzNjYyMjQsIm5iZiI6MTc1MzM2NTkyNCwicGF0aCI6Ii8yOTA5MDY2Mi80NzAzMzEzMDYtY2M2YmFjYWItNGNhOS00MmFkLWI3NGEtN2YzYTNiY2IxZjQ3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA3MjQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwNzI0VDE0MDUyNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBiZGIwMjBhMTUzM2FhNzVjYzM2MjFlOGZiMmYwMjQwMWFiODg2YzgyNGEzZDk1YzZjZGI1NTViNjA3OTFhZTcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.AE4YuXbQT-iEoZvZJMIKBrhRSxHkEFpkyPlJwfbkZz8"> that's most likely due to file and release on the tracker being named differently

deekerman commented

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

Author

Owner

@bakerboy448 commented on GitHub (Jul 24, 2025):

what tracker has that shit name scheme?

@bakerboy448 commented on GitHub (Jul 24, 2025): what tracker has that shit name scheme?

deekerman commented

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

Author

Owner

@pl98 commented on GitHub (Jul 24, 2025):

TorrentDownload

@pl98 commented on GitHub (Jul 24, 2025): TorrentDownload

deekerman commented

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

Author

Owner

@bakerboy448 commented on GitHub (Jul 24, 2025):

Open an issue with jackett for them to cleanup this shitty file naming.

No plans to support renamed releases using a non-standard schema on a public tracker.

@bakerboy448 commented on GitHub (Jul 24, 2025): Open an issue with jackett for them to cleanup this shitty file naming. No plans to support renamed releases using a non-standard schema on a public tracker.