November 2005 - chuck-users - lists.cs.princeton.edu

Inter-shred communication
by Ollie Glaskovik 28 Nov '05

28 Nov '05

I'm trying to communicate between shreds. The docs say static data isn't completely implemented so I realize this may not be possible right now. If it is possible, I wondering if someone could let me know if I'm taking the correct approach here and how I might achieve this goal. I run the command "chuck TheEvent.ck events.ck" and get this result: [chuck](VM): sporking incoming shred: 3 (events2.ck)... [chuck](VM): sporking incoming shred: 4 (events2.ck)... [chuck](VM): sporking incoming shred: 5 (events2.ck)... [chuck](VM): sporking incoming shred: 6 (events2.ck)... "signaling" : (string) "signaling" : (string) "signaling" : (string) "signaling" : (string) ... It keeps signaling but the data is never printed. The three files used are given below. Thanks for any help, Ollie ========================= TheEvent.ck ========================= public class TheEvent extends Event { static int value; } ========================= events.ck ========================= // the event TheEvent e; machine.add( "events2.ck" ); machine.add( "events2.ck" ); machine.add( "events2.ck" ); machine.add( "events2.ck" ); // infinite time loop while( true ) { // advance time 1::second => now; // set data math.rand2( 0, 5 ) => e.value; // signal one waiting shred e.signal(); <<<"signaling">>>; } ========================= events2.ck ========================= // the event TheEvent e; // loop while( true ) { // wait on event e => now; // get the data <<<me.id(), e.value>>>; }

2 1

stack class
by Atte André Jensen 27 Nov '05

27 Nov '05

Hi I took Grahams advise and started coding some of what I'll be needing and came up with the following way to do legato the IMO prober way; latest note on is sounding. I figured I needed a stack, so I made one. Three questions arise: 1) Did I reinvent a wheel? Is there alreasy a stack implemented in chuck (I looked in the docs but didn't find one)? 2) Is there a smarter/smaller/more elegant way of implementing a legato instrument the way I want; latest note on is sounding? 3) Most importently (for my learning chuck): Is there a way of getting rid of the static stack size (int stack_size)? In other words; can I have a dynamically growing array in chuck? Thanks in advance for any reply... -- peace, love & harmony Atte http://www.atte.dk 1 => int device; MidiIn midi_in; MidiMsg msg; if(!midi_in.open(device)) me.exit(); <<< "MIDI device:", midi_in.num(), " -> ", midi_in.name() >>>; sinosc s => ADSR env => gain g => dac; .01 => env.attackTime; .1 => env.releaseTime; .35 => g.gain; 1 => env.keyOff; stack held_keys; while(true) { // wait on the event 'midi_in' midi_in => now; // get the message(s) while(midi_in.recv(msg)) { // print out midi message <<< msg.data1, msg.data2, msg.data3 >>>; if(msg.data3 != 0) { held_keys.push(msg.data2); } else { held_keys.remove_by_value(msg.data2); } if(held_keys.count() > 0) { std.mtof(held_keys.pop()) => s.freq; held_keys.unpop(); if(msg.data3 != 0){ 1 => env.keyOn; } } else { 1=> env.keyOff; } } } public class stack { 200 => int stack_size; int latest_popped; int the_stack[stack_size]; 0 => int nb_elements; fun void push(int element) { if(nb_elements < stack_size) { element => the_stack[nb_elements]; nb_elements++; } } fun int pop() { if(nb_elements > 0) { the_stack[nb_elements--] => latest_popped; return latest_popped; } else { return 0; } } fun void unpop() { this.push(latest_popped); } fun void remove_by_value(int value_to_be_removed) { for(0 => int i; i <nb_elements; i++){ if(the_stack[i] == value_to_be_removed) { this.remove_by_index(i); i--; } } } fun void remove_by_index(int index_to_be_removed) { if(index_to_be_removed >= 0 && index_to_be_removed < nb_elements) { for(index_to_be_removed => int i; i <nb_elements; i++){ the_stack[i + 1] => the_stack[i]; } nb_elements--; } } fun int count() { return nb_elements; } }

2 1

help needed
by Atte André Jensen 27 Nov '05

27 Nov '05

Hi I'm trying to figure out a way to handle the multible keyboards I spoke about. So far I have something like the attached file (linux users can run the load script to load in corect order). But I really need some feedback on the following two things: 1) In sine.ck: listen() never recieves any messages. What am I doing wrong? Is my definition of the InstrMsg class screwed? 2) I would like to spork a member objects function (in zone.ck) but I get a [chuck](VM): NullPointerException: shred[id=5:spork~exp:(2)], PC=[137269484] if I try to. Isn't that possible or am I getting something wrong? Both questions are uncommented in the code. I really hope someone will help me a bit further. Thanks in advance. -- peace, love & harmony Atte http://www.atte.dk

2 1

passing by reference
by eduard 27 Nov '05

27 Nov '05

Hello all, I am trying to pass an integer by reference, but I can't get it right. Could any one help me on this? What I tried works fine for arrays, but not for integers only. Code is below. Thanks Eduard //////////////////////////////////////////////////////////////////////// /////////////////////////////// // main //////////////////////////////////////////////////////////////////////// /////////////////////////////// int a[10]; for(0 => int i; i < 10 ; i++) 10 - i => a[i]; PrintArray( a ); // passing array by reference works fine or am I not referencing? IsInArray( a, 8, 10); // ok 15 => int value; <<<"value before modification is: ", value >>>; ModifyValue( value, 35 ); // seems it's not correct <<<"value after modification is: " , value >>>; ModifyArray( a ); // ok PrintArray( a ); // ok //////////////////////////////////////////////////////////////////////// /////////////////////////////// // functions //////////////////////////////////////////////////////////////////////// /////////////////////////////// fun void PrintArray( int @ array[] ) { for( 0 => int i ; i < 10; i++ ) <<<"a[",i,"] = ", array[i]>>>; } fun int IsInArray(int @ array[], int num, int length ) { if( length > array.cap() ) array.cap() => length; if( !length ) return 0; // array is still empty for( 0 => int i; i < length; i++ ) { if( num == array[i] ) { <<<num, " found in pos ", i >>>; return 1; // num found in array } } <<< num, " not found in array" >>>; return 0; // not found } fun void ModifyValue( int @ val, int newValue ) { <<< "val is: " , val >>>; newValue => val; <<< "val is: " , val >>>; } fun void ModifyArray( int @ array[] ) { for(0=>int i; i < array.cap(); i++) array[i]*5 => array[i]; } // end of code

2 1

Midi problem
by james＠dis-dot-dat.net 27 Nov '05

27 Nov '05

Hi, First of all: thanks for chuck. I'm having a lot of fun with it. Followed by: Hello list. I've just joined. And finally: I may be doing something stupid, but I can't get chuck to connect to midi ports. I realised after a while that it had to connect to an existing port, and wouldn't make a port to connect to later, so I fired up vkeybd. aconnect -i shows: [snippet] client 128: 'Virtual Keyboard' [type=user] 0 'Virtual Keyboard' [/snippet] And chuck --probe shows: [chuck]: found 1 device(s) ... [chuck]: ------( chuck -- dac1 )--------------- [chuck]: device name = "Jack Server" [chuck]: probe [success] ... [chuck]: # output channels = 2 [chuck]: # input channels = 2 [chuck]: # duplex Channels = 2 [chuck]: default device = YES [chuck]: natively supported data formats: [chuck]: 32-bit float [chuck]: supported sample rates: [chuck]: 48000 Hz [chuck]: [chuck]: ------( chuck -- 6 MIDI inputs )------ [chuck]: [0] : "EMU10K1 MPU-401 (UART)" [chuck]: [1] : "VirMIDI 1-0" [chuck]: [2] : "VirMIDI 1-1" [chuck]: [3] : "VirMIDI 1-2" [chuck]: [4] : "VirMIDI 1-3" [chuck]: [5] : "Virtual Keyboard" [chuck]: [chuck]: ------( chuck -- 9 MIDI outputs )----- [chuck]: [0] : "EMU10K1 MPU-401 (UART)" [chuck]: [1] : "Emu10k1 Port 0" [chuck]: [2] : "Emu10k1 Port 1" [chuck]: [3] : "Emu10k1 Port 2" [chuck]: [4] : "Emu10k1 Port 3" [chuck]: [5] : "VirMIDI 1-0" [chuck]: [6] : "VirMIDI 1-1" [chuck]: [7] : "VirMIDI 1-2" [chuck]: [8] : "VirMIDI 1-3" [chuck]: My code is simply: Rhodey s => PRCRev r1 => dac; MidiIn min; if( !min.open( 5 ) ) me.exit(); while(true){ min=>now; } I know it's not very interesting, but it should at least work - shouldn't it? Anyway, running chuck miditest.ck gives: [chuck]: MidiIn: couldn't open MIDI port 5... [chuck]: ...(RtMidiIn::openPort: error starting MIDI input thread!) So, what am I doing wrong? I'm assuming it's me, since I'm new to chuck. I haven't quite got past the urge to write my assignments backwards (for chuck) yet. Any help would be appreciated. James -- "I'd crawl over an acre of 'Visual This++' and 'Integrated Development That' to get to gcc, Emacs, and gdb. Thank you." (By Vance Petree, Virginia Power)

2 1

ck.vim update
by eduard 26 Nov '05

26 Nov '05

Dear all, attached you will find a new VIM syntax highlighting file for Chuck files (thus for files like filename.ck ) In your .vimrc you can specify a color for each of the following labels: Statement, Operator, Repeat, String, Conditional, Comment, Special, Statement, Type, Structure, Boolean and Include in the following manner: highlight comment ctermfg=DarkGreen or you can also use any of the great vim coloring files, which will do this job for you. I hope it is useful to people as it is to me, and please, if you have any good/bad comments don't hesitate contacting me. Eduard

1 0

The ChucK Manual prerelease
by Adam Tindale 26 Nov '05

26 Nov '05

Hi All, I have been working on the manual for almost a year. It is nearing "completion". Some of you may have seen it in cvs. You can get your copy here: http://web.uvic.ca/~art/chuck/ChucK_manual.pdf I am making a public plea for help. The manual needs your help, fellow ChucKer. What needs to be documented? Do you have ideas? Do you know what all the values of the UGens are? The manual should help you use ChucK better. I hope to put it out in the wild "soon", in the truest ChucK sense of soon... I will take patches in plain text or .diff files. I will take criticism or abuse or ideas. I am more than happy to typeset text, but I only have so much time to write up tutorials, etc. If you have an idea for a tutorial, get it started and then I can finish it off when I merge it to the docs. The manual is done with LaTeX. If you or someone you know wants to help with that part of the manual it would be greatly appreciated. Enjoy. I look forward to you comments. --art

3 3

how to write to buffer
by eduard 26 Nov '05

26 Nov '05

Hello all, How can one apply some transformation to the output of an UGen an connect it to dac? For instance, if I want to add a constant k to the output of a sine oscillator and then send this to dac, how should I do it? thanks, Eduard

2 2

semi complicated midi setup
by Atte André Jensen 22 Nov '05

22 Nov '05

Hi I'd like to control chuck from my 3 usb keyboards. Preferably with the abiliy to split one or more of the keyboards to different sounds, dynamic voice allocation is a must for polyphonic sound. I'd like to make the code as modular as possible, in order to easily create one such setup for each song. This means that the definition of which keyboard(s) is spilt and how + routing to actual instruments + code for each instrument should be in seperate files. I'm still very new to chuck, so my first question is simply: is this at all possible with chuck? The second question: (if possible) could soneone provide a rough outline, how to achieve what I'd like? Thanks in advance for any pointers... -- peace, love & harmony Atte http://www.atte.dk

3 5

Stop Beeping at Me
by Adam Tindale 12 Nov '05

12 Nov '05

Hey All, Computers beep by default when you make a mistake. This sucks in a concert. I have recently installed Mac10.4. When I turn off the system volume in the system preferences the terminal will still beep at me. Also vim beeps at me. Here are a few things I did to stop the beeping. Terminal: In window settings in the Terminal menu there is now a tab for emulation where the audible bell option lies. Unclick this little monster to make your shell stop beeping. Vim: In your .vimrc file I had to put set noerrorbells in order to stop the beeping. I know that this is different in Linux to get bash to stop. What about windows? Emacs? I am sure a lot of you will have figured most of this out but it should help that we don't have to hear nasty system sounds at ChucK shows in the future. Cheers, --art

3 2