On Sunday 22 November 2009 17:52:39 Martyn Shaw wrote:
> OK, so a bit more testing here, following my own instructions
> (below) confirms (?) that this can cause a crash on the 10th Nov
> build. In case you want to test, an uncompressed unicode-release
> Audacity.exe 10th Nov is here
> http://dl.dropbox.com/u/1327769/Audacity.exe, which you could drop
> into a current unicode-release tree and try.
> All the good work of Al on zero-length clips etc seem to have fixed
> this and I can't get the problem on the HEAD version.
> I suggest that this is now fixed, although can't be 100% certain
> that the bug I was chasing was the one that I found, and the
> one(s?) that Al fixed. But life is too short to get certainty on
> this one, for me at least. Let's get a release and some more user
I'm definitely going to look at this project when I have a chance, back
up my CVS to Nov. 10 and see if I can get it to crash in some way, get
a backtrace, etc... I'm always curious to see where exactly different
crashes are coming from. I've just been looking at some other things.
> Martyn Shaw wrote:
> > Ok so what I'm doing seeing / doing here is this (using the 10th
> > Nov 09 code, since Gale reported the bug occurs on 11th Nov build
> > and the project I posted), but still don't have an exactly
> > repeatable scenario. I can get an exponentially increasing size
> > of the project file sometimes (say 1 in 4) when there are
> > waveclips of size zero, and a linearly increasing size of the
> > file when there are clips of size one.
> > Zoom to about 5:28.30 to 5:30.10 (if you need to).
> > 1 Select something about 5:28.70 to 5:28.90 and do Noise
> > Removal.. -> Get Profile.
> > 2 Select the bit with the last 2 splits in it (the solid one and
> > the feint one), say 5:29.862 to 5:29.987 and Effect-> Noise
> > Removal ->OK. This gives me 4 solid split line in the region
> > selected (I don't know why this step is needed but it seems to be
> > important).
> > 3 Select a region covering the first Split point, Ctrl+R a few
> > times.
> > Save the project and open it in a text editor. You may have a
> > whole load of waveclips of size zero or a few of size 1. It
> > seems to vary with what you selected in steps 2 and 3.
> > If you have a number of waveclips of size zero then Ctrl-R more
> > times eventually results in a hang since you get 1, 3, 7, 15 etc
> > of them until you reach some limit.
> > Why am I doing this? I would rather that P2 be cleared by a 'we
> > understand and have fixed it' route, rather than a 'there aren't
> > any more reports of it' route. But I could put up with the
> > second.
> > TTFN
> > Martyn
> > Martyn Shaw wrote:
> >> Hi there
> >> Still looking into the
> >> P2 Projects crash when applying repeated effects on zoomed in
> >> regions towards the end of audio tracks
> >> I think this may be related to the
> >> P2 Boundary drawing problem with Generate and SoundTouch
> >> ..."faint or no clip line"
> >> and quite possibly
> >> P3 R Unreliable project re-opening with orphaned and missing
> >> blockfile errors.
> >> These 'may' be fixed in HEAD, but until we know exactly what is
> >> causing them, we don't really know. That's why I've been
> >> working with 10th Nov code (since Gale said that reports of the
> >> 'P2 Projects crash when applying repeated effects...' had come
> >> in from 11th Nov build).
> >> Here is a project with the faint split lines, that is on the
> >> verge of failing (I think).
> >> http://dl.dropbox.com/u/1327769/Case.7z for a 37M 7zip example
> >> (http://www.7-zip.org/).
> >> If you can't get that let me know and I'll provide an
> >> alternative route.
> >> I generated this project (eventually) by something like
> >> Generate a chirp of 330s
> >> Select about 0.5s near the end
> >> Noise Removal -> Get Noise Profile
> >> Select another approx 0.5 bit
> >> Noise Removal->OK
> >> Select another 0.5s bit
> >> Ctrl-I (Split)
> >> Select a bit covering the second split
> >> Ctrl-R (repeat Noise Removal)
> >> although this probably isn't particularly repeatable.
> >> Please try this project, doing some operations on the last
> >> (less-than) 0.5 seconds. See if it fails for you. And/or look
> >> at the aup file in a text editor and see if you can see the
> >> errors.
> >> Thanks
> >> Martyn
> ----------- Let Crystal Reports handle the reporting - Free Crystal
> Reports 2008 30-Day trial. Simplify your report design,
> integration and deployment - and focus on what you do best, core
> application coding. Discover what's new with Crystal Reports now.
> audacity-devel mailing list