ftfind used to be part of the API but was removed (I don't know why,
perhaps a naming conflict or something). I will put it back, probably under
a different name. You will then be able to access ftable memory from
external programs.

Original Message:
-----------------
From: iain duncan iainduncan@telus.net
Date: Sun, 2 May 2004 18:14:15 -0700
To: csound-dev@eartha.mills.edu
Subject: [CSOUND-DEV:4541] Re: csound API question


> but it should be no sweat to add a ftfind() to the API. [with future
> implementation of named function tables!!]

The above would do what exactly? I'm thinking it would be cool if the area
of memory that ftables live in could actually be shared with another app so
that while csound is using the tables they could also be read and updated
from a host app or second app. Would this be a pretty major hack of csound?
I suppose another option would be to have the tables shadowed in the other
app and have csound and the host both send score messages to each other
indicating what they were doing with the tables but that seems a bit
convoluted if not necessary.

The idea being that a host sequencer could control/read the tables used
within csound for patch data, mixer routing, etc.

Thanks for the response.
Iain


>
>
> BY THE WAY, looking at csound5 i notice the FUNC **flist is still not in
> the ENVIRON globals -- dont you think it should!?!??
>
> [although at some point i could see some benefits to having real global
> functions, etc that multiple csound processes can share]
>
> -m
>
>
> On Sun, 2 May 2004, iain duncan wrote:
>
> > I'm wondering if the csound API makes it possible for a host app to
> > read/write directly to csound ftables or share memory with csound
ftables.
> > If so, which part of the API should I look at for that.
> >
> > Thanks,
> > Iain
> >
> >
>


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .