After updating from v2.0.3 to v2.0.4 Audacity.exe runs but there is no UI and after some seconds it idles using 50% CPU on a dual core. However it seems to have partially run because the value of the Version line of Audacity.cfg file has been updated to 2.0.4.
The PC is running XP SP1 and has run Audacity 1.2.6 for years, then has been updated to v2.0.3 using the ZIP package with FFmpeg v0.6.2 for Audacity added. Everything was running fine until I’ve updated to v2.0.4 still using the ZIP package. Language of the UI is English.
What I have tried:
Deleting the %appadata%Audacity folder had no effect. A new one was created, proving Audacity is partially running, but the process still got stuck at 50% CPU with no UI after a while.
Removing the ffmpeg folder had no effect.
Adding the Help folder had no effect.
Removing all DLLs from the Plugins folder had no effect.
Using v2.0.3 plugins and Nyquist had no effect.
In Audacity.cfg setting Enable=0 to [Ladspa] [Nyquist] [VAMP] and [VST] had no effect.
However using an hex editor I can see a reference to Avrt.dll in Audacity.exe v2.0.4, but AFAIK this DLL is only available on Vista or newer Windows versions. So if this file is really required then it breaks the compatibility with Windows 2000 and Windows XP (Download Audacity 2.0.4 for Windows 2000/XP/Vista/Windows 7/Windows 8). Is this file really used ?
Reverting back to v2.0.3 is making everything working again.
Well, if it’s supposed to run on Windows 2000 then it must run on XP SP1, any other Windows 2000 compatible app does run (e.g. WaveShop, Wavosaur, AIMP3, VLC, etc). I’m not going to update, I’ve already tried to do it, because this PC is used for multimedia purposes only and has been tweaked and tuned over years and the update destroys or resets many of these settings, not to mention the removal of some components. Anyway, as I said Audacity 2.0.4 does run, the CFG file got updated but I have to kill the running process because I don’t see any UI at all.
After changing the content of the Audacity.cfg file as you suggested the only dialog I see is about .AUP files association. After that, nothing. The process idles using 50% CPU but the CFG file has been updated like this:
Thanks for your report.
I’ve now seen three reports for this issue (out of 6427 downloads of the Audacity installer for Windows) so there is definitely a problem that is not “just your machine”. This may not be related to SP3 as at least one of the other two cases is using SP3.
Do you ever record with Audacity using “Stereo Mix”?
I know that Audacity should default to MME host, but clearly in a few cases on XP Audacity is not doing the expected thing (that is, it does not complete launching), so I wanted to eliminate the possibility of incorrect host selection when Audacity selects the default.
I’d still like someone with the problem to try this test Audacity 2.0.4 doesn't launch on XP - #7 by steve even if only to eliminate that possibility.
I’ve tested the 2.0.4 installer on Windows XP but not yet been able to reproduce the problem.
I can’t remember to have ever used Audacity for recording, I’m used to use Goldwave for recording and recently I’ve tried WaveShop, if it matters.
In the Devices preferences of Audacity the recording device is set to the Default Sound Capture driver and in the Windows mixer all of the inputs are muted but the CD and Line-In ones. I unmute the stereo mix input only when needed.
It’s already installed and the version number of msvcp90.dll and msvcr90.dll is exactly the same as the ones provided with Audacity 2.0.4.
I got the same feeling reading some other posts on this forum and it’ll be my pleasure to test such version.
FYI on this PC I’m also using foobar2000 with the Kernel Streaming output module set to 24 bits which is working pretty fine. The sound card is an on-board Realtek HD audio with an ALC888 chip.
By all means test, but I suspect the device that is selected is likely to be irrelevant given (as I understand it) Audacity queries all the devices and all the API’s on launch. Audacity won’t start until it’s completed those polls.
Thanks for trying it on XP yourself. If you (Steve) select WDM-KS host, can you play or record?
Devices and hosts are not the same thing of course, but yes, Audacity I believe does a complete poll even if hosts or devices are specified in .cfg before launch. That’s how you get all the non-selected hosts and devices listed in Device Toolbar and Help > Audio Device Info… , otherwise those could not be fully populated.
It would be better if Audacity bypassed devices or hosts that fail the query, but if devices or hosts do fail, Audacity will usually hang or crash.
If no devices or hosts are specified, then as soon as launch completes Audacity will choose
MME host and the Windows default playback and recording devices. That’s a misbehaviour really, as it should set the default to the Microsoft Sound Mapper choices as it used to prior to 1.3.13.
Virtual machines are not a very good test for audio I/O problems. Probably my running XP on Intel hardware that does not officially support XP is not the best test either - though Audacity does launch and list WDM-KS even though WDM-KS errors on playback and recording.
Is this the Vista machine that you have occasional access to?