[LAU] A virtual LAU chillout band - is this clearer?

plutek-infinity plutek at infinity.net
Wed Nov 14 13:38:21 EST 2007


>Date: Wed, 14 Nov 2007 11:17:00 -0500
>From: Frank Pirrone <frankpirrone at gmail.com>

<snip>

>Patrick and the Band!
>
>I either didn't make myself clear enough or I'm not myself clear on the 
>concept, but all that seemed to be necessary to explore this process is 
>what I stated in my last message:
>
>    * Song starts at a point in time with a designated originator's
>      idea, perhaps the chap who raised this possibility.
>    * He lays down a track on whatever instrument fits his
>      conceptualization and playing skills.
>    * A compressed file is uploaded to our server/repository along with
>      a project file appropriate to our choice of application.
>    * The relatively small group of participants downloads that track,
>      which at a few megabytes and a limited number of downloads is no
>      bandwidth problem at all.
>    * Each downloader who comes up with something they like and feel is
>      creditable simply uploads their compressed track.
>    * Now there are two tracks on the server following the first upload.
>    * Each track is aligned by virtue of the project file and will
>      automatically register correctly in that application for everyone.
>    * Tracks increase in number on the server, but only the new ones are
>      downloaded - names with cat, instrument, and timestamp will make
>      them clear enough.
>    * People share two things as matters proceed - their impressions of
>      the tracks being contributed, especially those duplicating a part,
>      say background riffs, and also their impression of how the tune is
>      developing.
>    * A fork is both uneventful and consequential to the process. 
>      Anyone loving what they currently have in hand can simply leave it
>      at that and take it from there.  Don't like my guitar part or
>      playing?  Trash it and substitute yours.  Love it?  Okay, it's in.
>    * To that last point, a call or even consensus can arise saying,
>      "Awesome guys, that drum part is it- done, and so is the bass and
>      the guitar.  Thanks, no more submissions needed on those tracks.:
>    * That's cool, my lead got in.  Hmmm, I'm bored now.  Wait, I'll
>      contribute a backing or harmony line vocal track.
>    * Finally, when a call or even consensus arises saying, "Damn, that
>      tune's a bitch.  Let's go with it." once agreement is established
>      everyone uploads the higher quality tracks of the "winning" parts
>      and things move on to the mixing and mastering stage.
>
>We'll argue over how to do that part when that bridge comes to us!
>
>Capiche?  Trash my idea if it deserves it, but just be kind...


perfectly clear and sensible. it does bring up the question of what the objective is. your outline assumes a single, "finished" version of each of a number of songs, agreed to by all and then published somehow. my instinct is that that is somewhat limiting -- i.e. it eliminates alternate mixes, and requires concensus as things go. however, the more i think about it, the more it makes sense to give the whole endeavour that sort of structural clarity -- it increases the sense of a unified community project, and also increases the likelihood of actually getting something "done".

'course, there may be some rogue elements who drift into quirky, personal remixes... that's cool, too. they could be published separately by those individuals, or there could be a section of the main site reserved for such mutations.

-- 
.pltk.



More information about the Linux-audio-user mailing list