"not well formed (invalid token)" error when recovering proj

[Franck Dernoncourt]

Just to let you know, my computer crashed while I was a recording the audio input with Audacity 1.3.14-beta (my Windows 7 x64 SP1 sometimes fights with the hardware, not Audacity's fault I believe). When I opened Audacity after reboot, Audacity offered 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 full of null characters (see enclosed zipped .autosave file), to make it work. (thank you XML!). I guess Audacity's recovering function could be easily modified to check for suspicious characters like wandering NULs to clean this kind of mess.

[kozikowski]

What did you use to view the xml with line numbers?

I guess Audacity's recovering function could be easily modified to check for suspicious characters like wandering NULs to clean this kind of mess.

Crashing doesn't always produce this exact problem, but are you volunteering to program that module? I can put you in touch with the right elves.

Koz

[Franck Dernoncourt]

What did you use to view the xml with line numbers?

Notepad++ and 010 Editor

are you volunteering to program that module?

Not sure I'll find the time but I'll have a look at the source code. On http://wiki.audacityteam.org/wiki/Developing_On_Windows, at line

To develop in C/C++ for Windows you need a second download from Microsoft, the "Platform SDK", or the later "Windows SDK". Check here for the one you require.

'Check here' points to a broken link. What's the right link?

[steve]

'Check here' points to a broken link. What's the right link?

This section of the wiki is being rewritten to bring it up to date, but it's not a simple job so it could be a while before it is fully updated.
Here are some interim notes on the subject: http://www.hometownband.org/CompilingAudacity.html
and a link for the Windows SDK: http://msdn.microsoft.com/en-us/library/ms717422.aspx

[steve]

Not sure I'll find the time but I'll have a look at the source code. On http://wiki.audacityteam.org/wiki/Developing_On_Windows, at line

To develop in C/C++ for Windows you need a second download from Microsoft, the "Platform SDK", or the later "Windows SDK". Check here for the one you require.

'Check here' points to a broken link. What's the right link?

The links on that page have just been updated.

[Gale Andrews]

To develop in C/C++ for Windows you need a second download from Microsoft, the "Platform SDK", or the later "Windows SDK". Check here for the one you require.

'Check here' points to a broken link. What's the right link?

I've updated the links a short while ago (but the page is as Steve says in a bit of a state of flux at present). The Windows SDK (Microsoft Windows SDK for Windows 7 and .NET Framework 4) is the one wanted for XP SP3 or later.

Note that Audacity doesn't support VS 2010.

On past experience, the developers probably won't want to handle nulls or anything specious in the .aup file (such as a control character), so it would mean a direct clean up/removal of the problem.



Gale

[Franck Dernoncourt]

The links on that page have just been updated.

I've updated the links a short while ago

Thanks!

the developers probably won't want to handle nulls or anything specious in the .aup file (such as a control character)

Why?

[Gale Andrews]

the developers probably won't want to handle nulls or anything specious in the .aup file (such as a control character)

Why?

Because the argument went that handling/ignoring specious characters in the .aup could create unpredictability in the project.

For example a few Beta versions ago, some files from iTunes contained metadata that would corrupt the .aup on Mac computers. We stopped that corruption occurring by preventing those characters being parsed into the .aup, but .aup files that already have those characters are refused with an error message.


Gale