Re: [Bluemusic-users] blue brainstorming
Brought to you by:
kunstmusik
From: Steven Y. <ste...@gm...> - 2008-03-25 05:57:43
|
Hi Atte, Thanks for sharing your perspective. I think it's important to keep this way of working in mind and I'd certainly love to support these interactions as I think they'd complement the existing blue user interface interactions well. There is a bit of an impedance mismatch between MIDI and csound I think, so some data massaging will be necessary, but I think something could get worked out. There used to be so many things I wanted to work out first so I would always push MIDI support away (plus I find MIDI just awfully limited with 0-127), but I think a number of infrastructure things are beginning to get put in place so MIDI can be better supported. One thing we'll have to figure out is a scheme for instruments being either drivable by MIDI or by pure score (which I think might be the better solution). It may require a certain instrument building convention to be able to be driven by score, maybe some pseudo-opcodes that function like csound's mididefault, etc. So, there's certainly things to work out. Controller data actually seems much easier to map, but note data I think will be tricky. steven On Mon, Mar 24, 2008 at 12:00 PM, Atte André Jensen <att...@gm...> wrote: > hannes kahl wrote: > > Hello all, > > > > Integration of the Csound API is relatively easy I think, and will be > > the solution for live interaction with blue. The Java and Python > > wrapping is very well and can help a lot. BUT: One have to consider > > is blue a composition environment (than more interest should point to > > the visual representation of music (UPIC, ChucK-Audicile, IanniX, > > SND, LilyPond can be inspiring)) OR is blue a life workstation. Blue > > development, I think, can not go to both directions. > > I think I understand your point but I don't agree. > > I'm a jazz pianist by education, and I'd argue the distinction between > composition and performance is not always relevant. It may be in > "classical" music where the composer thinks out the great scheme and the > musicians job it to execute the music the best he can. But in more > improvised formats the performance is the music more than the composition. > > I find working in blue very much a composition-in-traditional-sense > kind-of-experience, which is ok, and very instructive. But I miss the > ability to instantly interact with the music as it plays back. And we're > not even talking live performance yet. > > Basically, if everything blue does was done in realtime, I think I'd be > more than happy. > > Let's take automation: Now I have to click some points, listen for a few > seconds, adjust the points to what I hear, listen back, etc... With the > live-enabled blue I could assign the automation to a button on a > controller, and jam along with the music to get the feel of how the > automation works to the button, record as I go along, and the first > complete performance would mean the automation was done. > > I would argue it's faster this way, but more importantly I feel I get > closer to the music creation process. This might just be me with my > background, but that's how I feel. > > > -- > peace, love & harmony > Atte > > http://atte.dk | http://myspace.com/attejensen > http://anagrammer.dk | http://modlys.dk > > ------------------------------------------------------------------------- > > > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > |