Re: [Audacity-devel] Possible fix for 'Chains applied to files do not clear temporary files after p
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: Dan H. <da...@go...> - 2009-07-07 02:17:39
|
On Mon, Jul 06, 2009 at 04:48:52PM -0400, Alec Burgess wrote: > > Dan Horgan (da...@go...) wrote (in part) (on 2009-07-06 at > 09:51): >> [snip] >> I've committed a change to do this so we can see what it's like - >> it shouldn't be hard to change back if we decide against it. >> >> I think I prefer it this way, although I haven't needed to use batch >> chains much for actual work so it's difficult to judge. If it is >> reasonable to think of a chain as a fixed sequence of effects that the >> user builds once and then uses several times, I think being able to >> undo >> it in one step is logical as the user probably wouldn't want to be >> concerned with the individual items in the chain at the time when they >> apply it. But I don't know whether that's how it is actually used (or >> even whether that's how it's intended to be used). >> One thing which doesn't really agree with this way of thinking about >> it >> is the possibility of having 'export' commands in the chain - which >> can't really be undone. >> But one the whole I think I'm still in favour of undo in one go, >> since I >> suspect in the majority of cases it makes more sense and it does save >> disk space. > > When developing and testing the chain, would it be useful for user > (optionally before running the chain) to request that separate steps be > "undoable" so he can walk back through the chain to find problem(s), > tweak individual step(s) and then rerun the chain? > Perhaps... should it be a preference in that case? I'm not sure how different this would be to just applying the effects one by one to work out what the chain should be before actually creating it. Ideally there'd probably be some kind of separate mode for developing a chain, which would allow this and other features like a preview for the whole chain. |