yaaarrrgg
February 11th, 2009, 08:48 PM
Here's an idea for a music application:
A tool that allows two musicians (or more) to work on a project in real time, each recording tracks, from two or more different physical locations.
Newly recorded audio tracks would stream (p2p) to all other running instances of the application. So that after each track is recorded, each person has a complete copy of the media files. One person can assume control of the mix, then saving the project would propagate changes. If this used compressed audio as the native format, you could stream this in real time without much latency.
Also this app should run natively on the target platforms, without any additional services required. It would not have a business model wrapped around it, since the goal would be to make it easier for musicians to make music.
Or if there are any servers, it would be very light-weight, only handling routing the machines together, then passing all processing to the target machines for p2p file sharing. This way, any one person in a cluster could run the service. The bottom line, is there's no business model wrapped around it ... limiting services, bandwidth, storage, etc.
Overall this software would be a cross between a multi-track recorder (like ardour or traverso), p2p file sharing, and maybe a simple instant messenger. I suppose some form of file merging or locking might be useful (like svn/cvs) but a simpler approach would just be to allow individual contributers to fork a copy of the project.
Just a random thought ... :)
A tool that allows two musicians (or more) to work on a project in real time, each recording tracks, from two or more different physical locations.
Newly recorded audio tracks would stream (p2p) to all other running instances of the application. So that after each track is recorded, each person has a complete copy of the media files. One person can assume control of the mix, then saving the project would propagate changes. If this used compressed audio as the native format, you could stream this in real time without much latency.
Also this app should run natively on the target platforms, without any additional services required. It would not have a business model wrapped around it, since the goal would be to make it easier for musicians to make music.
Or if there are any servers, it would be very light-weight, only handling routing the machines together, then passing all processing to the target machines for p2p file sharing. This way, any one person in a cluster could run the service. The bottom line, is there's no business model wrapped around it ... limiting services, bandwidth, storage, etc.
Overall this software would be a cross between a multi-track recorder (like ardour or traverso), p2p file sharing, and maybe a simple instant messenger. I suppose some form of file merging or locking might be useful (like svn/cvs) but a simpler approach would just be to allow individual contributers to fork a copy of the project.
Just a random thought ... :)