Page 1 of 1
Program Runs Slow or Crashes After Using "Find Clipping"
Posted: Fri Dec 14, 2007 1:37 am
by upperdecker
I was fine for a few days until I tried using the Find Clipping option. Ever since then, the program is unresponsive, often requiring a control-alt-delete exit. I am running Windows XP Media Center Edition, and this post refers to Audacity 1.3.4-beta.
I even uninstalled and reinstalled, but the issue persists. What's especially odd is that even after the reinstallation, the program opened with an option to recover the last project. Did I somehow manage not to fully uninstall?
Any help appreciated. This is driving my OCD self nutty.
Tom
Re: Program Runs Slow or Crashes After Using "Find Clipping"
Posted: Fri Dec 14, 2007 10:13 am
by waxcylinder
You will not have un-installed properly, as there is no un-install option provided with Audacity (a seriuos ommission in my view).
What you probably did was to remove the Audacity exe files - what you probably didn't remove was your Audacity Preferences folder. In 1.3 whenever you change any of the Preferences a preferences file. Audacity.cfg is maintained for each Audacity user (in 1.2.x this was done in the registry).
You should find the file in C:Documents and Folders<your_user_name>Application DataAudacityAudacity.cfg
Try deleting this file and then re-installing Audacity - or perhaps even try deleting the file and just restarting Audacity.
WC
Re: Program Runs Slow or Crashes After Using "Find Clipping"
Posted: Fri Dec 14, 2007 11:41 am
by upperdecker
I think you gave me the fix I needed. Thanks so so much, WC. That was really giving me a fit.
Tom
Re: Program Runs Slow or Crashes After Using "Find Clipping"
Posted: Mon Dec 17, 2007 7:35 am
by Gale Andrews
[quote="waxcylinder"]You will not have un-installed properly, as there is no un-install option provided with Audacity (a seriuos ommission in my view). </quote>
What's wrong with Control Panel > Add/ Remove programs, or unins000.exe in the Audacity Program Files folder?
Re: Program Runs Slow or Crashes After Using "Find Clipping"
Posted: Mon Dec 17, 2007 11:12 am
by waxcylinder
galeandrews wrote:waxcylinder wrote:You will not have un-installed properly, as there is no un-install option provided with Audacity (a seriuos ommission in my view). </quote>
What's wrong with Control Panel > Add/ Remove programs, or unins000.exe in the Audacity Program Files folder?
Funnily enough Gale, that's exactly what my wife said about this when I discussed this later. Doh!
Question though - does Control Panel/Remove Prorams - remove the .cfg file with 1.3 and the registry entries with 1.2 to remove the Preferences settings?
WC
Re: Program Runs Slow or Crashes After Using "Find Clipping"
Posted: Wed Dec 19, 2007 10:40 pm
by yeti_07
upperdecker wrote:I think you gave me the fix I needed. Thanks so so much, WC. That was really giving me a fit.
The fix we all would desperately need would be the one, that fixes this annoying bug in audacity. I stumbled upon this myself a few ours ago. Restarted audacity, logged off and on again, even restarted windows. Nada. My cure has been to reinstall 1.3.3 (without a deinstall of 1.3.4).
What
is it that causes audacity to positively and permanently choke when using this function?
Y.
Re: Program Runs Slow or Crashes After Using "Find Clipping"
Posted: Sat Dec 22, 2007 7:59 am
by Gale Andrews
Hi WC- Uninstalling (by any method) does not remove the Windows registry settings (1.2.x) or the .cfg file (1.3.x). Those need deleting manually.
We'll make a note to look out for problems after running "find clipping" when we do further testing. I was using it a lot recently though without problems, though it was only a four minute track. Are we talking about very long tracks? You can also try View > Show clipping instead of Find Clipping. Show Clipping will show clipping in red, then you can zoom in to see how many samples are clipped.
Thanks
Re: Program Runs Slow or Crashes After Using "Find Clipping"
Posted: Sun Feb 17, 2008 11:17 pm
by Chuck17
I've experience the same thing - progam runs slowly after I use clipping. Whacking the cfg file fixed the problem. FYI, I'm running WinXP SP2. Thanks for the help!
-Chuck