On Monday 01 May 2006 12:33, Victor Lazzarini wrote:

> Btw, I expect that the ifilcod parameter would take
> a S-type variable, that is, say, bound to a string
> channel. Am I right?

Yes, all opcodes that take a string argument should accept
an S-variable too, even if the manual suggests "must be a
string in double quotes". So, you can use a global string
variable and export it in the orchestra header with
chnexport.

> And another thing, regarding the API, is it possible
> to pass a char *, cast as a float in p-field of a score
> event, to a instrument? If not, would it be possible to have
> support for strings in events ?

It is already possible to use string p-fields (or, more
precisely, exactly one string p-field) for score events.
To create such score events through the API, the function
csoundInputMessage() should be used, rather than
csoundScoreEvent(); note that currently there is some check
that limits the use of the string argument to p5, or, for
'i' events only, p1. The length of strings passed as a
p-field of a real time score event is also limited to 199
characters.

The string p-field can be used by many orchestra opcodes
directly, or it can be copied to a string variable first:

a1    diskin2 p5, 1

Sname strget p5
a1    diskin2 Sname, 1

csoundInputMessage(csound, "i 1 0 10 0 \"foo.wav\"");


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net