To view parent comment, click here.
To read all comments associated with this story, please click here.
My setup is in a bit of shambles at the moment, thanks to a hard drive crash last year. But I've been thinking about rebuilding it (most of the files were mirrored on other drives, thankfully) and documenting the process as a how-to guide.
The biggest limitation is that the BeOS filemanager (Tracker) has no way to natively read ID3 tags from files (as Win Explorer and, I believe, Finder do) - so separate apps need to be used to convert the tags to filesystem attributes. Though SoundPlay will do it automatically when a file is first played, and there are apps that can batch-convert the tags from multiple files.
Without going on and on, I find the biggest advantage is that it's extremely simple to customize the way files are displayed / listed. I normally use really verbose filenames (Track Num - Artist - Album - Title.mp3), but then set the filemanager to show only the track number & song title - and sort by track number. Attributes can also be set for the folders containing each individual album - so you can do stuff like sort the ablums for an individual artist by year, without having to put it in the folder name.





Member since:
2005-07-06
I think it's largely a matter of taste / preference. FWIW, I'm in the same boat as you are - I'd much rather use small, best-of-breed applications that focus on a specific task. Most of my music is stored on a BeOS machine, using Tracker / BFS attributes for indexing/cataloguing, SoundPlay for playback, ArmyKnife for tagging, and the RipEnc script for ripping and encoding.
Although I can certainly see why someone would prefer an end-to-end solution that handles all of those tasks.