Thanks for the reply, Tim.

On Tue, May 13, 2008 at 4:37 AM, Tim Mortimer <timmortimer@d2.net.au> wrote:
>
> Hi Chuck - we haven't heard from you for a little while - glad youre back in
> the mix.

In and out, I been busy and internet ain't so cheap here as it is back home.

> I recently had some discussion about some of these issues with Oeyvind, &
> certainly we agreed that handling any real time & scheduling on the csound
> side of the fence is probably the way to go. If you use the csound api in
> python, all your python functions can basically be seen as global by the
> csound "mainline" using pycall.

That is interesting.  At first I thought that wouldn't be useful, but
one of the options will be for users of my program to type their own
Csound orchestras, so it could indeed prove useful to have functions
they can access that way.

> That's my general feeling on the subject - now over to the more technically
> astute for any specifics.

I suspect there aren't too many specifics that go against the idea of
using Csound for everything it is capable of.

> Generally, I handle all my tempo calculations in python, not csound, & just
> supply csound with absolute times. This is something i don't presently do in
> realtime, & my demand for metronomes & metered rhythms is in general fairly
> low on my priority list... I heard enough 4 on the floor in the 90's to last
> me a lifetime! ; )

One of my reasons for making this program is for other microtonal
composers to use it, and some of them (like me) like meters, even if
they change on every bar.
Thinking about it some more, I think I will have to pass tempo
statements to Csound instead of absolute times, for the simple reason
that some may wish to write percussion or rhythm tracks directly in
Csound .sco (or other programs) and sync to my sequencer.

-Chuckk


-- 
http://www.badmuthahubbard.com