CavesOfTQLT Wrote: > Concerning duplicate tracks; if I've got R.E.M's Everybody Hurts* on > one of their albums, and I've also got the _same_ track on a > compilation, and _another_ on another compilation, that's three copies > taking up space, whether that space is valuable or not. Surely it would > be easy in this day and age of HDD to have just the _one_ copy and to > add a small reference 'track' file to each of the albums where the > track was removed. That way Slimserver would know that a particular > track should be present in an album, and the reference file would point > to where the track is actually located, in order to play it, or even to > reconstruct the album if this was needed. > > The only other way I can think of is to have just a single copy of > every track, and to use the 'Album' tag to reference every album that > track should be in. But then my preferred format of saving all R.E.M's > albums in one folder, all Coldplay's albums in another folder etc., > wouldn't be possible. Plus it would be a tagging nightmare. > > *Obviously if another artist/s did a version of R.E.M's Everybody > Hurts, such as The Corrs, then that copy would remain because it is > different, as would an instrumental version be if R.E.M decided to do > one.
Maybe I'm missing something, but when you start talking about compilation albums and storing multiple copies of tracks on the disk - isn't that pretty much what playlists are for? I think you're asking a _lot_ from SlimServer as a music library manager. It may get there some day, but given the current capabilities and the complexities of a web application that could do something like this, you're probably looking at the wishlist for SlimServer version 12.0 or so. -- JJZolx _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
