Audacity is unresponsive
Posted: Wed Jan 09, 2008 9:56 am
I am running Audacity 1.2.6 on OSX 10.4.11 on a G4 with a 400 mhz processor with 448 mb ram, with an external USB(1) Edirol UA5 soundcard, which I think falls within the requirements http://audacityteam.org/download/mac.
However I find Audacity to be frustratingly slow and often unresponsive when I ask it to do something; a typical example is that I press play, and it plays; I press stop and it stops; but then I can't get it to play again, or select some audio to work on. Even if I do manage the latter, many of the menus are just grayed out - eg save, delete, effects - even the 'about' menu. Eventually I close the window in frustration, and, fortunately, it asks if I want to save before quitting. I have to re-open the file to do make the next move, or quit and re-launch. At the moment I'm trying to work on a pretty simple file, with two stereo tracks with imported music and a mono track for a voiceover.
I'm just wondering if I'm maybe doing something wrong, have it somehow set up wrong, or if my machine isn't up to the job. I don't have these kinds of problems with Bias Peak LE - although I think that's limited to one stereo track in my version so maybe uses less processing power?.
Cheers for any pointers: I hope I've described the problem sufficiently.
However I find Audacity to be frustratingly slow and often unresponsive when I ask it to do something; a typical example is that I press play, and it plays; I press stop and it stops; but then I can't get it to play again, or select some audio to work on. Even if I do manage the latter, many of the menus are just grayed out - eg save, delete, effects - even the 'about' menu. Eventually I close the window in frustration, and, fortunately, it asks if I want to save before quitting. I have to re-open the file to do make the next move, or quit and re-launch. At the moment I'm trying to work on a pretty simple file, with two stereo tracks with imported music and a mono track for a voiceover.
I'm just wondering if I'm maybe doing something wrong, have it somehow set up wrong, or if my machine isn't up to the job. I don't have these kinds of problems with Bias Peak LE - although I think that's limited to one stereo track in my version so maybe uses less processing power?.
Cheers for any pointers: I hope I've described the problem sufficiently.