April 2007 - chuck-users - lists.cs.princeton.edu

mini Audicle crashes when removing shreds
by Leuthold Dominik 24 May '07

24 May '07

hi guys i continuously encounter crashes with the new version of mini Audicle. it happens when i try to remove a shred from the virtual machine, when the corresponding shred is already closed. (removing by clicking on the "-" sign in the vm form). steps to reproduce: 1: open the otf_01.ck from the examples and add it to the vm 2: close the shred window of otf_01.ck 3: remove the shred by clicking ont the "-" in the vm 3: peng! aargh.. this drives me crazy :-P unfortunately i encounter this error every 10 minutes cause i'm livecoding with a lot of shreds the same time. sorry to say, but i need to go back and use the older version - too risky for my health ;-) cheers /moudi

3 7

Anyone else running ChucK dual-core in 64-bit mode?
by Ken Restivo 02 May '07

02 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 By the way, I searched around and didn't see any mention of the problem I've seen (ChucK segfaulting in Ugen constructors). Is anyone else running dual core 64-bit machines out there (on Linux, especially)? - -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGMVQSe8HF+6xeOIcRAmoAAJ4lQzZ4sTgVpKP0Bn1fqDU+3lrOFQCgk++1 +D9RvFdNBJKOaY2KB0k/rT4= =Pdiq -----END PGP SIGNATURE-----

5 12

stereo ugens yet once more
by Lukas Degener 28 Apr '07

28 Apr '07

hi again, could you tell me what's the current state of affairs concerning stereo (multi-channel) ugens? I'm looking through the code and I can see that there is somthing going on, but I was not yet able to completely grasp the idea. :-) I see I can specify in and outs in type_engine_import_ugen_begin(...), Further it seems that for each channel, a "sub"-ugen is generated for me, everything basically looks put in place allready...so... How do I control how those "sub-ugens" are ticked? Would it be wise to just set their tick function pointer directly? Is there maybe already some example code which I could have a look on? Or am I looking in the wrong places? Sorry for pestering you with my questions :-). Kind Regards, --lu

2 5

chuck segfaults at startup on core2duo on linux jack
by Ken Restivo 27 Apr '07

27 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alas, I am dead in the ChucK waters. Just got a new Core 2 Duo laptop. Built ChucK 1.2.0.8 for linux-jack. Planned to use this machine for ChucK experimentation and live performance. And then: $ chuck cw.ck Segmentation fault Gah! $ chuck --probe [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 -- 3 MIDI inputs )------ [chuck]: [0] : "Midi Through Port-0"Segmentation fault Sad. No ChucK for me! This is with the stock 1.2.0.8 - -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGJbF8e8HF+6xeOIcRAllLAKD0f78S+IOEEFqJIGcASfthaIX5mACghGW1 qb6fSvK2uBex703V7MQKri8= =kaw9 -----END PGP SIGNATURE-----

2 3

chuck~ (for PD) version 0.1.3
by martin robinson 16 Apr '07

16 Apr '07

I've released a new version of the chuck~ external at: http://www-static.cc.gatech.edu/ugrads/m/mjr/chuck~ This version incorporates the latest ChucK release (1.2.0.8) and a few small improvements. The port to Windows has also been integrated (much thanks to Graham Coleman). Please be sure to read the errata for an important note on Windows usage -- hopefully I'll get this one fixed soon. Binary distributions for Mac and Windows are available. -- martin robinson

2 1

recording of my first livecoding session
by Leuthold Dominik 16 Apr '07

16 Apr '07

hey list as i mentioned last week i had my first chuck concert. i made a recording of the whole concert. you can get it here: http://www.maitredeplaisir.com/data/sounds/div/MdP_-_performs_ChucK_-_Live_a t_f_und_b_13.04.07.mp3 i had a lot of great feedback from mostly surprised people. they never saw something similar i guess. hehe... livecoding isn't that popular at all here in switzerland. i showed the miniAudicle on a screen so they were able to follow the process. the most common opinion was, that the sound itself wasn't that interesting, but in combination with the shown screen it was very unique. the reason for this could be, that it was a "one man show" and i had a lot to do with add/modify/remove and coding shreds. this means that the music remained the same for longer times. (you'll confirm this while listening to my recording) i came to the conclusion that i will try to iniciate a "chuck ensemble" with about 4 people. jassas /moudi

2 1

MIDI program change causes event parsing error
by Ken Restivo 15 Apr '07

15 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The following code causes an "event parsing error!" whenever a 2-byte MIDI message such as a program change is sent: // the midi event MidiIn min; MidiOut mout[3]; // the message for retrieving data MidiMsg msg; // open the device if( !min.open( 0 ) ) me.exit(); <<< "MIDI in device:", min.num(), " <- ", min.name() >>>; for(0 => int i; i < mout.cap(); i++){ if( !mout[i].open( i + 1 ) ) me.exit(); <<< "MIDI out device:", mout[i].num(), " -> ", mout[i].name() >>>; } int eventnum; // TODO: subclass MidiMsg and stick these in there int channel; int command; while( true ) { // wait on the event 'min' min => now; // get the message(s) while( min.recv(msg) ) { msg.data1 & 0x0F => channel; msg.data1 & 0xF0 => command; // print out midi message <<< eventnum, "(", msg.data1, ")", channel, command, msg.data2, msg.data3 >>>; eventnum++; // note, controllers (not bank!!), or pitchbend if (command == 144 || (command == 176 && (msg.data2 != 0 && msg.data2 != 32)) || command == 224) { mout[0].send (msg); } else { // XXX program changes are 2 bytes! // how to make MidiMsg handle those?? mout[1].send(msg); } } } The exact error message is: "RtMidiOut::sendMessage: event parsing error!". How does one cajole MidiMsg into sending a 2-byte Program Change? It's a pretty standard, um, MIDI message. - -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGIe3We8HF+6xeOIcRAgKJAKDTJiuNklwhUD8NLAC+4TEJEif04ACdF1VU ZVfLQqAbb5m0zW9t4FGUWO4= =2CHt -----END PGP SIGNATURE-----

2 1

Getting the channel of a MidiMsg?
by Ken Restivo 15 Apr '07

15 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm looking through the ChucK docs and source code, and I can't figure out how to get the MIDI *channel* from a MidiMsg event. Sure, there's data1 (the command), data2, and data3, but... no channel. Thanks. - -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGIdkMe8HF+6xeOIcRAqp/AKDhn2NVd0TIiSakwwS3PEB4i5XKSgCeL8e9 cl93uMfs609o02c9l0gzbW0= =LZsX -----END PGP SIGNATURE-----

2 1

MIDI channel -- solved
by Ken Restivo 15 Apr '07

15 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Looks like I just have to OR the data1 with 0xF to split out the channel and command. Sorry for the noise. - -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGIeRge8HF+6xeOIcRAuzyAKDFFA8M5df7RM7yCLD7JrAb/doLMQCeMpWS bJKb7uNGLYUzcby/HK0rxMQ= =p/PL -----END PGP SIGNATURE-----

1 0

Strange Behavior
by Piero B. Contezini 13 Apr '07

13 Apr '07

Hello, I don't know if this is the right place to put this on but, this code is crashing randomly on my tests: MAUI_View window; MAUI_Slider knob_0; window.size(300,300); window.name("Test"); window.position(0,100); knob_0.range(0,127); knob_0.size(150,knob_0.height()); //cut_knob_0.position(0,0); knob_0.name("Knob 0"); knob_0.displayFormat(MAUI_Slider.integerFormat); // impulse to filter to dac Impulse i => BiQuad f => Pan2 p => dac; // set the filter's pole radius .99 => f.prad; // set equal gain zeros 1 => f.eqzs; // set filter gain .5 => f.gain; window.addElement(knob_0); window.display(); 1 => int device; MidiIn min; MidiMsg msg; if( !min.open( device ) ) { <<< "erro ao iniciar device:" , device >>> ; } else { <<< "device inicializado:" , min.num() , " -> " , min.name() >>>; } public void controlKnob_0() { while(true) { while ( min.recv(msg) ) { msg.data1 => int msg_1; msg.data2 => int msg_2; msg.data3 => int msg_3; if(msg_2 == 3) { knob_0.value(msg_3); } } min => now; } } public void Distortion() { while(knob_0.value()) { knob_0.value() => float value; value * 39 => f.pfreq; // value => i.next; } min => now; } spork ~ controlKnob_0(); spork ~ Distortion(); while ( true ) { 1.0 => i.next; // Std.rand2f( 250, 5000 ) => f.pfreq; Std.rand2f( -1, 1 ) => p.pan; 100::ms => now; } What i'm doing is mapping one knob of my bcd2000 to a MAUI Slider, to see on the screen the position of the knob, as i've posted here before, the midi itself is hanging up using this controller, but I think it might be something i'm doing wrong, anyone can point me out a clue on what could be it? Thanks Piero

3 4