my new squeezebox and OS X concerns

[Mike Marley]

Hello all,

I just received my squeezebox the other day and I truly love it. I
have run into a couple of problems though and I would like some input
from others.

I decided not to use the itunes library and instead just pointed the
slimserver at my 250GB drive. Once the scanning got done everything
was okay and I was up and running. I tweaked around with some
settings, plugins, etc. I then added some more music to the drive in
an effort to consolidate everything. The problem is now everytime I
add any music I have to rescan the entire drive again which is
incredibly inefficient. During one of these scans, the hard drive went
south on me and I lost about 20 GBs of music. If it wasn't for
Alsoft's Diskwarrior I don't know if I ever would have gotten the drive
back.

The bottom line for me is this: There must be a better way to deal
with the scanning of music. I feel there is absolutely too much wear
and tear put on the drive everytime you add music to it. I know that I
can just browse my music folder to access the music immediately but
that takes away from the functionality quite a bit, don't you think.

The other night I was this close to returning the squeezebox since I
lost so much data but I am willing to hold out for now since I do
realize that there is active development on the software and hopefully
some changes can be made that address my concerns.

One question before I go. If I was using iTunes instead, would that
effect the scanning of the drive. Would slimserver just use the
library's xml file instead of scanning? If so, maybe that's the way to
go. Just the fact that slimserver does a rescan everytime the server
is started drives me crazy.

Thanks for listening and I look forward to some positive responses.

Mike

[kdf]

my new squeezebox and OS X concerns

Quoting Mike Marley <saltydog (AT) odaydo (DOT) com>:


> One question before I go. If I was using iTunes instead, would that
> effect the scanning of the drive. Would slimserver just use the
> library's xml file instead of scanning? If so, maybe that's the way to
> go. Just the fact that slimserver does a rescan everytime the server
> is started drives me crazy.

iTunes has its own scanning requirements. SlimServer, if selected to use iTuesn
will simply load the XML file. It check severy few seconds to see if there have
been any changes in that file, and reloads it if needed.

If you dont use iTunes, the nightly versions offer a setting to Cache the MP3
database (server settings, performance). The cache is then stored as
slimserver.db and reloaded on startup.

-kdf