Storage problem v 1.3.13-beta

[steve]

Could you try opening this AUP in the Unicode version of Audacity. It will need to be in the same directory as the folder "Test 4 ANSI created_data".

[Edgar]

In "audacity 1.3.13 (ANSI)" I opened an existing wav-file. This file containes the characters "°" and "ü" within the "Metadaten Editor...".

Hello Dieter!

What application was used to create the metadata in the WAV file in the first place?

Would you be willing to attach this WAV file? You could delete almost all the the audio (it is the metadata we are interested in) but if you edit it use the ANSI version (and to be on the safe side, make sure the new shortened WAV still creates a bad project). You might have to Zip the WAV file before you can attach it!

[Fleischmann]

Hello Steve,

I apologize I reply so late but as a real greenhorn I did not realize there are consecutive pages on the forum board.

I tell what I did:

I downloaded "Test 4 UNICODE.aup" to the folder containing the folder "Test 4 ANSI created_data" (and the file "Test 4 ANSI created.aup").
I opened "Audacity ® 1.3.12-beta (Unicode)" within I opened successfully the project "Test 4 UNICODE.aup". It shows data (i.e. the project) of "Test 4 ANSI created_data".


Hello Edgar,

Originally I produce wav-files. I open these wav-files in audacity and tag them within the "Metadaten Editor...". After finishing editing the stereo tracks I store the project as aup-file. Because mp3-players cannot read aup-files I export the stored aup-file, formerly as wav-file (44,1kHz/16bit), nowadays as mp3-file (320kbit/s floating).

I am sorry I close this message now because I lost the survey what to do. Of course you can have the wav-file but I must clean my brain first! Please be patient a while. I will be back soon!

Dieter

[steve]

I downloaded "Test 4 UNICODE.aup" to the folder containing the folder "Test 4 ANSI created_data" (and the file "Test 4 ANSI created.aup").
I opened "Audacity ® 1.3.12-beta (Unicode)" within I opened successfully the project "Test 4 UNICODE.aup". It shows data (i.e. the project) of "Test 4 ANSI created_data".

Is the metadata correct?

[Fleischmann]

Hello Steve,

If I open project "Test 4 UNICODE.aup" in "3.1.12 (Unicode)" metadata shows "°" and "ü".

If I open project "Test 4 UNICODE.aup" in "3.1.13 (ANSI)" metadata shows "°" and "ü".

Dieter

[Fleischmann]

Hello Edgar,

I am sorry I cannot verify what I wrote:
In "audacity 1.3.13 (ANSI)" I opened an existing wav-file. This file containes the characters "°" and "ü" within the "Metadaten Editor...".
The wav-file I opened contained "ä" and not "°" and "ü". I must have mixed up all the different files and versions. I replyed to Steve in this matter.

Nevertheless, if you think I could help, please tell me.

Dieter

[steve]

If I open project "Test 4 UNICODE.aup" in "3.1.12 (Unicode)" metadata shows "°" and "ü".

That file "Test 4 UNICODE.aup" was made by converting the original ANSI characters to Unicode.

I used G-Edit for the conversion (I'm on Linux). I'm assuming that Notepad++ can do the same.
When converting from ANSI to Unicode it is not enough to just change the character code of the troublesome characters, the file bust be re-saved using UTF-8 character encoding.
The method of converting using G-Edit was very quick and easy.
1) Open the .aup file in GEdit
2) Save the file and select "UTF-8" as the character encoding.
That's all.

[Edgar]

Nevertheless, if you think I could help, please tell me.

Dieter

The problem you are having may eventually affect other users. The current plan of the Audacity Team is to drop all ANSI support in the near future. If they had a very short WAV file with ANSI metadata containing "°" and or "ü" and could use ANSI Audacity to create an Audacity project (from that WAV) which failed to open in Unicode Audacity it would help the Audacity Programmers figure out how best to proceed.

Anyway, if you could attach the original WAV with ANSI metadata containing "°" and or "ü" I will bring it to the attention of the Programmers so they will have something to test.

[Gale Andrews]

In Notepad++, to convert your "Test 4 ANSI created.aup" which contains:

Code: Select all

<tags>
<tag name="GENRE" value="Drei Violinen und Klavier"/>
<tag name="TITLE" value="Caldara Sinfonia 4-3 Cembalo V1 V2 und Cembalo"/>
<tag name="YEAR" value="2011"/>
<tag name="ARTIST" value="Dieter Fleischmann und MIDI"/>
<tag name="COMMENTS" value="20110413; H2 90°, Dieter Grünke und MIDI"/>
</tags>

to ANSI as UTF8, you would choose Encoding > "Convert to UTF-8 without BOM" then save the .aup file. That would give you the same result in ANSI and Unicode Audacity (an openable project) as you had with the file Steve converted in Gedit.

However the real issue is how you got the above (i.e. the "°" appears as "°" in the .aup file and "ü" appears as "ü") in the .aup that 1.3.13 ANSI saved. You should have got "°" for the "°" and "ü" for the "ü" in that .aup file, then it would have opened in both versions of Audacity, albeit with incorrectly displayed characters in 1.3.13 ANSI.

Exactly how did you input the "°" in the Metadata Editor - with what input method or key sequence, or did you copy and paste the character from somewhere? Or was there a case where you did not type the metadata but an imported file had the metadata?

The issue you had definitely occurs quite often and isn't new, but I don't know how to actually reproduce it. It would not occur if Unicode versions of Audacity were used, so in that sense, removing ANSI support would be a good thing, to prevent ANSI versions being used for projects with Unicode characters. Note there is another method on the table to continue to support Win98/ME after 2.0 by supplying Unicode versions with the compatibility layer:
http://www.msfn.org/board/topic/130936- ... -45-final/

If we drop ANSI support after 2.0 but a user was in a position where only an ANSI version of Audacity would open the .aup file, they could still download a legacy ANSI Beta versions, or could still convert in Notepad++. I think it's a very poor reason for continuing to provide ANSI builds. @Dieter, do you actually have such an .aup file. that only opens in ANSI, but not Unicode? If so, please attach it.

And please, create all your new projects in Unicode Audacity. You don't need the ANSI version for new projects.



Gale

[Fleischmann]

Hello Steve, Edgar and Gale,

I must apologize for being quiet as long, but I feel I am demanded too much by this stuff. I was angry with me not being able to verify what I wrote myself. I mixed up files and versions and all together.

Since then I opened many projects using audacity v 1.3.13 and I am very pleased to say it is great and it meets all my demands, including the use of strange characters since I learned how to handle them.

Nevertheless if I shall stick to a problem about audacity I will try to put into words and contact the forum asking for help.

Many thanks to you all!

Dieter