[ardour-dev] deep design question: help requested (rapidly)
antoine.rivoire at ntlworld.com
Tue May 18 12:43:38 PDT 2004
Sorry for intruding,
I might have the wrong concepts here but allow me to try and explain
what I would find intuitive and usable.
In the region window, having a reference to the original region(A),
always, so that I can pull that back on the track very quickly. Maybe
having this in bold.
When this region is edited, it creates and new one (A-0).
New edit of A -> A-1
New edit of A-0 -> A-01
with some indentation, this might make a nifty tree where I can keep
track of what did quite a few edits ago without having to scroll through
a undo history window.
Another handy tool might be a "clean up unused region".
Sorry again if I miss the point here.
On Tue, 2004-05-18 at 14:03, Paul Davis wrote:
> One of the premises of Ardour, inherited from studying other DAWs such
> as ProTools, Nuendo and Samplitude, is that the UI should offer the
> user a list of all regions, possibly filtering/hiding parts of it in
> various ways if the user asks for that.
> Assuming that this premise is true (and it seems like a good one),
> lets suppose that we have a region, we'll call it region A. we modify
> region A, perhaps by trimming it or some other operation. we end up
> with a modified version. there are two choices with how we can
> implement this:
> 1) it could be the same region, but with modified data. call that
> region A'
> 2) it could be a new region, similar to A but different in whatever
> way was involved in the edit. call that region B.
> put more abstractly, is it possible to edit a region, or is it only
> possible to create a new region based on the old one?
> at the moment, ardour is using strategy (1), which leads to a
> problem. after the edit, what does the session list contain:
> [ region A ] OR
> [ region A'] OR
> [ region A, region A' ]
> ardour used to use strategy (2), but the way we implemented it led to
> many nasty issues.
> comments are urgently sought ..
> ardour-dev mailing list
> ardour-dev at lists.ardour.org
antoine rivoire <antoine.rivoire at ntlworld.com>
More information about the Ardour-Dev