Seems to me that LMS would be better served to scan both COMMENT and DESCRIPTION and create multiple (or combined comments). The database is set up so that it could easily handle a one:many relationship, allowing more than one comment per track. The spec states that you can have multiple tagging fields of the same name (and it works with some fields, such as ARTIST). I've never tried to see what happens if you have more than one COMMENT field, but the expected behavior would be that you'd end up with two comments. So that should also be the behavior (IMO) if another field that is mapped to the same internal field is present.
Kind of an ironic in light of the behavior of 'bug 18126' (http://bugs.slimdevices.com/show_bug.cgi?id=18126). Maybe when that bug is fixed, this problem could be tackled at the same time. ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=105202 _______________________________________________ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/beta
