Audacity Forum

... me to recover the project, but I got the error "not well formed (invalid token) at line 1105. I just had to delete line 1105, which was virtually ...

shortyzpapa815 wrote:Alright, did that and upgraded to the newer beta...but now I get an "error: not well-formed (invalid token) at line 8 and 10" respectively, for both of them.

Please upload both .aup files using "Upload attachment" underneath the buttons where you write your posts.



Gale

Alright, did that and upgraded to the newer beta...but now I get an "error: not well-formed (invalid token) at line 8 and 10" respectively, for both of them.

... problem will still occur". I read that as the invalid token error occurring (the subject of the topic). All we can reproduce ...

... the file is ANSI encoded, and this caused an "Invalid Token" error in both the Unicode version of Audacity and the ANSI version. ...

... this recently with German and East Asian characters on English Windows - if the file was made with the ANSI version of Audacity, it opens without error but with the Unicode characters incorrectly displayed. The problem is the same as we've seen before - somehow the .aup file written by the ANSI ...

Please,

need to solve this problem when I open the project: (Error not well-formed (invalid token) at line 7)

help urgent

thanks

Hey! Help me Please!!! When I try to open an AUP file it says "Error: not well-formed (invalid token) in line 1215" or some other number. How can i fix it? Helppp please!

... one, this time on a Mac: [*] http://www.audacity-forum.de/post/21795 - error: "Reference to invalid character in line 9" If they are on Audacity 1.2 they will get that problem (also if ...

... one, this time on a Mac: [*] http://www.audacity-forum.de/post/21795 - error: "Reference to invalid character in line 9" @Gale: I will try to produce a broken Audacity project with detailed ...