Re: [linux-audio-dev] discussion about development overlap

[Paul Barton-Davis]

>By default editing ecawave in is in fact non-destructive (it also has a
>direct mode). When you do the first editing operation, ecawave creates a
>temp file for editing. The temp file is opened in read/write -mode, so all
>following edits are done in-place. So in normal use, there aren't that
>many moments where you have to wait for disk i/o to complete.

but you said "large files". what happens when the soundfile is 500MB ?
where are you going to put the tmp file ? do you just assume there is
always space for this approach ?

>ecawave isn't aimed at, at the moment anyways. When you are editing one
>track of a song, independently of the context, you don't really want move
>its material around (ie. relocating a guitar solo, without hearing the
>drums).

actually, i would have almost said the opposite was true, at least
sometimes. but i supposed that such operations would fall into what
you mean by "audio sequencing". although i accept this as a legitimate
limitation to define, it rules out much of the most interesting stuff
that can be done with "large soundfiles" (as opposed to single
samples).

--p