Hans;<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The problem is that it might not be possible, if some keys are used for playing and other for manipulating data.<div class="im">
</div></blockquote><div><br>I don't think there will be a issue with that. Your program would have its data and its structure for playing sounds and both would be affected by a single shred that would parse the keyboard. That sort of thing is quite possible and a fairly normal type of structure for a ChucK program.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
But as for the voice assignment problem, perhaps there might be the need of some structure handling it. Hope for the future :-).<br><font color="#888888">
</font></blockquote><div><br>I'm certain you can do way better than hope. You'll need to define for yourself what voice assignment means to you here. From there on it's a matter of translating that definition to formal code. Personally I think it's a good thing that ChucK has no inherent idea of what voice assignment and cycling mean as that means we get to figure out what we need in our specific situation. The developers can't foresee what any individual programmer might want or need (I'm quite certain they are already very aware of that...)<br>
</div></div><br>> I was only hoping not having to program so much...<br><br>Sorry :¬).<br><br>I fear you're going to have to program a bit. It's not all *that* much and 90% is coming up with a good plan.<br><br>
Yours,<br>Kas.<br>