Re: [Bluemusic-users] blue live and windows

[Steven Y. <ste...@gm...>]

day Hi Pia,

> I wasn't thinking about a 'total conversion'. My initial idea (not that my
> initial ideas are always good) was more along the line:
>
> - add a user option 'render via Csound-External/Csound-Live!'
> - add a SoundObject -let's call it CsoundLive-, similar to the ObjectBuilder
>
> - now whenever the user chooses 'render external', CsoundLive objects are
> simply ignored (this might be refined, just for getting things started)
>
> - with CsoundLive! (I can't resist: I'm sure Ableton is already pretty
> scared) just dump the 'normal' blue objects to the csound proxy and process
> the CsoundLive! objects in a loop. (quite some unproven assumptions here)

blueLive already has some of this covered in that you can edit your
soundObject and press the trigger to generate and pass score to a live
running version of Csound.  These objects are ignored when the normal
timeline is run and the normal timeline is ignored when the blueLive
stuff is running.  There's no timers or things like that however.
More could certainly be done to blueLive to make it more of a
performance platform. I've used it in the past at Bay Area Csound User
Group meetings and originally built it for those occasions as well as
to test ideas in realtime, but it's not the strongest offfering.  It's
not high on my list to redo (I redid blueLive a couple months ago but
it was only a small change), but if anyone would like to put together
ideas and better contribute, it'd be really quite welcome.  I'm
swamped with things until after March/mid-April but will have some
time to help out on this if it gains momentum.  (BTW: If anyone is
going to the Linux Audio Conference in Berlin in March, I've been
accpted to do a demo of blue there; I'll also be giving a lecture on
blue and it's design in Ireland earlier in March, for anyone there).

> I can imagine that this isn't trivial and won't be done on a rainy sunday
> afternoon. But at least the changes would be somewhat local. I only had a
> quick glance over your code, but it seems, that most of the communication
> with csound is encapsulated in ProcessConsole, which helps.

Right, I had planned to start at the ProcessConsole as well and to do
a simple change of using a Csound API object instead of a Java
Process.


> > few script objects in blue and while it's possible to use Ruby within
> > blue already via the External SoundObject, it doesn't have the same
> > integration as use the Java-based Jython (Python) interpreter or Rhino
> > (JavaScript) interpreters.  If interested, I could possibly add a
> > JRuby SoundObject and Instrument to the mix.  Doing something like
>
> Now that would be *great*. I already did some ruby stuff, simple things; a
> note class, a simple framework for i-event processing, and based on that, a
> chord generator and arpreggiator.

That's great to hear!  I use a great deal of python myself in blue and
I'm sure I could set up a Ruby object to work in a similar way as the
Python object.  I'll be taking a look to see what's required to embed
JRuby (java libraries, ruby libraries, etc.).  The one concern I'm
having at the moment looking at all the libraries is that it'll
probably bulk up the size quite a bit of the download.  I'll play
around to see what is absolutely essential and hopefully it won't be
too much to add.

Thanks!
steven