Re: [Audacity-devel] 2hr Recording Bug fix now in CVS

[James C. <cr...@in...>]

> Before making the above suggested changes, with yesterday afternoon's HEAD
build, I tried a recording at 44100 stereo.  Well, this time it was still
running ok after about 2:45 hours.  [During this time, all other apps were
closed, and I did not even try any user interaction with W2K at all.] So I
did not even try to make the change.
>
> I saved this project, but it took close to an hour for the save to
complete!! [300 Mhz processor, but a very fast disk, with 8MB cache].  I can
zip (using InfoZip) a 4 GB (that is twice the data size) partition in much
less time than that :)
>
> I can only speculate how the data might be maintained currently in the
temporary area, and how it is in the final project area.  If the individual
files/segments have not been edited prior to a save, I would imagine we can
speed up this save by orders of magnitude, with renaming of the files into
the save area (assuming the temp area and final save area are on the same
partition).  Any comments?
>
> Cordially, Chacko

Wow, that's way too much time to save.

If you're interested in tracking down what's taking all that time,
a rough and ready way to profile is just to interrupt the program,
notice what routine it is in, resume where you left off, and
repeat a few times.

You might also try reducing the block size (in sequence.cpp I
think) and see if it is related to the number of blocks rather
than the total quantity of data.  If you reduce the block size
by a factor of 60 you might get a similar problem at 3 mins
recording, which would be more managable to track down.

Thanks for reporting this.

--James.