[ardour-users] [ardour-dev] bug or stupidity ?
dan at wintaper.com
Mon Jul 9 08:14:07 PDT 2007
I understand this philosophy - I'm all for non-destructive.
the problem here is a situation I encountered yesterday. Before I
realized all the looped takes were going into one file, I dropped a
region and accidentally moved the beginning point of the region to what
was really the end of the previous take by a little bit. So now this
"region" spanned 2 takes, and started near the end of one (during silence).
Because I did not immediately realize I had moved the start point, I
ended up with no way to align this track properly other than by ear.
"original position" didn't work for subsequent takes (loops), however
even if it did, how would it place the region that (now) spanned two takes?
I gotta disagree on this one. I know it is not a trivial thing to
change, but the way this is being handled is counter-intuitive and
actually increases the chances of error. This handling is already
causing problems with the original position concept - which frankly I
don't see how you can resolve as long as I can move the start point of a
region across two looped takes that really occur at the same point in
If each take went in its own wav file, there would be no problem with
"original position" alignment and I would not be able to move start
points across different takes (loops). This approach would likely
require less code than what you are doing now, since I would have to
guess there is some special handling for these looped record regions.
I did finally figure out that if I place the edit cursor right at the
punch point, I can right-click a track and choose "insert selected
region" to place the region properly. Of course this was a bit of a pain
since you cannot right click the punch point and move the edit cursor
automatically (you can move the playhead). so I had to manually position
the edit cursor by switching the time displays to audio-frames and then
cut and pasting values.
Paul Davis wrote:
> On Mon, 2007-07-09 at 09:26 -0400, Dan Tepper wrote:
>> Also, to confirm behavior, it appears that when recording this way,
>> Ardour actually records a continuous wav file (including the places
>> where one is not punched in) and creates regions corresponding to each take.
> we don't plan to change this behaviour. it allows us to avoid messing
> around with the filesystem during the loop.
>> It would make more sense (IMHO) to record each track as a separate wav
>> file, so that when I select a take, I can physically delete the others.
> maybe, but ardour is all about non-destructive editing. we don't want to
> keep adding new ways to destroy material, which would just increase the
> chance of you doing it by accident. we'd much rather allow some kind of
> separate process that splits the chosen take into a new file, and then
> allow you to just use the usual cleanup step, which will remove the
> entire multi-take set if appropriate.
>> I'm not so much worried about disk space as I am about just having too
>> many files and regions in a given project for sanity's sake.
> agreed on the regions, but the file part seems in opposition to your
More information about the Ardour-Users