I had a very similar problem appear after upgrading from v2.35 to v2.36. It turns out that this is due to the default ID3v2 character coding changing from UTF-16 to UTF-8. I think this is a bug: /t/3397/1
I had a very similar problem appear after upgrading from v2.35 to v2.36. It turns out that this is due to the default ID3v2 character coding changing from UTF-16 to UTF-8. I think this is a bug: /t/3397/1