Just added this to the bug report: Ok Ive done a little digging on this. Multiple tags of the same type is not a user error as it was common practice for various tag editors, especially for ARTIST (as opposed to a delimitered list in a single tag). I can see how some tag editors might have (perhaps erroneously) done the same with date tags (original release date, reissue release date).
The scanner already caters for multiple tags of the same type. If there is more than one tag it makes an array of the values against that tag name. Nothing is broken here it works perfectly. The bug is with the listing code for dates. The listing code works perfectly for multiple name tags, and lists an entry for each name in the array. And shows a comma delimited list of names in the record summary. However the listing code doesn't work for multiple date tags. They scan perfectly and are stored as an array of dates under that tag entry. However when they are shown in a date listing it appears as though the array is read as byte values assuming it is an integer, when it is in fact an array. eg. Date value 1: 1961, Date value 2: 1961 - Date listed: 2584 Date value 1: 1989, Date value 2: 1989 - Date listed: 4938 Date value 1: 1992, Date value 2: 2012-08-12 - Date listed: 5260 As per the Name tags, the date a record is listed under should be both 1992 and 2012, if two values are present, or a single year of both values are the same. If listing under two dates is not acceptable then probably by the first value in the array. Hope this makes sense. ------------------------------------------------------------------------ HumanMedia's Profile: http://forums.slimdevices.com/member.php?userid=44865 View this thread: http://forums.slimdevices.com/showthread.php?t=101516 _______________________________________________ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
