SUMMARY This is more of a feature request, not a bugreport actually. However, as the situation impacts user's experience, this goes here as a "bug report". All my music resides on a network disk, available through dynamically mounted NFS share. Every time I launch Elisa it starts "importing new tracks" to the collection, while there's been no changes to files on the server. Is it possible to make Elisa stop auto-renewing collection on each launch and rely on database stored locally? STEPS TO REPRODUCE 1. Add a network-based source of music to Elisa's settings 2. Wait for importing to be finished 3. Close Elisa, launch it again OBSERVED RESULT Importing "starts" again. EXPECTED RESULT Local database providing music collection info, renewal only through explicit clicking on respective menu item / button. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.2 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION
Hello, I'd like to be more precise: when the entire music collection is situated on a network location, Elisa doesn't cache / save db of those files locally (at least it looks like that), because every time it being launched anew, it shows an empty collection and starts scanning again. It is totally unusable for a network-located collections of music.
Elisa has two methods of finding music: 1. The Systemwide Baloo file indexer 2. Filesystem crawling #1 is fast, but relies on the music location being indexed by Baloo. #2 supports arbitrary locations but it's slow. Handling locations that can't be indexed by baloo without filesystem crawling would require adding third method and TBH I'm not sure how worth it that would be.
OK will try to enable indexing for a share and see how it goes.
Hi again. After disconnection from and re-connection to the NFS share where my collection resides, Elisa's unable to show any file due to removal (automatic removal I must say) of the source configured in its preferences. So I have to add that source back and wait for everything scanned/imported again. Sad. Well, I'm better off of this and return to Cantata.
This bug isn't fixed yet just because you moved to another app. Re-opening.
*** Bug 445621 has been marked as a duplicate of this bug. ***
*** Bug 457782 has been marked as a duplicate of this bug. ***
I would argue this is a bug report and not a feature request if #457782 is a duplicate of this. Configuration should not be getting changed out from under me, whether the folder is reachable or not. I also don't see how this is specific to network-based locations at all. I mount via SSHFS, which is a FUSE filesystem and shouldn't need handling any differently from other FUSE filesystems. Additionally, I can replicate this with a USB external hard drive (simply configuring a folder on the drive and then launching with the drive unplugged.) One other thing, I see "importing ### tracks" every time I launch Elisa even with only the default ~/Music folder configured. So #457782 was not a duplicate of what was initially being described here, and what was initially being described here also had nothing to do with networking. Nate, would we be able to re-open and un-mark #457782 as duplicate, and rename #418605 to be more specific about re-scanning on every startup (and remove the network reference)?
(In reply to Nate Graham from comment #7) > *** Bug 457782 has been marked as a duplicate of this bug. *** Nate, please see my previous comment-- you incorrectly marked #457782 as a duplicate and you are conflating various hard bugs and UX wishlist items in combining all of these into a single thread. Can you please respond to this?
Oops, my mistake.