View Full Version : Ripping entire library.
My sqeezebox has arrived and I've got it running wirelessly over a linksys
wrt54g router. Slackware OS. I've test-ripped some ogg, flac, and mp3 using
k3b. Artist/Album info seems a bit off.
Time to rip my entire collection. I intend to stream music to my Rotel/ B&W
stereo down stairs. Here's what I'd like to know:
1. Anybody out there using slackware? How did you install slimserver? How do
you maintain updates?
2. I've got a new 200 gb drive to put my tunes on. What file system is best
for music? Which inode size? Should I put some swap at the beginning of a
disk that will be all data?
2. Is there a documented How-To/Procedure that anybody can recommend for
ripping my entire collection of cds? I want to use the highest quality stream
possible. Flac? Is there a format for ripping that will ensure that
artist/album metadata works properly/seamlessly with the slimserver?
Thanks in advance for any and all responses.
Jason Holtzapple wrote:
>>2. I've got a new 200 gb drive to put my tunes on. What file system is best
>>for music? Which inode size? Should I put some swap at the beginning of a
>>disk that will be all data?
> I don't have a recommendation on which file system to use. Most of my
> friends use ext3 or xfs and avoid reiserfs for their large music libraries.
Regardless of the file system you choose (I went with ext3 for my Linux media
server), I heartily recommend using logical volume mapping (LVM) when setting up
your drive. This will allow you to easily add additional drives later on and
have them appear as a single volume to the OS. You can also more easily resize
volumes if you so choose.
There's a good introductory article at IBM's developerWorks site:
I'm a slackware guy. I installed slimserver using the tgz, and I made my own
rc.slim script since the stock one didn't work for some reason or another, but
I'm not at my machine to remind myself why at the moment. Whatever it was, the
solution was pretty straightforward. When I upgrade, I just move the old
slimserver directory aside and untar the new one in its place.
I've used reiserfs for my mp3 collection for a long time, and I've never had
any problems with it, even with the occasional yanking-of-the-wrong-power-cord
or other such unclean shutdown. It's much faster to mount a very large drive
than ext2. I haven't been following ext3 news, so that may be just as good or
better than reiserfs by now, but I have no reason to switch since reiser works
great. The only downside reiserfs ever had was that way back in the day, you
had to patch your kernel to use it, but it's in the package now, so that's moot.
For ripping my collection, I use a python program a friend of mine wrote and
now refuses to support/fix, since he lost interest after he finished ripping
his collection. :) All it does is plumb together your chosen ripper, normalizer,
and encoder, with cddb info thrown in. I'm sure there are a million programs
like it, but unfortunately, I don't know of one to recommend. I do recommend
finding one which is UI-less and just does its thing when you run it from the
command line, so you can have a simple 'rip' script that calls your ripper and
then pokes slimserver to do a rescan. That lets my relatively technophobic
girlfriend "slimp3"* her discs without asking me how.
*yes, the verb "to slimp3" is now commonly used in my house.
Bryce Richards says:
> 1. Anybody out there using slackware? How did you install slimserver? How do
> you maintain updates?
> 2. I've got a new 200 gb drive to put my tunes on. What file system is best
> for music? Which inode size? Should I put some swap at the beginning of a
> disk that will be all data?
> 2. Is there a documented How-To/Procedure that anybody can recommend for
> ripping my entire collection of cds? I want to use the highest quality stream
> possible. Flac? Is there a format for ripping that will ensure that
> artist/album metadata works properly/seamlessly with the slimserver?
Powered by vBulletin® Version 4.1.12 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.