Audacity Forum

So Ive been trying to work through this problem for a long time now, i have audacity 1.2.6 and I like to export my projects as wavs. Its been happening increasingly, I create a song, save it, try to return to the audacity file and i get the message:

"Error: Not well-formed at line...(whatever line it may be)"

so ive read up on here alittle bit, try to open the audacity file in a txt document and see if i can find an illegal character of some sort but i have never been successfulll....

on the latest error i got a "not well formed at line 93" so i unwordwrapped the txt document and it only had like 50 or so lines, not even 93...it leaves me confused and frustrated...

if any one can help me out and save some of the music ive made i would appreciate it infinately!

Thank you...

You may have unwrapped too far. The AUP file is standard XML Extensible Markup Language and it follows standard opening and closing tags format. "Hello, my name is <name> Koz </name>.

Knowing that, you can intelligently unwind an AUP file like this simple one:

http://kozco.com/tech/audacity/aup1.jpg

I added blank lines to make it a little easier to read, but that's an actual file. Even at that I think there's one or two unwinding errors.

That's not to say it's easy. It's not, and Macs like to hide "illegal" characters, so even if I find one, I can't see it.

And are you sure you're unwinding the right AUP file. Look at the top lines and make sure they match the show. There are standard places to get errors -- like when you put funny characters in a metadata listing, a problem that happens constantly in Audacity 1.2. If you pull yourself out of this one, you might want to seriously consider upgrading to Audacity 1.3.12.

http://audacityteam.org/download/

Koz

I would also recommend upgrading to Audacity 1.3.12, and keep an eye out for 1.3.13 which is due for release soon. (there are still some characters that 1.3.12 has trouble with and 1.3.13 should fix these).

Another possibility is that if Audacity 1.2.6 crashed you may have a truncated or mashed .AUP file. If you attach the .AUP file to your post we can have a look (see "Upload Attachment" below the compose message box).