"comment" does't post to Properties when mp3 file is saved

[souprman]

On 1.3.13 beta - I noticed that every time I export an mp3 file (converting from wav to mp3) the table comes up to post the artist name etc and that works fine but the "comment" I post in there does not post to the Properties (right click the file and details tab and its not there.) So I have to enter it again there. No biggy but vs. 1.2.6 does it fine on my XP.
I like to use Audacity now on my Win64 Ultimate 3.8Mhz mach. Its import and exports much faster.

[Gale Andrews]

On 1.3.13 beta - I noticed that every time I export an mp3 file (converting from wav to mp3) the table comes up to post the artist name etc and that works fine but the "comment" I post in there does not post to the Properties (right click the file and details tab and its not there.) So I have to enter it again there. No biggy but vs. 1.2.6 does it fine on my XP.
I like to use Audacity now on my Win64 Ultimate 3.8Mhz mach. Its import and exports much faster.

Thanks. This is already known about, as you can see in the 1.3.13 Release Notes. The problem is that the "language" of the Comments tag is treated differently by different player software. iTunes doesn't accept the language being set to "XXX" for undefined as it was in Audacity 1.2.6, thus iTunes could not see the 1.2.6 Comments tag. So in 1.3 we left the language bytes empty, which iTunes accepts but Windows Explorer and Windows Media Player do not. It seems Windows is out of step here, as per the comment in "Audiograbber" on http://www.id3.org/Compliance_Issues:

If a language is unknown or undefined, the Language Code should be left blank.

Unfortunately, you can't write the Comment twice (once empty and once with "XXX" for Windows), because only one language is allowed in the Comments - if two Comments exist with different languages, only the first Comment is read. And although iTunes accepts DEF for "undefined", Windows doesn't.

So I'm figuring the only answer is to specify "ENG" for English, which every other application I tried does. I'll try and find out if this creates any problems with reading non-Latin characters where the operating system isn't actually running in English.


Gale

[Gale Andrews]

So I'm figuring the only answer is to specify "ENG" for English, which every other application I tried does. I'll try and find out if this creates any problems with reading non-Latin characters where the operating system isn't actually running in English.

Here is an unofficial build that writes the Comments tag in English:
http://www.gaclrecords.org.uk/audacity- ... mments.zip

It should work fine on Windows running in English. If anyone running Windows in some other language could test it, it would be very helpful (I've asked edgar-rft off-Forum).

1) The comments tag in the included "eng_comments_in_deutsch_nihongo.mp3"
reads:

English Füße 田中さ

Does it appear correctly in Windows running in your language? Please check in Windows Media Player and by right-clicking the file > Properties in Windows Explorer.

2) If you create some MP3's with comments in your language (including as many non-Latin characters as you can), do you see what you intended in Windows Media Player and Explorer Properties?

PS It occurred to me there might be some way to set the system language for the tag, but I couldn't find anything about it.



Thanks


Gale