by chrisjj » Thu Jun 25, 2009 7:00 pm
MM's default reading/writing of WAV tags (UTF-8 encoding in an ANSI field) is non-compliant with the standard (
http://www.saettler.com/RIFFMCI/riffmci.html), causing written tags to have garbage characters when viewed by compliant programs, and causing tags in files written by compliant chars to faulty display in MM (see
http://www.mediamonkey.com/forum/viewto ... 90#p170990.)
I think very few if any other programs use MM's non-standard flavour (
http://www.mediamonkey.com/support/inde ... icleid=111), so the only advantage I see in MM's behaviour is some increased functionailty in MM-to-MM round trip. This IMO does not outweigh the cost of the failures.
Hence i suggest that MM should be changed to use standard WAV tagging by default.
Wish tracked at
http://www.ventismedia.com/mantis/view.php?id=5847MM's default reading/writing of WAV tags (UTF-8 encoding in an ANSI field) is non-compliant with the standard (http://www.saettler.com/RIFFMCI/riffmci.html), causing written tags to have garbage characters when viewed by compliant programs, and causing tags in files written by compliant chars to faulty display in MM (see http://www.mediamonkey.com/forum/viewtopic.php?p=170990#p170990.)
I think very few if any other programs use MM's non-standard flavour (http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=111), so the only advantage I see in MM's behaviour is some increased functionailty in MM-to-MM round trip. This IMO does not outweigh the cost of the failures.
Hence i suggest that MM should be changed to use standard WAV tagging by default.
Wish tracked at http://www.ventismedia.com/mantis/view.php?id=5847