![]() |
|
Controlling Track Sorting when multi-disc and multi-audio quality - Printable Version +- MinimServer Forum (https://forum.minimserver.com) +-- Forum: MinimServer (/forumdisplay.php?fid=1) +--- Forum: General (/forumdisplay.php?fid=2) +--- Thread: Controlling Track Sorting when multi-disc and multi-audio quality (/showthread.php?tid=6944) |
Controlling Track Sorting when multi-disc and multi-audio quality - SonicREP - 22-06-2023 00:31 I’m new to using minimserver and customizing tagFormats and tagOptions, so any suggestions would be appreciated. I want to sort the tracks for an album when the album has to two different quality levels and multiple discs. My example album is: Ella & Louis Again, which is a 2 disc set, that I have encoded as 24/96 and 256K. As renderers I am using Wiim Home app, but the issue also shows up in Linn. When the Album is shown (screenshot), the disc are separated (as expected due to showAllDiscs=true), but the tracks appear to be automatically sorted by "Track Number" and then possibly(?) sorted secondarily by AudioQuality. Track 1 is shown with two quality versions, then track 2, ... I want to have disc 1, followed by the tracks for HD [24/96], followed by the tracks for [256k], then disc 2, ... Effectively sorting the tracks by AudioQuality, Track Number. I‘m looking for the minimserver property that controls sorting tracks, or alternatively needing to understand if this is something done automatically by the renderer (Wiim or Linn) and can’t be affected through minimserver. My understanding of sortTags is that they can be set for Album.sortTags and Folder.sortTags. However, I could not determine how to affect the sorting of tracks when an album is displayed and wondered if minimserver offers control over the track sorting. Ideally I'd hope to use minimserver to set a tagOption to customize the track sort to be "AudioQuality, Track Number" (or whatever I’d like the track sorting to be). An additional question is about what generates what I’ll call the “subtitle” under each track (screenshot). i.e., Ella Fitzgerald; Louis Armstrong- Ella and Louis Again (1967) (1, 2) HD, LC [24/96, 256K] It appears to be a concatenation of the tracks's Artist tag (with ‘;’ delimiters) and the Album.displayFormat from my config. Perhaps this is something done by the renderers (Wiim or Linn). I see no reason to duplicate the Album.displayFormat in this subtitle. Is there a property within minimserver to control this “subtitle” (as I’ve named it)? Here are the tags for one of the tracks on Ella & Louis Again: Generic tags Label Value Property name Track title Makin' Whoopee title Track number 2 / 19 track Disk or media number 1 disk Artist Ella Fitzgerald; Louis Armstrong artist Artists Ella Fitzgerald; Louis Armstrong artists Album artist Ella Fitzgerald albumartist Composer Walter Donaldson composer Release year 1957 year Album Ella And Louis Again album Release date 1957-02-25 date Release label name(s) n/a label Genres Jazz, Jazz vocal genre Copyright. ℗ 1957 UMG Recordings, Inc. copyright Native tags vorbis Key Value LABEL n/a TRACKTOTAL 19 COPYRIGHT ℗ 1957 UMG Recordings, Inc. TITLE Makin' Whoopee ARTIST Ella Fitzgerald; Louis Armstrong ALBUM Ella And Louis Again GENRE Jazz, Jazz vocal ALBUMARTIST Ella Fitzgerald COMPOSER Walter Donaldson DISCNUMBER 1 DATE 1957-02-25 TRACKNUMBER 2 METADATA_BLOCK_PICTURE [object Object] I’d appreciate help understanding the best way to do this (or a different way to think about my problem). Here is my current config. .configVersion = 2.2.105 .licenseType = full minimserver.activeProfile = default minimserver.monitorUDN = d906bc03-2725-4fbc-988d-a0f66e4b345d minimserver.udn = 6390a70b-95be-4a4a-a623-5e4818a09e44 minimserver.systemUpdateID = 156 minimserver.configVersion = 2.2.109 minimserver.license = 2.0.4 .updatesExpiry = 20240608 minimserver.contentDir = /Users/.../Media/TAG TEST minimserver.displayName = Test MinimServer minimserver.indexTags = Artist, Date, Genre, All Artists, Composer, *RecentAdded, *RecentPlayed, \#AudioData, \#AudioFormat, \#AudioQuality, DISCNUMBER, Comment minimserver.itemTags = TrackNumber, TotalTracks, Disc, \#AudioDuration, ArtistSort, albumartist, AudioQuality, AudioData minimserver.tagOptions = Album.sortTags\={Date, AlbumArtist, \#AudioQuality}, Composer.reverseName.display, all.ignore.sort\={The, THE, the}, Date.yearOnly.* minimserver.tagValue = AlbumArtist.default\={Artist},Artist.Value.Sort\={ArtistSort} minimserver.tagFormat = Title.displayFormat\={$tracknumber^$totaltracks^/^$title^. $\#audioquality^ $\#audiodata^ [^]^}, Album.displayFormat\={$album^ ^$Date^ (^) ^$DiscNumber^ (^) $totaltracks^ $\#audioquality^ $\#audiodata^ [^]}, Comment.displayFormat\={$*infoFileURI^<a href\=&\#x22;^&\#x22;>Digital booklet</a>$comment} .autoUpdate = true minimserver.lastRescan = 1687371173160 minimserver.noWelcomePage = 2.2 http.listenerPort = 9790 minimserver.listViewAlbums = 25 minimserver.serverOptions = indexArtwork\=auto,showAllDiscs\=true .logLevel = debug watch.logDimension = 1125,446 .integrityCheck = 282e49b0bb26595e69bc4125aac191278 RE: Controlling Track Sorting when multi-disc and multi-audio quality - simoncn - 22-06-2023 09:52 The sort order for tracks within an album is by track number and then by track title if track numbers are equal. There is no MinimServer configuration property to change this. The "subtitle" appears to be a combination of the artist property and album property that the control point receives from the server. Diffferent control points provide different information here. If you want both sets of tracks to appear as a combined list under the same album disc, you can sort the 256k tracks to the end of the list by giving them track numbers 101, 102, etc. instead of 1, 2, etc. To automate this, you can create a tag update file containing the following: @TRACKNUMBER=1 &AUDIOQUALITY=LC =TRACKNUMBER=101 @TRACKNUMBER=2 &AUDIOQUALITY=LC =TRACKNUMBER=102 etc. For details of how tag update files work, see this section. The tag update file does not change track numbers in the files themselves, only the track numbers used by MinimServer and sent by MinimServer to the control point. Another option is to group all the 256k tracks together as a separate album by telling MinimServer not to merge the 256k folders with the 24/96 folders. To do this, you can use a match filter on the folder names as described in this section. RE: Controlling Track Sorting when multi-disc and multi-audio quality - SonicREP - 26-06-2023 22:33 Simon, thanks for taking the time to provide your suggestions. I was initially hopeful that MinimServer's flexibility would allow for setting the sort order on tracks without any additional modifications. However, I understand from your suggestions that achieving this requires either adding update files or modifying the organization and tagging within the existing files. While these methods can certainly be effective, they do involve altering existing elements. Nonetheless, I appreciate your input and will keep these options in mind. In my opinion, the most direct and simple solution would be to enable direct application of the sort order to the tracks. Perhaps this could be considered as a future option if it aligns with the direction that MinimServer is headed in. RE: Controlling Track Sorting when multi-disc and multi-audio quality - simbun - 27-06-2023 08:54 (22-06-2023 00:31)SonicREP Wrote: When the Album is shown (screenshot), the disc are separated (as expected due to showAllDiscs=true), but the tracks appear to be automatically sorted by "Track Number" and then possibly(?) sorted secondarily by AudioQuality. Track 1 is shown with two quality versions, then track 2, ...Whilst I too have a use case for a .sortTags at the track listing level, personally I don't think it's a good option in your use case as it doesn't allow you to easily enqueue the album/quality you're interested in. Assuming the tracks are in the order you requested (as below), the only way to enqueue the HD album would be to enqueue each track individually! Code: >> Disc 1You haven't actually said why you're indexing both a lossy and lossless version of the same release, but if you do this for every album then wouldn't it be easier to just filter on #AudioQuality before you got to the album level? |