| From James Crook <crookj@...>
| Sun, 30 Dec 2007 13:25:53 +0000
| Subject: [Audacity-devel] Toolbars unresponsive...
> Gale Andrews wrote:
> > At the moment my "toolbar buttons unresponsive" issue I posted on
> > Watching Brief which I had ever since I was using that 26 December
> > build has disappeared with last reboot (though the reboot before did not
> > help). It was so bad at one point that after clicking even (say) Mute,
> > I'd have to task switch away and back before I could click another Mute
> > button. I'll keep a closer eye if memory (system or Audacity) has
> > anything to do with it if it starts happening again, unless someone has
> > any ideas. The build before last I was using (early December) has no
> > such problem.
> Early December build was wxWidgets 2.6.1
> 26 December build was wxWidgets 2.6.4
> Malware? Dodgy RAM? (but for those I'd expect occasional complete lock-up)
If someone had written to -help list stating those symptoms I am sure I
would have suggested the same. But no, this computer is kept clean and
only a month old, 1GB of RAM and properly set up. As it was when I first
started working with your 26 Dec build, open one project and toolbar
buttons were unusable. After a while, task switching was necessary after
most actions to do another. Certainly no unusual CPU use - that is
monitored all the time. Close that build, open the same project in early
December build and everything worked for hours on end.
> Is it a USB mouse and do you have a USB microphone on the machine?
Do you have a specific reason for asking? At the time, I was using a USB
keyboard. USB external drive connected but not running. No other USB
While here, I am wondering about Show Clipping. I had a project with one
20 minute track and a few brief clips dotted around underneath. If I
turn Show Clipping on, any Audacity build that includes it is unusable
after that, displaying the busy cursor (even after 30 minutes) and has
to be force quitted. If Show Clipping is already on when the Project is
opened, Project opens but as soon as you take any action with the menus,
Audacity becomes unresponsive. Same result on my other PC. Find Clipping
does work OK (takes about three minutes). Trying other (essentially
single track) projects, it looks as if a 15 minute track is the limit
for Show Clipping at 44100 Hz. Does anyone else find this? Should there
be a progress dialogue if you turn Show Clipping on and Audacity sees
this will take more than a few seconds?