Hello,
Fedora 12 amd_64 Audacity 1.3.11
After working with audacity sound only, for about 5 hrs or so I saved to file and audacity wrote over it's existing file and saved a blank zero byte file. I hadn't altered the sound track much so that had nothing to do with it.
Now I add a new letter to the file name and save it that way to make sure the file gets saved. It is a work around but it is better than losing everything.
Also just playing different small sections of the sound track it froze up the whole audacity application and I had to use the system monitor to shut it down. Here I did something with the mouse that I didn't normally do. I believe that I started a short section of the sound track in loop mode by holding the shift key down and then hit stop just as it was starting to play. I haven't got had it repeat this though as I don't want to lose any work. The sound track is about 2 1/2 hrs long.
Thank You,
2 hangups
Forum rules
Audacity 1.3.x is now obsolete. Please use the current Audacity 2.x.x package for your distribution or compile Audacity from the source code.
Audacity 1.3.x is now obsolete. Please use the current Audacity 2.x.x package for your distribution or compile Audacity from the source code.
Re: 2 hangups
There's a known issue that rapid play/stop activity (particularly with the transcription speed slider) can cause Audacity to loose its connection to PortAudio and freeze. It's usually triggered (though thankfully not very often) by manic clicking.
I don't know about the blank zero byte file business - there's no issue here. Is this repeatable on your machine? What are the exact steps to reproduce the problem?
I don't know about the blank zero byte file business - there's no issue here. Is this repeatable on your machine? What are the exact steps to reproduce the problem?
9/10 questions are answered in the FREQUENTLY ASKED QUESTIONS (FAQ)