I would have thought that variables in instr or opcode scope would not be accessible, but variables at global orchestra scope would be. Surely Csound must have a table of them somewhere we could scan.

However, if that is not possible, it is sufficient if we do as you suggest and have special Csound opcodes for accessing externally created variables. I would suggest

extset sname, xvalue

xvalue extget sname

Under this would be polymorphic opcodes for i, k, and a rate. It would be up to the API client to know how big an array of ksmps MYFLT is for getting or setting a rate variables.

Do you have another suggestion?

-----Original Message-----
From: Istvan Varga 
Sent: Mar 25, 2005 11:10 AM
To: csound-devel@lists.sourceforge.net
Subject: Re: [Cs-dev] API, was Broken again

Michael Gogins wrote:

> I mean global variables that are declared in the Csound orchestra.

Like gaVariable, gkVariable, or giVariable, dynamically at performance time ?
I do not think that is possible, definitely not with the current parser.

However, if you are talking about named "variables" that can be created
or accessed with special Csound opcodes (as well as through the API), that
is very possible (even though not implemented yet), and I can surely
implement it. What opcode names and syntax would you like ?


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/csound-devel





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Michael Gogins wrote:

> extset sname, xvalue
> 
> xvalue extget sname
> 
> Do you have another suggestion?

These seem to be OK. Should it be possible to create variables from the
orchestra ? Also, how about the API functions (name, prototype) ?


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

How about using Matt's code?  

invalue
outvalue

(documented http://csounds.com/matt/MacCsound/doc.html)

I'm sure he'd appreciate it, and it seems that it'd get us all closer
towards common API. It's also common practice for MacCsound users for
the past couple of years now.

steven


On Fri, 25 Mar 2005 17:54:51 +0100, Istvan Varga  wrote:
> Michael Gogins wrote:
> 
> > extset sname, xvalue
> >
> > xvalue extget sname
> >
> > Do you have another suggestion?
> 
> These seem to be OK. Should it be possible to create variables from the
> orchestra ? Also, how about the API functions (name, prototype) ?
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I can tell you that invalue and outvalue are clear, intuitive, and work
great on MacCsound!

on 3/25/05 1:32 PM, Steven Yi at stevenyi@gmail.com wrote:

> How about using Matt's code?
> 
> invalue
> outvalue
> 
> (documented http://csounds.com/matt/MacCsound/doc.html)
> 
> I'm sure he'd appreciate it, and it seems that it'd get us all closer
> towards common API. It's also common practice for MacCsound users for
> the past couple of years now.
> 
> steven
> 
> 
> On Fri, 25 Mar 2005 17:54:51 +0100, Istvan Varga 
> wrote:
>> Michael Gogins wrote:
>> 
>>> extset sname, xvalue
>>> 
>>> xvalue extget sname
>>> 
>>> Do you have another suggestion?
>> 
>> These seem to be OK. Should it be possible to create variables from the
>> orchestra ? Also, how about the API functions (name, prototype) ?
>> 
>> 
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

_______________________________________________________________________
 +  Dr. Richard Boulanger, Professor
 +  Music Synthesis Department, Berklee College of Music
 +  1140 Boylston Street  - Boston, MA  02215-3693
 +  Office Phone: (617) 747-2485   Office Fax: (617) 747-2564
 +  eMail: rboulanger@csounds.com  or  rboulanger@berklee.edu
 +  WebPage: http://csounds.com/boulanger/
________________________________________________________________________
 +  Almost Everything Csound @ http://csounds.com/
 +  The Csound Catalog with Audio @ http://csounds.com/catalog/
 +  The Csound Book @ http://csounds.com/book/
 +  The Csound Magazine @ http://csounds.com/ezine/
 +  CsoundForums @ http://csounds.com/phpBB2/
________________________________________________________________________



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net