Bugzilla – Bug 2704
DB scanning fails to find directories starting with double underscores "__"
Last modified: 2008-09-15 14:38:10 UTC
Title pretty much says the meat of the issue. I have directories that are titled in such a way that they start with double underscores, for example, "__Audio_Books". As long as the directories start with a double underscore SlimServer (during the rescan process) fails to notice them. The songs don't appear in the DB. I can't see them in the "Browse Music Folder" etc. When I change the double underscore to a single underscore, everything works. To repeat the bug. 1) Rename a file with a noticable chuck of MP3s to "__foo" 2) Go to "Server Settings"->"Rescan Music Library" and select "Clear ... and Rescan ..." 3) Wait for rescanning to end. 4) Notice that the songs are now gone from the DB, and are not visable from the top level "Browse Music Folder" option. I have no clue whether double underscores in the middle of the direcotry name do anything. Nor, do I know if the problem also manifests itself with files (versus directories). BTW, in case you're wondering why I use double underscores, it forces the directory to the top of the sort order in Windows Explorer. (Yeah, I could use 1_*, 2_*, etc.)
I do that too in Windows to force directories to the top, but why the need for two underscores when one will suffice?
This is a vestige of when the "Now Playing" playlist was stored on disk as an m3u file with two underscores. For a short term fix, I suggest changing the names to 1 underscore. I've checked in a fix as change 5421.