Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rescan only a given subfolder or new files #13989

Open
arximboldi opened this issue Dec 5, 2024 · 5 comments
Open

Rescan only a given subfolder or new files #13989

arximboldi opened this issue Dec 5, 2024 · 5 comments

Comments

@arximboldi
Copy link
Contributor

Feature Description

Ideally, we would have #6631 and #5630 addressed. But instead, sometimes you know the new files are in a particular subfolder. Instead of triggering a full re-scan, it would be nice to say "rescan only this folder" to find new files. Or maybe an option that could help with speed would be also something like "Scan only new files" instead of checking that existing files are the same and some of the other more expensive tests.

@fwcd
Copy link
Member

fwcd commented Dec 5, 2024

Not saying anything against this request, but I'm curious: Has rescan performance been an issue for you? My library has around 18k tracks and incremental rescans usually take less than a second (on a reasonably fast SSD)

@ronso0
Copy link
Member

ronso0 commented Dec 5, 2024

How would we select the directory?
Via Computer feature tree? (meeh..)
Or would there be a popup when triggering a rescan, showing a tree of watched dirs, with a checkbox for each dir?

@arximboldi
Copy link
Contributor Author

Actually I was thinking something like the "Computer" tree, in fact it would be nice to have another tree "Library files" that looks a bit like that but shows only the library folders. You could right-click "refresh", and when you select one of the folders it shows all the files that live anywhere inside that sub-tree. It could also be an interesting way to navigate the library and find music for people that (like me) have huge libraries that also have meaningful organization o disk...

@ronso0
Copy link
Member

ronso0 commented Dec 6, 2024

I think you can already use the 'Quick Links' node for that, no? It's not at the top level, but still.

@fwcd
Copy link
Member

fwcd commented Dec 6, 2024

I think it's a nice idea actually. Maybe we could just present the music directories beneath the "Missing Tracks" and "Hidden Tracks" nodes:

Screenshot 2024-12-06 at 16 29 38

The "Tracks" node would still display the entire library and the directory tree would then only display the tracks under that directory (and potentially subdirectories). Though it might be an interesting questions whether to use the file system to find the subdirectories and then query the db for tracks in those locations or whether we'd just use the db to infer the entire hierarchy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants