Vidur's database work should address this.

*** Bug 696 has been marked as a duplicate of this bug. ***

Any progress on this bug?  It's been out there quite a while, but I just noticed
it while I was consolidating disk1/disk2/... etc sets into one directory.  

This seems a terrible flaw to me.  

FYI I'm running the 01/06/2005 build for windows.  This was opened in june of
2004 and Dean's comment dates from August.  So what's up?

I hope you mean the 1/06/05 build of 6.0 at least.  

There is a lot of progress toward this bug, if not yet this bug specifically. 
try having multiple albums with the same title, for example.  Those used to be
merged together.  The particular problem expressed in this bug may still exist,
but its far from forgotten. 6.0 is still in alpha level, and this bug (as well
as MANY others, just as important) is part of the path to 6.0

Well, thanks for the comment.  I can't wait for 6.0 and the new database.  As it
stands, it's rather shocking to have music in the library and not be able to
play it --  

I believe I will have to stop evangalizing for your product until the fix comes
out for this bug.  I'm rather disillusioned:

-- My music library has, at the moment, 2415 MP3 files in it.
-- Slimserver 5.4.1 (build 1/6/2005) shows that I have 268 albums with 2659
songs by 91 artists.  That's a difference of 244 songs on the PLUS side of reality.
-- If I "browse artists" and ask it to play "all albums", the playlist shows
2363 songs.  That's 52 songs on the MINUS side of reality.
-- However, if I browse the music folder and ask it to play "all subfolders", I
get a playlist containing 2415 songs, which is exactly right.

How can I recommend that my friends purchase this product?  I don't even know
where to begin trying to reconcile these numbers and getting all my music to be
"playable".  

Also, I notice that songs occasionally and randomly show up listed under "No
Artist/No Album" even though they clearly have ID3 tags on them.

BTW, I installed to 6.0 nightly build for Windows today, hoping it might solve
some of these problems.  FYI, the SlimServer service wouldn't even start -- it
started and quit immediately.

please do not use this tool for soap box.  If you have a compaint, take it to
the list or support@slimdevices.com.  

This resource is designed for developers to work out problems and for people to
make contructive requests and input.  If all you have to contribute is ranting,
then the discussion list is perfect for that. Bug reports are welcome, but the
rest is for people who are trying their best to satisfy everyone's desire as
fast as possible.  you asked if there is progress, and the response is that
there is.  that is all that can be granted at this time. 

how are you supposed to recommend it?? well, as a product that is openly
serviced,  pick anything else and just try to compare it.  if you find something
better, then go for it. 

Sorry.  I feel bad and I apologize.  It was inappropriate for me to rant.  I
know you guys are awesome and are doing the best you can.  I was just a little
frustrated.  Again, sorry.

After massaging my music folder for hours last night, I now have only a
three-song discrepancy between my library and what Slimserver shows.  Close
enough for now!  I'll wait patiently for 6.0.

RE

you dont have to wait.  There are nightly builds of 6.0 available if you want to
tackle the process head on.  not every build is stable, but some work well
enough.   Give them a shot, and see what songs are missing and report that.  as
far as song scanning and data storage, 5.4.1 is dead.  The mthods used there are
past their limit and effectively unfixable.  6.0 is a work in progress, but
already there is huge improvement.  

Vidur believes that this is fixed in 6.0.   Please verify with the beta.  Thanks.