|
'Album Sort' - unexpected behaviour
|
|
09-03-2022, 14:47
(This post was last modified: 09-03-2022 14:48 by DavidL.)
Post: #11
|
|||
|
|||
RE: 'Album Sort' - unexpected behaviour
(09-03-2022 14:16)RSJ Wrote: So... If I have two version of Beethoven's 9th Symphony, I can call one 'Beethoven - Symphony No. 9 [Karajan]' and the other 'Beethoven - Symphony No. 9 [Haitink]' and assign different AlbumSort tags. I have several recordings of (for example) Beethoven - Symphony No.9, which is all I use for 'album'. I distinguish between the different versions using 'Album artist': 'Karajan' in this case. Furthermore if you have multiple recordings of this symphony conducted by Karajan I distinguish between them by adding a date to the Album artist name e.g. 'Karajan (1964)' System: ALAC iTunes library on Synology DS923+ (running MinimServer) > NetGear router > Optical isolation > dCS Network Bridge (controlled by Galaxy Tab S2 tablet running BubbleUPnP&Mosaic) > PS Audio DirectStream DAC > Primare A60 > Harbeth SHL5plus 40th Anniversary model |
|||
|
09-03-2022, 14:57
Post: #12
|
|||
|
|||
|
RE: 'Album Sort' - unexpected behaviour
If you are using Conductor - album for display, you cannot remove the conductor from the album title.
If you want albums sorted by conductor without including conductor in the album title, you could use this setting: Album.sortTags={Conductor, Album, Composer} |
|||
|
09-03-2022, 15:13
(This post was last modified: 09-03-2022 15:14 by RSJ.)
Post: #13
|
|||
|
|||
|
RE: 'Album Sort' - unexpected behaviour
That is exactly what I do at the moment (I am responding to DavidL's comment). However, I also use the AlbumSort tag as a way of listing albums in the correct order. Otherwise, all dual-symphony albums which start, for example, 'Beethoven - Symphonies Nos. 6 & 7' appear before single symphony albums - e.g. 'Beethoven - Symphony No. 3'. I have got around this by have an AlbumSort tag of (for the example above) 'Beethoven - Symphony No. 6 & 7'.
However, Simon has indicated that different AlbumSort tags cannot be used for albums that have the same name - e.g. three versions of Beethoven's 9th symphony cannot have different AlbumSort tags if they all have the same Album tag. What I had wanted to do was create a 'flight' of, say, Haitink's recordings of the Beethoven symphonies with the LSO, followed by the Karajan BP recordings. My plan was to do this by including the conductor's name after the first part of the album name in the AlbumSort tag (e.g. 'Beethoven Symphony Haitink No. 3'). This works if the Album tags/names are all different, but not if they are the same. So, where there are dual symphony recordings with different pairs of symphonies, there is not an issue. But a conflict is created for the single symphony recordings which have the same Album name. |
|||
|
09-03-2022, 16:36
(This post was last modified: 09-03-2022 16:54 by simbun.)
Post: #14
|
|||
|
|||
RE: 'Album Sort' - unexpected behaviour
(09-03-2022 15:13)RSJ Wrote: However, Simon has indicated that different AlbumSort tags cannot be used for albums that have the same name - e.g. three versions of Beethoven's 9th symphony cannot have different AlbumSort tags if they all have the same Album tag. It's because of the album.value.sort setting. (08-03-2022 22:37)RSJ Wrote: tagOptions I might be having a moment here, but what are you using album.value.sort for, can't you just use Album.sortTags={AlbumSort, Album, Composer}? EDIT: Sorry, it's probably not fully populated! I'll have a try applying a .default to AlbumSort |
|||
|
09-03-2022, 16:55
(This post was last modified: 09-03-2022 16:55 by RSJ.)
Post: #15
|
|||
|
|||
RE: 'Album Sort' - unexpected behaviour
(09-03-2022 16:36)simbun Wrote: I might be having a moment here, but what are you using album.value.sort for, can't you just use Album.sortTags={AlbumSort, Album, Composer}? I think it is probably the way that I am explaining what I am trying to do... Assume for the moment that the only recordings of Beethoven symphonies I have are conducted by Karajan and Haitink. What I am trying to achieve is that the listing of the Haitink recordings appears in symphony order and then the listing of Karajan recordings. This is a change from the way that I previously had them displayed, which was simply in symphony number order, regardless of the conductor. I thought that I could use the AlbumSort tag to achieve this. |
|||
|
09-03-2022, 17:00
(This post was last modified: 09-03-2022 17:23 by simbun.)
Post: #16
|
|||
|
|||
|
RE: 'Album Sort' - unexpected behaviour
If you change tagValue to:
Artist.Value.Sort={AlbumArtist}, AlbumSort.default={Album} and then have tagOptions: Album.sortTags={Composer, AlbumSort} Does that give you what you want? |
|||
|
09-03-2022, 17:25
Post: #17
|
|||
|
|||
|
RE: 'Album Sort' - unexpected behaviour
Thank you for the suggestion. I will give that a try tomorrow evening (I am not at home at the moment).
|
|||
|
09-03-2022, 17:58
Post: #18
|
|||
|
|||
|
RE: 'Album Sort' - unexpected behaviour
I'm not sure whether you saw this post. It suggests a small change to what you already have that I think will do what you want.
|
|||
|
09-03-2022, 23:40
(This post was last modified: 09-03-2022 23:58 by simbun.)
Post: #19
|
|||
|
|||
|
RE: 'Album Sort' - unexpected behaviour
As much for my own understanding as anything else...
@RSJ, hopefully to clarify a few things... Unless I'm mistaken, it looks like you've:
The configuration being used is: Code: tagOptions: Album.sortTags={Album, Composer}, all.ignore.sort={The, THE, the}, Composer.reverseName.displayYou say that it's mostly working apart from a few exceptions, and I believe those exceptions (highlighted in the log) are because of the setting: album.value.sort={AlbumSort} <source-tag>.value.sort={<target-tag>} is used to tell MinimServer how to sort the values in <source-tag>, it's like saying Mon = 1, Tue = 2, Wed = 3 ...., so you can't have 'Beethoven Symphony No. 9' (the album tag) map to both 'Beethoven Symphony Haitink No. 9' and 'Beethoven Symphony Karajan No. 9' (the albumsort tags); it's typically used for defining the sort order of tags used in Indexes (as all the unique values of <source-tag> are presented in a list), but also tags like AlbumArtist and Artist that have a one to one mapping. So, without that configuration option you're able to have one AlbumSort value per "Album" (as defined by MinimServer as mostly a unique combination of Album and AlbumArtist). In your case you said you use the same logic as @DavidL, so have Conductor as AlbumArtist, which means you can have: Code: AlbumArtist Album AlbumSortSo to get your [%COMPOSER% Symphony %CONDUCTOR% No. X] sort you would need to change your original config to: Code: tagOptions: Album.sortTags={AlbumSort}, all.ignore.sort={The, THE, the}, Composer.reverseName.displayIf AlbumSort isn't always populated you'd also need: Code: tagValue: AlbumSort.default={Album}Hope that makes sense. |
|||
|
10-03-2022, 19:40
Post: #20
|
|||
|
|||
RE: 'Album Sort' - unexpected behaviour
(09-03-2022 14:57)simoncn Wrote: If you are using Conductor - album for display, you cannot remove the conductor from the album title. Unfortunately, this does not work, because it simply sorts by conductor and then album, whereas I want to sort by conductor at a lower level (i.e. within certain musical works by a composer). |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 2 Guest(s)

Search
Member List
Calendar
Help



