And now we have two interleaved threads going, this is really going to confuse people!!
Listener Wrote: > > > Recognise these tags: "Performer" in Vorbis, > > TP1/TPE1 in ID3v2.2/2.3. > What Does SS use as Artist now? It seems reasonable that it is using > TP1/TPE1. Should be using TOPE/TOA. > > > Request 2 - Alternate tags for "band". > I agree. One clarification. SS should always load all the contributor > tags. These settings for adding other tags to Artist should just affect > what is queried. Sorry, don't understand. > > > Request 3 - Improve "Advanced Search" in Web interface > > (simplified version: superceded by Multi-Level Browse) > > I don't see the advanced search as being superceded by the Multi-Level > Browse. That allows you to specify several tags at once and see the > result. Since this is a web interface only command, it is more > tolerable to get a sizeable result set. I think I just responded to this in the other thread - ok, no problem with keeping browse and search separated in the web interface. > > > May want only to do this if there are less than N values to > > stop this getting out of hand. Ideally N should be > > configurable on this form - default say 50? > I'd say more like 20-30 items max in the list. However, for Genre, I'd > show them all. I think the developers should find a max. number that > works well on the screen and wire it in. ok > > > (4) For extra credit (but not essential in first release)... > > Some of these tags can legally have multiple occurrences, so > > the search should allow for this. Tags which can occur only > > once (Album, Artist, Year, Title) can just be entry boxes > > against a fixed label as in the current Advanced Search form. > > > The ones which can be multiple could be accomodated by having > > a number of flexible labels, each with a pull-down > > selecting from the valid tag names. You could default the > > first to "Composer", the second to "Conductor", etc. > > I don't understand why this has to be much more complicated than the > single occurrence case. I see three ways to keep it simple: > > a. Let the user pick one and only one value for a tag that may occur > more than once (You specify John Williams. You get all the albums with > John Williams, the guitarist solo and the albums with John and Julian > Bream.) > > b. Let the user specify more than one value with the logic being > "choice 1 and choice 2". Specify "multiple (choices)" in the HTML > defining the drop-down list. The SS code that handles the users input > gets more than one value for the drop-down list control. Works just > right for the two John and Julian Bream albums. > > c. Let the user specify more than one value with the logic being > "choice 1 or choice 2". Same HTML as for b. This would work for > finding a performance of the Beethoven Violin Concerto with either > Heifetz or Grumiaux as soloist. Worse than than a. for John Williams > and Julian Bream albums. > > I think that b. is the way to go. I thought I was keeping it simple. Your option "a" is the same as not doing the (4) "extra credit" and is certainly the simplest option. I don't like your option "b" so much. Where the number of possible values is large, so having a pull down list is not practical, I want to be lazy and just type in part of a name (e.g. "Kara" or "Haif"). To make this work for both short and long lists, I'd prefer my idea of having selectable labels from the valid tags and value boxes which are either open or prepopulated as appropriate. > > > Request 4 - Widen list of tags for browsing (simplified > > version: superceded by Multi-Level Browse) > > I presume that that the sequence of browse steps will be hard-wired for > request. My preference for the hard-wired sequencesl: > > Browse Composer => Album => Tracks > Browse Conductor => Composer => Album => Tracks > Browse Genre or Year or Album - as it is now. > Yes, I think the sequence will have to be hardwired at this point. At the risk of being controversial, should it be Conductor=>Artist instead of Conductor=>Composer ? This would be on the grounds that "Artist" should always be populated with something, but "Composer" may well not be. It would also be consistent with "Genre". > > We really need to find a tag that can be given a short name for the > work. I looked in the OGG Vorbis recommendations and don't see any > easy answer in the standard tags. I do have a suggestion. Let the > user specify a tag name for an OGG Vorbis tag he wants to store and use > to browse. It would appear in the "Browse <tag>" list and in the "And > Browse <nn> <tag>" menu items list. > > I'd define "Work" as a tag to browse and use a tag editor to fill it > out from the Album name." Someone else could choose whatever tag he > has placed in his music files. Nice idea - a user defined arbitrary tag that you tell slim to look for and that you can then search or browse on ... I have no idea if this would create an implementation problem, but we can always ask. An "optional extra", perhaps? Regards Ceejay (past my bedtime again...) -- ceejay ------------------------------------------------------------------------ ceejay's Profile: http://forums.slimdevices.com/member.php?userid=148 View this thread: http://forums.slimdevices.com/showthread.php?t=18767 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
