While it is possible to increase the limit, the space for arguments is
of static size (due to the way opcodes work in Csound), so having a
higher maximum is at the expense of wasting space and making note
allocations slightly slower when a large number of arguments is not used.
Alternatively, you could use a different mechanism (tables, zak,
channels, etc.) to pass unusually large number of values.

By the way, the limit was intended to be 24, not 23, so there may be
a minor bug.

On Thursday 04 May 2006 03:58, David Akbari wrote:

> Lately I've been working a lot with this device called the lemur that 
> transmits OSC [1]. I have reached the point where I need more than 23 
> arguments to output from this device's interface.
> 
> I've discovered what could potentially be an abnormality in the UDO 
> mechanism [0].
> 
> Can someone please tell me why the commented out instrument in example 
> [0] does not compile ? It is *identical* in every respect to the 
> version that does compile, however as soon as the output args exceed 
> 23, Csound is erroring out simply with 'too many output args' - is 
> there a limitation of <= 23 output args in UDO's ??? Is this intended ? 
> Is there a way to possibly extend this to 50 or maybe 100-200 (like 
> p-fields) ??? I would really find it useful if it were possible to have 
>  >= 24 output arguments in a a UDO ! Hopefully this is just user error 
> of some sort ... any help is appreciated in understanding this behavior 
> !


-------------------------------------------------------
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