Is there a simple way to ignore the composers of, for example, all tracks with GENRE=Noise ?
But this syntax is illegal.
my control point to display classical music composers only.
> Create a new field in tag editor (e.g classical_composer) and then copy over composer but only for classical tracks, then configure MinimServer to use this field instead of the composer field.
Or do you only want composers for classical everywhere ?
(06-11-2017 14:10)ofrex Wrote: The reason I am asking is that I would like my control point to display classical music composers only.
This may seem like a trivial suggestion, but it isn't.
You could simply use the browse sequence Genre > Classical > Composer. This requires no tag editing beyond what you already seem to be doing, and no additional property settings.
In fact, this is the starting browse sequence I most commonly use, to the point where I don't have to think about it, which is the least effortful means of using any tool.
(08-11-2017 18:10)DavidHB Wrote: You could simply use the browse sequence Genre > Classical > Composer. This requires no tag editing beyond what you already seem to be doing, and no additional property settings.
This is a good suggestion from David but, dare I say, it could be improved with a little more effort.
The following suggestion removes one tag selection step, i.e.
In short, it creates a new tag with a single value, which is added to the top index.
I found a couple of "classical" variations among my files.
(09-11-2017 12:41)Alandbush Wrote: This is a good suggestion from David but, dare I say, it could be improved with a little more effort.
On issues of this kind, there is often no 'better' or 'best', but only what the user finds most convenient and intuitive (often the same thing) and suited to his or her use case, muscle memory, and level of confidence in dealing with MinimServer settings. Between us, you and I have given users alternative options, which is a good thing.
All that said, your suggestion intrigues me. I particularly like the way it is all done in settings, with no addition to the tagging commitment. I'll give it a go and report back.
(10-11-2017 21:43)DavidHB Wrote: All that said, your suggestion intrigues me. I particularly like the way it is all done in settings, with no addition to the tagging commitment. I'll give it a go and report back.
I am very happy that the suggestion has some merit. Thanks.
I tried this as well, and it works, but I found no fewer steps in the end: I now have a starting list which shows Albums, Items, Album Artist, Genre, Classical Library, etc. - all good. But when I select Classical Library I get a screen with two selections, Classical and Unknown. When I select Classical I get the full display of selections for Classical, but that extra screen showing all the rest of my collection under “Unknown” means I haven’t saved any steps over just going to Genre and selecting Classical. Am I doing something wrong?
(11-11-2017 16:44)antonmb Wrote: I tried this as well, and it works, but I found no fewer steps in the end: I now have a starting list which shows Albums, Items, Album Artist, Genre, Classical Library, etc. - all good. But when I select Classical Library I get a screen with two selections, Classical and Unknown. When I select Classical I get the full display of selections for Classical, but that extra screen showing all the rest of my collection under “Unknown” means I haven’t saved any steps over just going to Genre and selecting Classical. Am I doing something wrong?
Looks like you have missed adding the single tag value (Classical) to the indexTags entry.
Refer to Index tag selection for an explanation.
This is a fantastic tip. One selection step may not seem like much, but on a small screen it makes a lot of difference with repeated use. Thank you!
I have just stumbled across this thread, but my attempts to experiment with the tagUpdate setting were unsuccessful. When I tried to define the tagUpdate property as /volume1/music/tagUpdate.txt, I just got the following red error message.
In fact, anything I attempted to specify for the value of tagUpdate, with or without a path, generated the same error. Where might I be going wrong?