Bugzilla – Bug 4554
More then one DATE tag gives gibberish results
Last modified: 2011-11-06 23:22:54 UTC
Once upon a time I found a document describing a tagging method for Vorbis audio files (which applies to FLAC since FLAC uses Vorbis tags). http://reactor-core.org/ogg-tagging.html That document recommended a format for the DATE tag with the date first, optionally followed by a space and an alphanumeric string. I have included multiple DATE tags with alphanumeric comments for each denoting (composed), (recorded), etc. In the slimserver database, the date/year either doesn't show at all, or is assigned to some arbitrary and meaningless four digit value (5398 or 9544 for examples). Here is an example of my tags: comment[0]: ARTISTSORT=Bach, J.S. comment[1]: TRACKNUMBER=03 comment[2]: REPLAYGAIN_TRACK_PEAK=0.40563965 comment[3]: REPLAYGAIN_TRACK_GAIN=+3.44 dB comment[4]: REPLAYGAIN_ALBUM_PEAK=0.40563965 comment[5]: REPLAYGAIN_ALBUM_GAIN=+4.01 dB comment[6]: DATE=1722 (composed) comment[7]: DATE=1983 (recorded) comment[8]: ARTIST=Bach, J.S. comment[9]: PERFORMER=Koopman, Ton comment[10]: TITLE=C minor (Prelude) comment[11]: ALBUM=Das Wohltemperierte Klavier Band 1 comment[12]: OPUS=BWV 847 comment[13]: GENRE=Classical comment[14]: COMPOSER=Bach, J.S. The date shows up in the album browse level as 9543. At the track detail level, the year is not shown at all.
Steven could you have a quick look at this? Should be reproducible in other OSes.
This is the behavior I am seeing: If I tag a FLAC file with a date tag that has more then 4 alpha numeric characters they are ignored in Slimserver. For example a file tagged with: DATE=1722 01 01 (composed) Will result with a Year of 1722 in Slimserver. This is the behavior I expected. Now if I tag a FLAC file with more then one date tag I get an unpredictable result in Slimserver. For example if I tag a FLAC file with: DATE=1722 DATE=1983 will result with a Year of 5963 in Slimserver. If I tag a FLAC file with: DATE=1722 01 01 (composed) DATE=1983 06 06 (recorded) will also result in a Year of 5963 in Slimserver. So it looks like the behavior is caused by more then one DATE tag and I changed the summary to reflect this.
Unassigned bugs cannot have a priority.