"file not well formed in line 6" error?

[Leland]

This should be fixed. If you want to try it, wait for the next nightly build found here:

http://audacity.homerow.net/index.php?dir=mac%2F

Leland

[Leland]

This should be fixed. If you want to try it, wait for the next nightly build found here:

http://audacity.homerow.net/index.php?dir=mac%2F

I should clarify this a bit.

The writing of non-printable characters and/or Unicode characters to the .aup should now be corrected. I do not know how the control characters (0x01 and 0x0d) were getting into the file in the first place and if anyone can provide a way to reproduce it that'd be great.

Leland

[Madrol]

Hello everyone! I speak small one in English excuse me. I am Hungarian and one Whoo the program loads up a character into the name of the audio lane. it is necessary to exchange this!

Sample: Audio Sáv 1 "á" character exchange to "á"

Or use the program on an English language. Good one needs it so according to me to be.

I hope so I was able to help somebody.

MaDRoL

[Gale Andrews]

Hello everyone! I speak small one in English excuse me. I am Hungarian and one Whoo the program loads up a character into the name of the audio lane. it is necessary to exchange this!

Sample: Audio Sáv 1 "á" character exchange to "á"

Or use the program on an English language. Good one needs it so according to me to be. MaDRoL

This may be difficult to to explain, but what version of Audacity are you using? You can check this at Audacity > About Audacity. If you have a 1.2 version of Audacity, it cannot understand accented characters like "á" if you use that character in a file or folder name, in a track name, a label or in a metadata tag. You need to download the Beta version of Audacity. The Beta (1.3) versions are Unicode, so understand accented characters.

If you download the current Beta (1.3.9) from the above link, and there is still a problem with foreign characters not displaying properly, please let us know exactly how to create the problem.


Gale

[Gale Andrews]

I should clarify this a bit. The writing of non-printable characters and/or Unicode characters to the .aup should now be corrected. I do not know how the control characters (0x01 and 0x0d) were getting into the file in the first place and if anyone can provide a way to reproduce it that'd be great.

We were provided with an iTunes MP4 file that seemed to reproduce the problem in the .aup file and are tracking it as Bug 147. Michael Chinen has now committed a fix which should show up in the Mac Nightly Build "2010.04.25-03.15" or later (that is, take the latest non-debug build from the bottom of the list).

Any comments on whether the iTunes file attached to Bug 147 saves and reopens correctly in the Nightly, and any tests you can do with other recently purchased iTunes files would be much appreciated. Please post any comments here. Note this only fixes the creation of new project files. Trying to open old .aup files that already have the unhandled characters will still fail.


I've also been told files from Walmart can have the same problem. As an aside, both Apple and Walmart are apparently among companies that embed personally identifiable information inside purchased files.


Thanks


Gale

[IAmADeadHead]

I have the same problem. I tried to repair it by myself using those techniques, but it still says "Not well-formed in line 21"
And my lines are :
<?xml version="1.0" standalone="no" ?>

<!DOCTYPE project PUBLIC "-//audacityproject-1.3.0//DTD//EN" "http://audacityteam.org/xml/audacityproject-1.3.0.dtd" >

<project xmlns="http://audacityteam.org/xml/" projname="Histoire de gars 003_data" version="1.3.0" audacityversion="1.3.12-beta" sel0="469.3891514155" sel1="469.3891514155" vpos="0" h="465.2998477241" zoom="47.6853798868" rate="44100">

<tags>

<tag name="id3v2" value="1"/>

<tag name="ARTIST" value="SoundJay.com Sound Effects"/>

<tag name="TITLE" value="E3812zyl_.aiff.au"/>

<tag name="YEAR" value="1999-09-01"/>

<tag name="Software" value="Sound Forge 4.5"/>

</tags>

<wavetrack name="Thème" channel="0" linked="1" mute="0" solo="0" height="20" minimized="0" rate="44100" gain="1" pan="0">

<waveclip offset="0.00000000">

<sequence maxsamples="262144" sampleformat="262159" numsamples="1974348">

<waveblock start="0.00000000">

<simpleblockfile filename="b00018.au" len="262144" min="-1" max="1" rms="0.130203"/>

</waveblock>

<waveblock start="262144">

<simpleblockfile filename="b00020.au" len="262144" min="-1" max="1" rms="0.130105"/>

</waveblock>

<waveblock start="524288">


<simpleblockfile filename="b00022.au" len="262144" min="-1" max="1" rms="0.132877"/>
</waveblock>

<waveblock start="786432">

<simpleblockfile filename="b00024.au" len="262144" min="-1" max="1" rms="0.180363"/>
</waveblock>

<waveblock start="1048576">

<simpleblockfile filename="b00026.au" len="262144" min="-1" max="1" rms="0.174083"/>

</waveblock>

I don't understand now... Could someone help me?
___
DxH

[steve]

I suspect it is the first "e" in "Theme"

<wavetrack name="Thème" channel="0" linked="1" mute="0" solo="0" height="20" minimized="0" rate="44100" gain="1" pan="0">

[IAmADeadHead]

I suspect it is the first "e" in "Theme"

<wavetrack name="Thème" channel="0" linked="1" mute="0" solo="0" height="20" minimized="0" rate="44100" gain="1" pan="0">

Yes, it worked! Oh my God I tried to fix this without even realizing that. I thought the Thème word was okay, since it's how we spell it in french.

Thank you!
___
DxH