John Stimson Wrote: > > > I think that clearly the composer should be shown along with the title > of the work, and the movement. But we may want to know who the > top-billed performer is, as well -- either the conductor or the > soloist. So just to throw an idea out there, which may be excessively > complicated: > > COMPOSER(artist) - TITLE -[ PART -] ARTIST(album) > or > COMPOSER(artist) - TITLE -[ PART -][ ARTIST -] ALBUM > > Values in () are used if the preceding tag is empty, values in [] are > only displayed if the tag exists. That should give you normal pop > music behavior for tracks without the classical tags, or the desired > classical music display when those tags are present. > > The downside of this scheme is that sometimes pop music does include > the COMPOSER tags. One track of an album by The Police may have > COMPOSER=Sting, and another may have COMPOSER=A. Summers. > > As for how to add a symphony to the playlist, it would be nice if > slimserver could treat sequential tracks with the same TITLE as a unit. > Instead of the browse tree looking like > > ALBUM->TRACK > > it could look like > > ALBUM->TITLE(->PART) > > With the TITLEs sorted in track order.
Well, we already have the ability to define Display strings in pretty much any way we like, so as long as the tag is in the system you can use it. COMPOSER is already in the database, though apparently not in the list of fields you can put in the display string (but this would be a VERY simple enhancement, I think I could even do it myself). What you won't be able to use is PART, as its not in the Slimserver database. If you want that added as a recognised tag you'll need to put in an enhancement request. Recognising that you might want two different format strings for classical vs pop, its not too hard to switch, using the player UI: Settings -> song Title Format allows you to flip between your pre-defined formats. What I think is new in your request - though I've not played with this area much - is a requirement for a small amount of intelligence in the string format. It will already (apparently) cope with a tag not being present (intelligently omits the associated separator if the field is blank) [this was your square bracket notation]. What would be nice is the ability to substitute a different tag if the first one is blank (your round bracket notation). Thats an interesting idea, it might be worth asking around to see if that would help in a variety of different scenarios. That enhancement request ought to be relatively simple ... here's a more complicated alternative ... how about something along the lines of the ( ifthisistrue ? option if true : option if false) operation. You might use this to ask slimserver to select one of two different format strings depending on whether the ifthisistrue tag has a value. I've a funny feeling I might have just got too complicated, but let's see if anyone else bites... Ceejay -- ceejay ------------------------------------------------------------------------ ceejay's Profile: http://forums.slimdevices.com/member.php?userid=148 View this thread: http://forums.slimdevices.com/showthread.php?t=20850 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
