Audacity Forum

25 minutes later and the audio is still not selected - WTM shows Audacity status as Running - and the windows task button in the task bar does not say "Not Responding" ...

UPDATE: 1hour 15 mins after initial selection and the audio is still not selected - test abandoned.

WC

Here is another symptom which I got on XP which is suggestive of excessive page faults. After a long Audacity process has finally completed, you terminate Audacity, yet other programs still seem to be extremely slow for a while but gradually speed up to normal. This again happens mostly when the total "commit" value approaches or exceeds the amount of actual main memory you have on your machine. Remember that there are lots of other processes also using memory, so when Audacity starts to crawl, it basically takes over almost all physical memory, and forces all the other processes memory pages to be transferred to the page file on the hard drive. Once Audacity has terminated, they all must get their pages back from the hard drive paging file before they can run full speed.

I have not had a chance to do any performance testing with my WingDoze 7 machine yet -- still wrestling with 7 vs XP and the weird 7 audio setup.

More thoughts on this tomorrow.

Dave

However this week with a differnt project it worked well and reasonably briskly.

Recorded a project without saving the project first, two hours duration and saved it into a new named project - this took about 6 minutes, but I'm used to that.

This morning I fire up Audacity, open up the project go to the send of the first hour, as I only need the first hour. As before the display moved to the last 8 seconds of the project with the label track showing as selected but not the audio - but this time it tikes less than 10 seconds for the audio to be selected, and the subsequent deletion wasn't too slow either.

So is this behaviour down to this being a newly opened instantiation of Audacity and with a freshly opened (but previously saved) project.

I.e. does the aberrent slow behaviour occur if you have had Audacity and the project(s) open and working for a while?

WC

See also this recent posting from user mahobbs: http://forum.audacityteam.org/viewtopic ... 16&t=44994

WC