"Error: reference to invalid number at line N" on 1.3.12

[kowk]

Thanks for the input.

I downloaded and applied the Security Update. The problem didn't get away, however.

I tried out retyping the filename suggested by Storer. It was successful. This suggests that import of filenames does not work fine under Mac OS X, perhaps due to some kind of character encoding error?

Kow K.

[kozikowski]

<<<I tried out retyping the filename suggested by Storer. It was successful. This suggests that import of filenames does not work fine under Mac OS X, perhaps due to some kind of character encoding error?>>>

No. It suggests that when you typed the original filename, you pressed, for example, the bell character (Control-G) by accident instead of a real printable filename character. Mac OS may have hidden it from you. OS-X does that occasionally to "help you."

I wonder if you wanted to go through the bother of finding the file in Terminal instead of the heavily graphic desktop and finder, that would show you [^G] instead of a normal blank space.

Koz

[kozikowski]

Which leads directly to the geek joke...

For whom the ^G tolls, It tolls for thee.

Koz

[kozikowski]

I can tie that to the original error, too. Folders, directories and filenames are burned into the AUP XML listings. The AUP file may have been happy with oddball characters inside the filename, but Mac OS may hot have. Or reverse.

Koz

[bgravato]

The inumerous different codepages and character set encodings available can drive one crazy... Even more if you have to make it work across multiple OSes... That's why I always try to stick to the standard alphanumeric characters only (and the ocasional underscore or dash instead of spaces, which can be trouble makers sometimes too...)

[kozikowski]

<<<spaces, which can be trouble makers sometimes too..>>>

I didn't pay him to say that.

I have to manage files across hundreds of different machines across three continents. It is the policy not to put spaces in filenames.

Koz

[bgravato]

One of my biggest problems with spaces is when I want to process a lot of files in batch mode, using shell scripts from the command line... spaces always make my life harder so I avoid them at all costs

[palmaccheer]

I have the invalid line at #7. Can someone tell me what needs to be changed? I have spent a considerable amount of time creating a dance routine and now it is unusable.

<?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="Cheer Music_data" version="1.3.0" audacityversion="1.3.12-beta" sel0="105.9200000000" sel1="168.9200000000" vpos="0" h="26.1261840585" zoom="11.8654909307" rate="44100">
<tags>
<tag name="id3v2" value="1"/>
<tag name="ARTIST" value="Ke$ha"/>
<tag name="Full Name" value="Boom Boom PowX&#x0002;"/>
<tag name="Author" value="Lukasz "Doctor Luke" Gottwald, Kesha & Benjamin Levin.au"/>
<tag name="Copyright" value="&#x2117; 2010 RCA Records, a unit of Sony Music Entertainment"/>
<tag name="ALBUM" value="Animal"/>
</tags>
<wavetrack name="01 Bad Romance 1" channel="0" linked="1" mute="0" solo="0" height="150" minimized="0" rate="44100" gain="1" pan="0">
<waveclip offset="-0.08126984">
<sequence maxsamples="524288" sampleformat="131073" numsamples="491186">

[bgravato]

Line 7 is this one:

Code: Select all

<tag name="Full Name" value="Boom Boom PowX&#x0002;"/>

Try removing the &#x0002; part from it...

Line 9 might give you problem too... if so try equivalent solution...

[palmaccheer]

I removed the invalid characters and now I am getting an error stating that there are 29 missing audio files. How do I get the audio files to stay with the .aup file?