Project instability in 1.3

[Gale Andrews]

Audacity 1.3.12 is in my opinion definitely the way to go.

For me 1.3.12 remains liable to crashes on Windows (both XP and 7) if doing repetitive editing over long periods of time (think 100+ edits or so). That's really the only advantage for me that 1.2.6 has and possibly that intensity of editing is not a typical workflow. I normally use 1.3.12 to record, maybe to move some bits around and then export WAVs and edit them in earnest in 1.2.6.





Gale

[steve]

For me 1.3.12 remains liable to crashes on Windows (both XP and 7) if doing repetitive editing over long periods of time (think 100+ edits or so).

I use Audacity extensively at work on Windows XP SP3. Most projects are less than 5 minutes duration, but may contain up to 20 tracks and hundreds of edits. If I keep Audacity open all day, then there is a fair chance that it will crash by mid afternoon, but I usually close Audacity completely after each project and it is extremely rare that Audacity 1.3.12 crashes.

I also use Audacity 1.3.9 as I have Nyquist WorkBench installed in 1.3.9 (I'm not able to build from source-code on the works machines, but Leland kindly sent me a pre-compiled copy of Nyquist WorkBench for Audacity 1.3.9). Unfortunately crashes are not uncommon on that version, but Audacity 1.3.12 is really solid and dependable for me.

[Gale Andrews]

Yes, 1.3.12 is significantly less liable to crash for me too than a few Betas before, it has improved. I rarely have more than four tracks but will often peg away at edits at the same spot in one track and this seems to be the crux of my problem, either in that spot or immediately when I move to another one. I have never been able to faze 1.2.6 in that way.


Gale

[waxcylinder]

For me 1.3.12 is the best ever Audacity - it hasn't crashed on me yet- the only problem I get is the Timer Record overrun (seemingly fixed by Nikolay's patch for Alpha 1.3.13 - he says touching wood frantically).

Like Steve, I keep Audacity open all day for LP transcriptions. I never save a project, but instead record a side eport it for ClickRepair processing and then import it bnack into Audacity for intertrack cleaning and amplification to "normalize". Export the tracks and then delete the audio and the label track and start again with the next side. So a fair number of edits in a day - but so far no crashes.

Platform: Windows XP-HE-SP3

WC

[Gale Andrews]

I don't have to save projects, just work in a repetitive way on the temporary data in the same small spots over an hour or so. Not everyone who works like that will get the problem, but I know several people who are still troubled by this even in 1.3.12.

Unless I can't finish in a session I wouldn't save a 1.3.12 project because I tend to get that "orphaned blockfiles" problem when I re-open them... without it ever being repeatable enough to figure out what caused it.



Gale