16 Mar
2006
16 Mar
'06
6:14 p.m.
On Thu, 16 Mar, 2006 at 10:49AM -0500, Thomas Vecchione spake thus:
Ok so the next question is how best to handle this in
an open format on
the web.
I was thinking of doing something like a forum with the ability to
attach files, but I really dont think this is the best idea. The things
I would like to be able to do is have the ability for people to start
lines of work on each project, post up a track and have others listen to
it and add their track seperately so that others can listen to them and
add one themselves, keeping each track seperate if possible for someone
to come in and mix it all down afterwards. Now snapshots could be taken
by each musician of course of a mix up to that point they made, but I
would definitly think it would be best served keeping each track
individual until the final mixdown so as not to limit the mixdown
process(Of course I am first an engineer of decent quality, secondly a
musician of a poor quality, so this may be a bit biased;)
No, I think this is about right. A bit like CVS for working audio.
Maybe what we need is to have a library of tracks per piece, with a
particular version of the piece being described as a subset of this.
I was thinking maybe have some information about mixing - volume
envelopes to be applied to the tracks for this piece. But, how you
work that at the application level is a nightmare. I think the last
thing we'd want to do is force, say, Ardour. Not that I have anything
against it, but different people work in different ways.
The other thing important about this is the ability to
have a running
conversation between all those involved, possibly an initial concept
statement from the first person to post up a track, with the ability to
be modified later on?
Yes, good idea. Forking should be allowed/encouraged, maybe, but
keeping the same library so that cross-pollination can happen easily.
James
Discussion and ideas are welcome here.
Seablade
--
"I'd crawl over an acre of 'Visual This++' and 'Integrated
Development
That' to get to gcc, Emacs, and gdb. Thank you."
(By Vance Petree, Virginia Power)