i wrote too quickly. to be more precise, i should have said:
"the SQL that populates this display should be constraining by an ID
unique to this album"
cdfreak wrote:
But if you constrain by both album and artist, you'll have 10-15 of each
compilation cd, and some soundtracks. In this case, you'd need to have a
tag specified for "cdartist" (Various Artists) or to somehow note that
it is a compilation cd or multiple artist album.
you're right. various artists albums are a special case. SS needs to
deal with this case generally. once that is done, then it should take
care of this case as well.
it seems like a workable approach to this problem should already exist.
do the standard tagging systems have a marker for compilations? how do
other library management and playback applications deal with issue?
Or, you could rename the album to be more than just the common name,
like Footsteps to be Artist - Footsteps. But this would make displaying
look rather poor when it says "Miles Davis - Footsteps by Miles Davis".
could work, but seems a horrible hack.
There's not a very easy solution from a database perspective without a
field that is album unique. If it doesn't come from the id3 tag it
needs to come from the file/folder location.
is there no unique album key in the SS DB schema? that's a real
weakness. i can see why it would be hard to nail down, as most audio
files are track-based and not album-based.
a key based on uniqueness of Artist-Album concatenation might be good
enough once the V/A problem is addressed.
Going by *folder* giving each "folder" an ID# in the database, [...]
any solution that relies on identifying unique albums by path is going
to fail for users that don't follow the expected conventions. i suppose
it would be possible to allow user to enter custom masks to hint this
type of interpretation.
thoughts?
--rt
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
