|
Streamlining the browsing tree & multiple configs
|
|
21-09-2013, 22:23
(This post was last modified: 21-09-2013 23:31 by haggis999.)
Post: #45
|
|||
|
|||
|
RE: Streamlining the browsing tree & multiple configs
Some further experimenting with the MinimServer configuration I displayed a couple of posts ago, has shown up an issue with classical albums that contain single track works (similar to a pop album). Because I am browsing in the classical genre I am expecting to be able to use my custom Work tag, whether or not that work occupies one track or 40 tracks. I also have aliasTags = Work:Group.
However, for a single track work the Work tag and the Track tag would be the same and the 'Group' would be a group of one. The result is a redundant extra step in the selection process but that is a relatively minor problem. My primary issue is that there is no quick way to select all the tracks in, for example, a Chopin piano recital CD. You can only drill down to a single track at a time on the album. Is there any way to change this behaviour? David EDIT: One solution might be for me to have an empty Work tag for single track works. That fixes the immediate problem in MinimServer but I don't yet know if it messes things up elsewhere. I have created a calculated custom tag in JRMC snappily called WorkOrTrackTitle. The value of this tag comes from the expression if(!isempty([work]),[work],[name]), which returns the Work tag if available and the Name tag (what JRMC calls the Track title) if Work is empty. Using WorkOrTrackTitle where previously I would have used Work may be a viable solution in all apps that support custom tags. Obviously, I would have to save the WorkOrTrackTitle tag into all the FLAC files. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



