As kdf mentioned in the forum this is a feature, not a bug. "Scanning playlist" doesn't mean we're looking for playlists only and be fine with it. They actually have to be processed, analyzed for new songs being referenced etc.

Thanks Michael.  At the risk of trying your patience, can you explain to me why doing the playlist checks you mention should require:

"Merge Various Artists" (1547 of them), takes 5:04

"Database Cleanup #1" (31782), takes 1:34

"Database Cleanup #2", might have finished in 2 minutes or so, hard to tell.


From the outside, I would have thought that a user-initiated playlist-only scan would have meant something like this:

"I have created this playlist.  Please add it to your list of playlists."


It apparently also seems to mean:

"Please make sure every song in the playlist is present in the database so you can play it."


which is fine, but I would not have thought it _also_ meant

"and while you're at it, conduct an eight minute cleanup of my database."


and I'm not completely sure why it should have to mean that.  Especially when those other database cleanup scans take place AFTER the playlist scan (if the readout is to be believed), meaning that the playlist scan doesn't even benefit from scanning a newly clean database, if that was supposed to be the point.

Any explanation appreciated.  I tried to look at the source code but unfortunately my programming skills are too rusty, and I couldn't reason it out for myself.

please don't open new bugs if you're already discussing it elsewhere

*** This bug has been marked as a duplicate of 6308 ***