| Thank you Oeyvind,
Maybe I didn't look closely enough, but perhaps this could be written
more explicitly in the manual? I see now what "implies declaring the
channel with mode 1" means, but your explanation is much clearer. The
text for these opcodes seems a little terse.
Presumably, declaring a channel with mode 1 using chnget, and then using
the same channel with mode 2 using chnset, will make that channel "mode
3" (both read and write)? I'll be trying this when I get home later
anyway, I'm "at work" at the moment.
Joe
Oeyvind Brandtsegg wrote:
> You can declare them in the instrument too. And you don't even need to
> explicitly declare them;
> - the first time you use chnget the channel will be implicitly
> declared (read mode)
> - the first time you use chnset the channel will be implicitly
> declared (write mode)
> This means that you can just start using them without any declaration.
> If you feel it is more clear, and feel more safe by explicitly
> declaring the channels, that will work well too.
>
> best
> Oeyvind
>
> 2008/6/19, Joseph Sanger :
>> Hello there list,
>>
>> Just a quick question... I've never used chn before. I intend to use it
>> purely within csound, not using the API.
>>
>> Do chn channels need to be declared in the orchestra header, or is it
>> possible to declare them within instruments? I'd like to (for instance) pass
>> a string to an instrument from the score, and use that as a channel's name.
>>
>> Thanks!
>>
>> Joe
>>
>> PS Many thanks to Mr. Sateler for the Debian package, works very nicely on
>> DebianPPC!
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
>> csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
|