Hi, again, Core.<br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div> </div> <div> </div> <div>// setting up the keyboard to trigger Osc
<br>// this should trigger a middle c tone when A key is pressed</div> <div>{<br> if (<a href="http://msg.is" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">msg.is</a> ButtonDown()) and if (msg.my_keynumber
= 65 then <br> SinOsc s => Dac;<br> 261 => s.freq;<br> 1::second => now<br>}</div> <div> </div> <div>it still giving me errors ? even when i running the <a href="http://kb.ck" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
kb.ck</a> file in chuck any help would be great thanks </div></blockquote><div><br>Well, it's giving you issues because it's not correct syntax. Unlike humans programming languages demand that you write everything in a certain way. For example I understand what you mean with "and" here but ChucK will only get it if you write "&&" or if the structure of the program implicitly means we want both things to be true (like below). Like with learning French or Japanese in learning ChucK you will need to learn the right syntax. Like with other languages there are definitions on what correct syntax is (the manual) but also like other languages the best way to learn is to try to figure out what others are saying (the examples directory) and simply trying to speak it yourself.
<br></div>-----------------------------------8<-------------------------<br>65 => int mykeynumber; //define what key we are interested in for readability<br>SinOsc s; //Let's define the oscillator outside of the loop, it will save issues
<br><br><div>{<br> if (<a href="http://msg.is/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">msg.is</a>ButtonDown() ) //detect the type of message<br> { <br> if (msg.which == mykeynumber)
<br> {<br> //This bit will only get run if the message is a a button-down one AND it refers to the right button<br> //Structuring it like this means you can check for other buttons as well in a cleaner way.
<br><br> s => dac; //notice "dac" is lowercase, it's not a Ugen as such.<br> 261 => s.freq;<br> 1::second => now;<br> s =< dac; //disconnect once we are done
<br> }<br> }<br>}</div> -------------------------------------------------------------<br>That's how I would rewrite what you wrote. I had to interpret it a bit as I'm not 100% sure what you are after exactly but I think this is fairly close.
<br><br>The advantage of this structure is that you could add something along the lines of this bellow the paragraph that deals with detecting the key;<br><br>----------------8<--------------------<br>else if( msg.which
== anothernumber) //you'll need to define this other number, of course<br> {<br> s => dac; <br> 330 => s.freq; //another key another note. <br> 1::second => now;<br>
s =< dac; <br> }<br>--------------------------------------------<br><br>This means we only have to check for the message type once which saves CPU and leads to a cleaner program.<br><br>Did you have a look at the keyboard-organ example in the HID dir? That example might be interesting to you too.
<br><br><br>Oh, and don't worry about getting errors, everybody gets them, it's rare to write something larger with no typos at all. Just take them on one by one and try to figure out what the issue is, correct it and try again.
<br><br>Hope this helps,<br>Happy ChucKing!<br>Kas.<br></div>