Audacity Forum

Testing v1.3.9.

This issue doesn't happen all the time. I did see a P4 listed that may be related but it refers to this happening on a stressed system and I don't believe that is the case here. (I am running Vista x64, 8GB RAM, 3.0GHz duo-core, nVidia 9800 GT.)

When it happens, after clicking the zoom-out button, there will be a delay of from a few seconds to several 10s of seconds -- even to the application becoming non-responsive -- but it eventually comes back. This behavior will happen for a few minutes (occurring with subsequent clicks of the zoom-in button) and then it will stop. I can then zoom-in/out with no delay at all.

I've not noticed any particular pattern. I've seen this right after initially importing a WAV and rending the waveform. I've seen it after letting the application sit idle for several minutes. No apparent sequence that leads to this. Watching process status, there is nothing indicating any kind of load on the system itself.

How many tracks and what length is the recording?

Two tracks, each about 20 minutes long (two sides of an audio cassette). I've not seen this every time, but I have seen it on more than one project.

Have you tried pulling up the Task manager to see what's running and if anything is using an undue amount of resources?
Is there noticeable disk activity while this is happening?

stevethefiddle wrote:Have you tried pulling up the Task manager to see what's running and if anything is using an undue amount of resources?
Is there noticeable disk activity while this is happening?

From my original post:

RodBarnes wrote:Watching process status, there is nothing indicating any kind of load on the system itself.

I brought up Process Explorer and looked to see if anything else significant was occurring but didn't see anything. But I will make it part of my testing to check disk and CPU activity when this next occurs. It seems to be happening less frequently -- probably because I am becoming more familiar with this version and/or I've altered my methods. But it did occur again just last night.