When I run Audacity the welcome window is partially drawn and the program goes no farther. CPU goes all the way to 98 or 99 percent. Program hangs.
I had 1.3.x installed and I installed 2.0.2 over it, thinking that Audacity would take care of itself. When I had this problem I learned that I should have uninstalled 1.3.x first.
Since then I’ve uninstalled/reinstalled several times. I’ve tried removing all mention of audacity in the registry, wiping out the Application Settings folder, modifying the cfg to this:
I don’t understand how you have that .cfg file as you say:
" I’ve tried removing all mention of audacity in the registry, wiping out the Application Settings folder, modifying the cfg to this:…"
"When I run Audacity the welcome window is partially drawn and the program goes no farther. "
The audacity.cfg file is written when Audacity closes, but if Audacity is not opening, then it can’t have closed, so where has that copy of the audacity.cfg file come from?
When I run audacity.exe, it opens the “Audacity” window (all gray), and on top of that the “Welcome to Audacity!” window (mostly gray, with a white bar on top, as if partially drawn). If I have the cfg file open in my text editor, it will tell me at this point that the file has been updated. When I refresh the text editor it shows me the new settings. It’s as if the program is going through a list of steps, updating the cfg as it goes; but it only goes so far.
Thanks, that makes sense - it’s getting a little further than I thought it was.
It may be worth trying it with your “normal” (hardware) sound card rather than with TotalRecorder.
Go into the Windows Sound Control Panel and set the default playback device and the default recording device to a real (hardware) device (for example - speakers for playback, microphone for recording - if this is a full size computer you may need to plug in a microphone to make the mic input available).
Reboot your computer and check that the settings are as you set them.
Then change the audacity.cfg file back to:
Looks like it’s fixed.
I followed your instructions, updating my windows audio properties to use my sound card (Realtek AC97 Audio) for both recording and playback, and resetting the cfg file. After reboot, I ran Audacity and got the same partially-drawn windows and pegged CPU. Following your logic, I manually updated the cfg to set RecordingDevice to Realtek AC97 Audio. This allowed Audacity to start up normally.
Thanks so very much for your help. Amazing response time and accurate advice.
Thanks for replying. I am not sure why Audacity tried to use Total Recorder after resetting audacity.cfg, unless Audacity was still open (in which case it will overwrite the .cfg file when you quit Audacity), or unless Total Recorder actually still was the Windows default device (merely selecting the device doesn’t make it default on Windows Vista, 7 or 8).
Note that following the improvements to Device Toolbar in 1.3.13, Audacity now initializes after resetting audacity.cfg to the explicitly named default playback and recording devices in Windows, rather than to the “Microsoft Sound Mapper” devices which are mapped virtual devices that point to whatever the current Windows defaults are. I’m not sure this change was intended; some people have complained about it, though the playback / recording devices Audacity initialises to should still be the same.
Since 2.0.2, Audacity write details to .cfg on launch and when most settings are changed, not only when it exits.