Re: [Audacity-devel] Several "Export" commands for batch chains patch
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Gale A. <ga...@au...> - 2013-08-02 14:01:55
|
| From Joel Bouchat <bo...@ho...> | Fri, 2 Aug 2013 12:14:29 +0200 | Subject: [Audacity-devel] Several "Export" commands for batch chains patchþ > Gale wrote: > > > Hi Joel, > > > > I just noticed on Windows 7 x64 SP1 running English UK format that > > although Windows Media Player doesn't see the tags in a WAV file > > exported from Audacity, it does see them if I edit and save the tags > > in Foobar2000 before opening the file in WMP. To check, look at the > > File's properties in WMP. > > > > Can you replicate this and might it be worth looking into? I don't > > want to necessarily assume it's repeatable because I have > > dBPowerAmp on this machine which does sometimes cause more > > metadata to be seen by Windows apps. > > > > > > > > > > Gale > > > Yes you are right, WMP can extract the ID3 tags from a file created by > foobar2000 but not from a file exported from Audacity. > > At least at the condition that foobar200 creates this WAV file directly > from the original mp3 file. > When i create a WAV file with AUdacity and modify its tags with > foobar2000, WMP cannot read the ID3 tags anyway. What version of Windows and WMP is that, and is Windows running in French? I have now tried it on my Windows 7 32-bit which does not have dBPowerAmp (English UK locale). I find that if I fill the seven standard tags in Audacity's Metadata Editor, export as WAV, edit the metadata and OK in Foobar, WMP 12.0.7601.17514 then sees Title, Artist, Album and Genre in that WAV (I did not export the other tags it lists). > There is certainly a difference between the ID3v2 metadata formatted > by Audacity and the metadata formatted by foobar2000. Yes, and Foobar can apparently cope with reading the UTF16 metadata in this MP3 file: http://forum.audacityteam.org/download/file.php?id=8008 whereas Audacity seems to produce corrupted characters. > We rely on "LIBID3TAG" to create the ID3 tags, and there is little that > can be done inside Audacity code itself. > To avoid encoding mixture, i have try to force the format to UTF16 > and next to ISO_8859_1 but this makes no difference: foobar200 reads > both formats without problem and WMP reads none of them! What is your or others' view of switching to taglib? http://taglib.github.com/ It has been proposed before and there is a bug open to do it: it http://bugzilla.audacityteam.org/show_bug.cgi?id=364 . However the main reason to do it given there was to improve WAV metadata which has largely been achieved now with your patch for this (thanks!). Gale |