Audacity Forum

I know what it is and I know how to fix it, but I don't remember how to tell on a Mac where the problem is. You can open up your AUP file in TextEdit and read it. It's not a sound file. It's computer programming in semi-English. http://kozco.com/tech/audacity/aup1.jpg This is a picture of a very sim...

Make a copy of the .aup file. Then open the original .aup file with TextEdit. Look for a section like this: <tags> <tag name="id3v2" value="1"/> <tag name="ALBUM" value="An Album Title"/> <tag name="ARTIST" value="The Artistes"/> </tags> So...

... project file, i received the following error message: Error: not well-informed (invalid token) at line 8 does anyone know how to correct this? i am using ...

Audacity 1.3.9 and later should be able to handle Unicode characters correctly. However, it is strongly recommended that you stick to alpha-numeric characters (a-z A-Z 0-9), space, hyphen and underscore for file names. Even if Audacity can handle these names correctly, there is a very good chance th...

Audacity doesn't like the Hungarian word Audio Sáv. It only accepts Audio Track. It's -weird, but it's true.

See those accented characters? Audacity chokes on them. Carefully edit them to unaccented versions and you should be good to go.

-- Bill

Hello, I've been working on a project lately. And trying to open it It gave me the error written above. Is it possible to recover the project and if, then how. Further ease of solving. I'll paste the first 20 lines of the project data code here. They have been copied ...

"Error: not well-formed (invalid token) at line 393." You need to see what is on line 393 of the .AUP ...

... but when I try to recover I get "Error: not well-formed (invalid token) at line 393." Since the file exists, but recovery is ...

... there are no forbidden characters. The exact error message I receive is: "Error: not well-formed (invalid token) at line 6" Can anyone help me? This is the .aup file ...