DSF files date tag not always indexing.

[paulg]

(22-11-2023 00:11)simoncn Wrote:  DSF files use ID3v2 tags. Date tagging changed between ID3v2.3 and ID3v2.4 and some tagging programs don't handle this correctly.

Please try doing a full rescan. Does this produce any warning messages in the MinimServer log about Date tags in the files with this problem?

To do a full rescan, set the startupScan property to 'full' before you do the rescan.

I have had a play around with a test profile and it seems that the DATE tag only accepts a year entry (eg;2023).

In order to display a year against every DSF album and to still be able to order the albums by an artist in order of release I amended all the DATE tags to display just the year and then added a new wild tag called 'Channels2' and used this tag to add a consecutive count and then set the sort order of this new tag with a +.

Example.

Two albums by one artists released in 2022

With FLAC I would tag the DATE tag as 2022-01-01 and 2022-01-02 and set the sort order for the DATE tag with a + to display the 2022-01-01 first on my list of albums by this artist.

With DSF I have had to tag the DATE tag as 2022 for both albums and then add the sub tag to allow ordering into my new 'Channels2' tag so 01 on the first album and 02 on the second album.

Here is my new setup.

indexTags:

Artist, All Artists, Channels1:Compilations, Albumsort:Collections, Genre:Genres, Date:Year Of Release, Channels:Stereo / Multichannel, Grouping:Media Format / Audiophile Labels, *RecentAdded, *RecentPlayed, #AudioData, #AudioFormat, Channels2:.

tagOptions:

Album.sortTags={+Artist, +Date, +Channels2}, Date.yearOnly.index

tagValue:

Grouping.default={'Various Other'}, Channels1.default={'Non Compilations'}, Albumsort.default={'Non Collections'}, Channels.default={'Stereo'}, Channels2.default={'.'}

I used a . and moved it to the bottom of the list because I don't need to browse the tag, it is just to enable ordering of albums by the artist.