Anyway to shock Audacity into responding.
Posted: Tue Jun 03, 2008 12:25 pm
I recorded a massive 8 track jam session last night. One huge Audacity project.
This morning, I started to fool around with it, realized I hadn't saved it yet, and did a Save As to my 2nd local hard-drive (Audacity's temp directory is on 1st local hard-drive)
I expected it to take some time, as there are over 13,000 raw audio files.
As usual, Audacity went into its "Non Responding" mode while doing all this, but it's never come out of it.
It only copied around 1000 of the raw audio file to it's new location, there's no "aup" file.
Looking at Task Manaager, there are two tasks, both with the new project-file-name, one with the Audacity Icon, the other with a default file icon, both non-responding. They both link back the the Audacity Process, which is just sitting there using no CPU time.
Is there a command line way or something to shock Audacity out of it's never-never land?
If not... what's the easiest way to recover my lost project? (8 tracks, 2+ hours each)
This morning, I started to fool around with it, realized I hadn't saved it yet, and did a Save As to my 2nd local hard-drive (Audacity's temp directory is on 1st local hard-drive)
I expected it to take some time, as there are over 13,000 raw audio files.
As usual, Audacity went into its "Non Responding" mode while doing all this, but it's never come out of it.
It only copied around 1000 of the raw audio file to it's new location, there's no "aup" file.
Looking at Task Manaager, there are two tasks, both with the new project-file-name, one with the Audacity Icon, the other with a default file icon, both non-responding. They both link back the the Audacity Process, which is just sitting there using no CPU time.
Is there a command line way or something to shock Audacity out of it's never-never land?
If not... what's the easiest way to recover my lost project? (8 tracks, 2+ hours each)
