Help for Audacity on Windows.
Forum rules
This forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at
https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the
1.2.x and
1.3.x forums.
-
steve
- Site Admin
- Posts: 80752
- Joined: Sat Dec 01, 2007 11:43 am
- Operating System: Linux *buntu
Post
by steve » Thu May 08, 2014 3:26 pm
Ok, so we can see that the alpha version is stalling after setting:
Code: Select all
TempDir=C:\DOCUME~1\utente\IMPOST~1\Temp\audacity_temp
and before setting:
One of the differences between the stable version and the alpha version is that the latter has experimental support for WASAPI and WDM-KS enabled. These can provide better sound card performance and more flexibility than the older WDM / Direct Sound options, but unfortunately the drivers for some sound cards are buggy with these technologies. Due to these stability problems only the "loopback" option for WASAPI is enabled in the release version and WDM-KS is disabled altogether.
Sometime updating the sound card drivers can solve these problems and allow the alpha version to run.
There is some information here about checking and updating drivers:
http://wiki.audacityteam.org/wiki/Updat ... ce_Drivers
-
DjDiabolik
- Posts: 30
- Joined: Wed Apr 30, 2014 3:27 pm
- Operating System: Please select
Post
by DjDiabolik » Sat Jun 07, 2014 11:58 am
i never tryed to lauch beta whit my BCD3000 Shutted down....... otherwise yes..... i have this driver installed.....
*EDIT*
Can post........ i have shutted down my BCD3000........ reset the preferences file.... and try to start the last beta (now the 04-jun-14). Same things..... on XP this never started........
*EDIT 2*
I have also try to reset my .cfg........ same things...... this is the .cfg after a fail start:
Code: Select all
NewPrefsInitialized=1
Version=2.0.6-alpha-Jun 4 2014
PrefsVersion=1.1.1r1
[Version]
Major=2
Minor=0
Micro=6
[Directories]
TempDir=C:\DOCUME~1\utente\IMPOST~1\Temp\audacity_temp
-
Gale Andrews
- Quality Assurance
- Posts: 41761
- Joined: Fri Jul 27, 2007 12:02 am
- Operating System: Windows 10
Post
by Gale Andrews » Sun Jun 08, 2014 1:35 am
DjDiabolik wrote:i have shutted down my BCD3000........ reset the preferences file.... and try to start the last beta (now the 04-jun-14). Same things..... on XP this never started........
I have also try to reset my .cfg........ same things...... this is the .cfg after a fail start:
Code: Select all
NewPrefsInitialized=1
Version=2.0.6-alpha-Jun 4 2014
PrefsVersion=1.1.1r1
[Version]
Major=2
Minor=0
Micro=6
[Directories]
TempDir=C:\DOCUME~1\utente\IMPOST~1\Temp\audacity_temp
Then as Steve suggested, the WDM-KS support in the alpha build is probably upsetting the SoundMax built in audio.
You could investigate if you have the correct drivers for SoundMax:
http://wiki.audacityteam.org/wiki/Updat ... ce_Drivers . The drivers should be supplied by the motherboard or computer manufacturer.
After ensuring you have the correct drivers, click the Windows Start button then type:
in "Run" and hit ENTER. Save and attach the report. Please see here for how to attach files:
http://forum.audacityteam.org/viewtopic ... 49&t=64936 .
Other than that you could use 2.0.5, or uninstall SoundMax in Windows Device Manager and use the BCD 3000 as your audio device, or build the 2.0.6-alpha without WDM-KS support.
Gale
-
DjDiabolik
- Posts: 30
- Joined: Wed Apr 30, 2014 3:27 pm
- Operating System: Please select
Post
by DjDiabolik » Thu Jun 26, 2014 10:29 pm
I don't really need to use the beta 2.0.6 for moment and it's useless i try to compile it

the 2.0.5 have all i need to do.........
Othewise i already check....... i have all driver updated........ there's no exist more recent driver i have already installed....... i also can upload the report of "dxdiag" in this same reply if you thinks it's usefull for obtain a final 2.0.6 version i can use correctly.
Gale Andrews wrote:DjDiabolik wrote:i have shutted down my BCD3000........ reset the preferences file.... and try to start the last beta (now the 04-jun-14). Same things..... on XP this never started........
I have also try to reset my .cfg........ same things...... this is the .cfg after a fail start:
Code: Select all
NewPrefsInitialized=1
Version=2.0.6-alpha-Jun 4 2014
PrefsVersion=1.1.1r1
[Version]
Major=2
Minor=0
Micro=6
[Directories]
TempDir=C:\DOCUME~1\utente\IMPOST~1\Temp\audacity_temp
Then as Steve suggested, the WDM-KS support in the alpha build is probably upsetting the SoundMax built in audio.
You could investigate if you have the correct drivers for SoundMax:
http://wiki.audacityteam.org/wiki/Updat ... ce_Drivers . The drivers should be supplied by the motherboard or computer manufacturer.
After ensuring you have the correct drivers, click the Windows Start button then type:
in "Run" and hit ENTER. Save and attach the report. Please see here for how to attach files:
http://forum.audacityteam.org/viewtopic ... 49&t=64936 .
Other than that you could use 2.0.5, or uninstall SoundMax in Windows Device Manager and use the BCD 3000 as your audio device, or build the 2.0.6-alpha without WDM-KS support.
Gale
-
Attachments
-
- DxDiag.txt
- (45.51 KiB) Downloaded 25 times
-
Gale Andrews
- Quality Assurance
- Posts: 41761
- Joined: Fri Jul 27, 2007 12:02 am
- Operating System: Windows 10
Post
by Gale Andrews » Fri Jun 27, 2014 9:06 am
Thanks for the dxdiag report. It appears to show that the Driver Provider for the SoundMax device is "Analog Devices", so it's not merely a generic Microsoft driver. Do you have a branded computer like Dell or HP or did you build the computer yourself? Where did you get the driver from?
We're not currently planning to enable WDM-KS for 2.0.6 release - if we did enable it, it would have to be optional with a way for the user to enable or disable it.
WDM-KS is enabled in alpha builds for diagnostic purposes.
If you have the most appropriate drivers for the SoundMax I could probably give you a special build of Audacity that would write a log file of what happens when Audacity's PortAudio interface queries the SoundMax device. It would not solve the problem for you, but might give us some diagnostic information on how we could avoid the freeze on launch, or how we could at least make Audacity ignore SoundMax if it's not compatible with WDM-KS. We can't make devices WDM-KS compatible if they are not.
Please let me know if you want to try that. Thanks for your help.
@Steve if you are reading this, were you in a similar position with some sound device on an XP computer?
Gale
-
steve
- Site Admin
- Posts: 80752
- Joined: Sat Dec 01, 2007 11:43 am
- Operating System: Linux *buntu
Post
by steve » Fri Jun 27, 2014 10:06 am
Gale Andrews wrote:@Steve if you are reading this, were you in a similar position with some sound device on an XP computer?
I had a similar problem on Windows Vista. "Audacity 2.0.5" (release version) worked perfectly but "Audacity 2.0.6 alpha" crashed before it started. The problem was resolved by updating the sound card drivers (downloaded from the PC manufacturer's website).