Re: [Audacity-devel] Slow update of selection posn on big projects
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Richard A. <ri...@au...> - 2013-11-14 10:08:28
|
On Tue, 12 Nov 2013 21:00:12 -0800 (PST) Norm C <n_b...@ho...> wrote: > When working with large projects (eg. my latest is 15 tracks, each an > hour long) it can take several seconds on a moderately fast PC to > simply update the selection cursor position when you click in a > track. This feels exceedingly sluggish. The majority of that time is > spent rewriting the autosave file, which in my case is over 2 MB long > and involves thousands of mallocs, one per string. I noticed a > comment in TrackPanel about how MakeParentModifyState in this case > "doesn't warrant autosave, maybe implement bWantsAutoSave". Makes > sense to me, and doing that results in the updates happening very > quickly. > > Seems to me that the downside of losing the selection position in the > event of a crash is pretty minimal, and the time saving is pretty > substantial. But there may be differences of opinion. Should this be > opened as a bug report, or an enhancement, or should I go ahead and > submit the patch? I can't see any down side as described, so I'd like to see the patch. I've certainly seen the symptoms when using Audacity on low power platforms (raspberry pi) or with large projects (16 hours long on an AMD C60 netbook), so if we can fix it safely I'm all for it. I also wonder if we could make the autosave process quicker by avoiding memory (re)allocation if that is the constraint, but the trade off for this specific case is certainly worth looking at. Richard |