Re: [Bluemusic-users] [announce] blue 0.114.0
Brought to you by:
kunstmusik
From: Steven Y. <ste...@gm...> - 2007-03-02 16:08:49
|
Hi Hector, It's curious, for myself, I am interested in the representation of music, not so much performance aspects like playing an instrument. So, blue has more of the former in its conception than the latter. Regarding realtime Csound, I do think it's an appropriate tool. I remember back in San Francisco getting together for the Bay Area Csound User Group meetings, Matt Ingalls presented some work of his with MacCsound that really made me think "Yes, this makes a lot of sense!" and that it *was* a good platform for performance work, whether live or in your case in the studio. In my optinion, text is really great for expressing algorithms but not very good for configuration of those algorithms, and vice versa for GUI. That's what makes MacCsound a really neat tool in that you can visually build the interface and in realtime work with the interface for configuration of the algorithms, while coding of the algorithms is done via text in Csound code. I think it's a case of using each for its strengths. When I first built BSB, I was very much interested in the above idea of using GUI for visualing and easily modifying configuration and using code for expressing the algorithms. What I did not consider was live performative aspects, but as I mentioned elsewhere, it might just happen by side effect that it could be used as an interface for performance. The more important thing now though is for me to get back coding so we can see what happens! =) steven On 3/1/07, Hector Centeno <hc...@gm...> wrote: > Hi, > > Thank you for your sharing your opinions about my idea of including > realtime controllers. I wouldn't consider realtime use of Csound as > being out of it's purpose (am I wrong? should I switch to PD?) and > also I wouldn't consider it's realtime use to be a performance only > technique since it could be part of the compositional process where > material needs to be generated in this way for further non-realtime > processing and layering (I don't perform live using Blue and Csound, > in fact I never perform live... maybe I should try, he,he ), so from > this point of view it would have a place within Blue's concept. > > Cheers! > > Hector > > > On 2/28/07, Steven Yi <ste...@gm...> wrote: > > Well, blue certainly been mature IMO for a while, so perhaps I should > > go ahead and update the major number. The argument against using year > > is a good one so I'll drop that idea. I think I'd like to up the > > major number of the release when the API stuff can be worked out as > > that seems signficant enough a change to merit it. After that, I'll > > continue to do as I have been, increasing minor number for new > > releases and the last number if it's a bug fix build. > > > > So, 1.0.0 will be here sometime soon(after 6+ years of working on it... :P)! > > steven > > > > p.s. - Soon should be sometime within the next few builds, as I > > already started exploring ideas on working to ensure that blue finds > > the installed csound API... > > > > > > On 2/28/07, Dave Seidel <da...@su...> wrote: > > > +1 > > > > > > - Dave > > > > > > Michael Bechard wrote: > > > > Regarding versioning, I always look to the version number when determining if I'm going to use a given piece of open source software; I generally don't like mucking around with an immature app, no matter how potentially useful it may be. Having blue in perpetual sub-1.0 status will only hurt it, IMO, and switching to a year-based versioning system will give a potential user no indication of how mature your software is or how long it's been around. > > > > > > > > Michael Bechard > > > > > > > > > > > > ------------------------------------------------------------------------- > > > Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net's Techsay panel and you'll get the chance to share your > > > opinions on IT & business topics through brief surveys-and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > _______________________________________________ > > > Bluemusic-users mailing list > > > Blu...@li... > > > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share your > > opinions on IT & business topics through brief surveys-and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Bluemusic-users mailing list > > Blu...@li... > > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > > > > > -- > =============================== > http://www.hcenteno.net > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > |