I think that this derivation handling might be one of the big keys to
the whole system here. Sometimes, slight variations in a track can make
all the difference, and it's one of the areas where collaboration and
community criticism can come into play. Listen to some of Brian
Wilson's Pet Sounds sessions to get an idea of how many different takes
were made of each particular musical line and how many of these pools of
takes had to be chosen from and mixed into the final project. Music
isn't nearly as clean as software is in terms of black and white
improvements, and most of the musicians around here that I've talked to
consider the concept of a 'revision' of a track or an 'update' to be
pretty ludicrous.
From experience, it's as hard as anything to choose exactly which take
of a musical line should go into the final mix, and with a system like
this, you could ask other people's opinions and get the kind of
assistance that you'd pay a producer and a recording engineer large sums
of money to do. This would be one of the things that'd draw small
artists into the fray, as most small acts can't afford the kind of
advice and expertise that a community could provide. "With many ears,
all out-of-tune guitars stay on the pitch", perhaps.
As Luke, Greg, and Adrian said, there will be more interesting stuff to
ruminate on tomorrow.
-Steve Salevan
ssalevan@xxxxxxxxxx
Luke Macken wrote:
Instead of providing a central colloboration server to manage song/track
revisions, I think it should be designed around handling derivations
(while
keeping a solid audit trail of creators and licenses, of course).
There was much brainstorming yesterday, and there is definitely going
to be
more tomorrow, so hopefully we'll be able to add some more context to
this initiative in the near future.
luke
_______________________________________________
Fedora-music-list mailing list
Fedora-music-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-music-list
