Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 225 - Chains: Exported metadata tags are corrupted if they include Unicode tags
Chains: Exported metadata tags are corrupted if they include Unicode tags
Status: RESOLVED FIXED
Product: Audacity
Classification: Unclassified
Component: Formats
1.3.14 alpha
PC Windows and Linux
: P3 Repeatable
Assigned To: Default Assignee for New Bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-09-12 23:44 UTC by Gale Andrews
Modified: 2018-08-20 11:45 UTC (History)
3 users (show)

See Also:
Steps To Reproduce:
1 new project in Unicode version of SVN HEAD 2 File > Import > Audio > attached 情義兩心知.mp3 and verify the tags 3 File > Close to ensure stored metadata is cleared 4 File > Apply Chain... 5 Select "MP3 Conversion" chain, click "Apply to Files" and open the attached 情義兩心知.mp3 6 File > Close to ensure stored metadata is cleared 7 File > Import > Audio and choose the created 情義兩心知.mp3 from the "Cleaned" folder 8. File > Open Metadata Editor and note the tags have been corrupted/removed. The Unicode tags have been replaced with dots, Genre changed from "Pop" to "Blues" and the Year and Replay Gain tags removed.
Release Note:
If an imported file includes Unicode metadata tags and the file is exported using an Export command in a chain, the exported tags may be corrupted. Workaround: Import the file(s) via File > Import > Audio, apply the chain (minus the export step) to the project , then File > Export Multiple.
First Git SHA:
Group: ---
Workaround:
Closed: 2018-08-20 00:00:00


Attachments
情義兩心知.mp3 with Unicode tags which are corrupted by Chain export (9.21 MB, audio/mp3)
2010-09-12 23:44 UTC, Gale Andrews
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gale Andrews 2010-09-12 23:44:59 UTC
Created attachment 39 [details]
情義兩心知.mp3 with Unicode tags which are corrupted by Chain export

Also the user who reported this on Win XP SP 3 and Win 7 said that a message
box appeared "The specified filename could not be converted due to Unicode
character use", though the filename was created correctly.[1] I do not have the
file that caused the message to appear at the moment. 

This bug is not apparently a problem on Ubuntu. There is no problem on Windows
if the tags in the file exported from the chain do not contain Unicode. There
is no problem on Windows with loss of Unicode tags when using export from the
File menu. 


[1] The message presumably comes from the following code at line 166 of
src/Internat.cpp:

#if defined(__WXMSW__)
//
// On Windows, wxString::mb_str() can return a NULL pointer if the
// conversion to multi-byte fails.  So, based on direction intent,
// returns a pointer to an empty string or prompts for a new name.
//
char *Internat::VerifyFilename(const wxString &s, bool input)
{
   static wxCharBuffer buf;
   wxString name = s;

   if (input) {
      if ((char *) (const char *)name.mb_str() == NULL) {
         name = wxEmptyString;
      }
   }
   else {
      wxFileName f(name);
      while ((char *) (const char *)name.mb_str() == NULL) {
         wxMessageBox(_("The specified filename could not be converted due to
Unicode character use."));

         name = FileSelector(_("Specify New Filename:"),
                             NULL,
                             name,
                             f.GetExt(),
                             wxT("*.") + f.GetExt(),
                             wxFD_SAVE | wxRESIZE_BORDER,
                             wxGetTopLevelParent(NULL));
      }
   }
Comment 1 Gale Andrews 2011-03-01 22:23:21 UTC
DEVEL-FIX MADE. r10979 removes any writing of ID3V1 tags. ID3V1 tags will still be imported, but they will be written as ID3V2 tags.
Comment 2 Gale Andrews 2011-03-04 05:35:06 UTC
I think this is fixed now - tested on Windows and Ubuntu with the file in the attachment. Changing to RESOLVED - FIXED.