Audacity Forum

I just recently downloaded audacity 1.3 and used it for a pod cast, this is the second time in a row this problem has happened on audacity 1.3

After we record it, we open it back up an hour later to Export it to a MP3, and the file is corrupt. It no longer recognizes the .au files that are linked to them. Whats even worse is that audacity 1.3 doesnt put the files in any particular order. I have downloaded Flexible renamer and renamed every file from 1.au to 1000.au or whatever the number is it goes up to. However after i do this, and try to use the Recovery program made for audacity 1.2 It doesnt recognize the au files in that folder anymore..

What im saying is.. We need these files to link to each other. so we need them numbered in order, however when i number them the Audacity recover file no longer recognizes the au files as .. well au files .. even though they still work

It seems the only way i could fix it is if i were to go through and renumber them by hand, rather then use the flexible renamer, .. however theres far to many files for that

ANY ONE.. have anything to help me.. maybe a new audacity recover tool for audacity 1.3
or anything

You should NEVER be attempting to manipulate the individual .au files. Theye are linked and controlled by the .aup file that you created when you SAVEd the project. You should then on subsequent uses open the .aup file.

Audacity projects are fragile little beings sometimes, that don't take kindly to being moved around or cleaned up.

WC

Well, I did the things this site itself has taught me to do in the past. If the files become unlinked, to find a renamer tool and rename all the au files. Then use audacity Recover.

Now.. i cant do that with out messing with the au files. I was hoping there is another way to link the 1.3 au files back to the original aup application..

I need help please

In no particular order:

One great problem with file renaming is the need for leading zeros.

1.au is not 999 orderly files away from 1000.au. 0001.au is. Computer numbering is nearsighted and stupid.

Are you absolutely certain that you're not moving anything around after the capture? How about using punctuation marks inside filenames? All punctuation marks except under_line and da-sh are forbidden and will cause troubles. Are you running out of hard drive space?

Audacity Projects are clouds of files and they're brittle. If you want to be certain of a successful capture, after the last note in the performance, Export As WAV... and park the large, single sound file somewhere safe. After you do that, it doesn't matter what happens to all those stupid au files.

Koz

One other note. the first two au files are graphics, not sound, and the number changes.

Koz

<<<We need these files to link to each other.>>>

We need your projects to stop failing. If you're on a PC, when was the last time you updated your virus software and did a comprehensive system scan? Defragment all the hard drives? Fragmentation will drive Audacity--or any real-life software nuts.

You keep leaning on 1.3.x as the Devil's Spawn. It might be. It's listed as unstable beta software. Have you tried 1.2.x? I've captured many long live performances with 1.2.x and it's worked just fine.

You didn't use the evil term "USB" in any of your posts. Is that an oversight? Audacity doesn't much like USB audio equipment.

Koz

kozikowski wrote:
You didn't use the evil term "USB" in any of your posts. Is that an oversight? Audacity doesn't much like USB audio equipment.

Koz

USB kit often works fine with Audacity - a lot of the problems are down to poor USB connectors. I used to run an ION TT through USB worked fine (but too much wow & flutter) - and now use a USB soundcard. Both of them had no problems with Audacity (on PC Windows XP-HE-SP2).

For people with laptops with a mic-in only and no line-in - then an external USB soundcard can be a good solution.

WC