mirror of
https://github.com/Lidarr/Lidarr.git
synced 2026-03-02 22:56:57 -05:00
Ignore/Hide unmapped filed #2835
Labels
No labels
Area: API
Area: Database
Area: Db-migration
Area: Download Clients
Area: Extras
Area: Import Lists
Area: Indexer
Area: Metadata API
Area: Notifications
Area: Organizer
Area: Parser
Area: Scanning
Area: Tooling
Area: UI
Area: Unit Tests
Area: Update API
On Hold: MetadataAPI Blocking
Priority: High
Priority: Low
Priority: Medium
Status: Accepted
Status: Cannot Reproduce
Status: Confirmed
Status: Don't Merge
Status: Help Wanted
Status: In Progress
Status: Info Needed
Status: Investigating
Status: Logs Needed
Status: Maybe One Day
Status: Needs Triage
Status: On Hold
Status: Ready for Review
Status: Unlikely
Status: Waiting for OP
Status: Won't Fix
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: Enhancement
Type: External Bug
Type: Feature Request
Type: Regression
Type: Support
Type: Support.
conflict
conflict
no-conflict
not-pulled
radarr-pull
readarr-pull
sonarr upstream
sonarr-pull
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Lidarr#2835
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Dante2202 on GitHub (Apr 17, 2023).
Is there an existing issue for this?
Is your feature request related to a problem? Please describe
Deleting tracks from the unmapped list deletes tracks from root folder instead of just deleting track from the unmapped list. Having thousands of unmapped tracks would take years to go through to match, deleting them isn't a practical solution as users still want to keep the unmapped tracks.
Potentially going through hundreds/thousands of artist folders and manually selecting each album to move into an “unmonitored” folder would break existing continuity with artist/album categorization. Also, if you attempt to match unmapped tracks they show back up in the unmapped queue if you have duplicate albums.
Lidarr is constantly analyzing & attempting to match unmapped files causing user hard drives & servers to take a massive performance hit every time "rescan folders" runs.
Users have a valid reason for having multiple versions of the same album. Example: Remastered Edition, Deluxe Editions, Anniversary Edition, Vinyl, etc…
While it is understandable that only 1 version of an album is matched in Lidarr, the remaining alternate versions go to the unmapped files queue where they are forever being rescanned in an attempt to match causing performance issues.
Describe the solution you'd like
An option to also "Hide/Ignore" unmapped files instead of physically deleting them from root folder. Deleting files does not solve the issue, most users want to keep unmapped files and just ignore/hide them, not delete them.
Describe alternatives you've considered
Manually editing the database to assign AlbumId value of unmapped files to a value other than "0", this initially works and clears all unmapped tracks but when a "Rescan Folders" task begins the unmapped files come back.
Anything else?
Just the ability to hide/ignore unmapped files, I cannot delete my unmapped files.
@bakerboy448 commented on GitHub (May 15, 2023):
Duplicate of #2548