For questions, answers and opinions
https://forum.audacityteam.org/
Please inform us what Service Pack you are running.Oatmeal wrote:Sorry to resurrect an old thread but I wanted to remind the developers that this bug still exists in the latest beta build (1.3.9)
This has (we believe) been fixed since my last post about it in this thread, and the fix will be in the next Beta 1.3.10. See "Fixed since release" on our Known Issues page. The fix was tested on Vista and Windows 7, but if you want to test it before 1.3.10 Beta is released, please download 1.3.10 Alpha from the "nightly development builds" link on that page.efraim wrote:I ran into this problem with 1.3.9 on windows 7 professional 64 bit build 7600 when I was trying to import the sound from a video file and had to add ffmpeg. It crashed both when trying to open the preferences from the menu and with ctrl-p. I tried uninstalling and reinstalling, deleting the preference file in the appdata folder, running as compatibiliy mode as vista and xp, running as admin.
When I plugged in a microphone it stopped crashing.
Even if this is microsofts fault by saying "jump" I think audacity is to blame for the crash since it doesn't seem to have proper error handling.
I did not know such a page existed, I just downloaded the latest version (1.3.9) and ran into this problem and wanted to report it. I should have looked a bit further before posting about it. I just downloaded the alpha and it does indeed work, it says no devices found when looking at recording devices. Keep up the good work!Gale Andrews wrote:This has (we believe) been fixed since my last post about it in this thread, and the fix will be in the next Beta 1.3.10. See "Fixed since release" on our Known Issues page. The fix was tested on Vista and Windows 7, but if you want to test it before 1.3.10 Beta is released, please download 1.3.10 Alpha from the "nightly development builds" link on that page.
Gale
No problem. The "Known Issues" online pages are mentioned in README.txt that comes with the program, and on the New Features in Beta page. The most direct way to report a bug is to our feedback e-mail address.efraim wrote:I did not know such a page existed, I just downloaded the latest version (1.3.9) and ran into this problem and wanted to report it. I should have looked a bit further before posting about it.Gale Andrews wrote:This has (we believe) been fixed since my last post about it in this thread, and the fix will be in the next Beta 1.3.10. See "Fixed since release" on our Known Issues page. The fix was tested on Vista and Windows 7, but if you want to test it before 1.3.10 Beta is released, please download 1.3.10 Alpha from the "nightly development builds" link on that page.
Gale
Thanks for checking that.efraim wrote: I just downloaded the alpha and it does indeed work, it says no devices found when looking at recording devices.
I found through trial and error that in Windows 7 x86 I hyad to plugin a mic in order to keep Audacity v1.3.9 Unicode from crashing whenever I went to access the preferences menu, thanks for the tip, I just wanted to let people know that this also applies to Windows 7.Finally went back to the office after the holidays. Yes! Thanks for posting the link that helped me figure it out. Vista seems to report at the driver level that there is no recording device when there is no mic plugged in on my computer. There must be some bad error handling code in Audacity that causes the whole program to crash when the preferences are accessed in this case. I plugged in a mic and preferences showed up fine allowing me to install ffmpeg support.