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

De-Lurk and showing some stuff I've written the last few days
by Loscha 11 May '07

11 May '07

Hello All. My name is Edward. I'm a synthesis buff from Melbourne. I've been using Chuck for about a week now, and I'm really loving it. I haven't really learnt to use a sporking language before. I used to program in Borland Turbo C 2.0 back in the early 90s, and also did a lot of QuickBasic, but, I never really caught up to the modern age so to speak. I'm only 29, so I thought, there's no time to learn like now! I think I've got this all sporked off in a reasonably sensible way, but, I could probably do more. I am totally open to people sending me suggestions (on or off list). I'm not "precious" about my program in any way. I hope some of you get some use from this example. I don't think it is by any means "distro example" quality, but, I hope that with some work, and the addition of some more features not present in examples currently in distro, that one day it might be! I have tried looking around for a model for sympathetic strings, and have had no luck. If anyone has any advice, please advise. best wishes to all; -Edward r Jones // Tambura-with-sporking.ck // // Tambura with Sporking // // by Edward r Jones (loscha(a)gmail.com) // // This is my emulation of an electronic tambura device. // By Tambura, I mean the Indian classical instrument. // A Tambura has 4 to 6 strings, which are plucked in a repeating pattern to accompany Indian classical music // It has a resonating cavity, and resonant sympathetic strings, like a Sitar, but, no frets. // Please Help! This Model Needs! // // = Sympathetic Strings. I've tried setting up a series of 8 delay lines // tuned to the resonant frequencies I desire), but, they didn't give me the results I wanted at all. // I am new to coding Physical Modelling, and if anyone has some advice on this matter I'd love to hear from you. // // A Resonant Cavity. // I've goen with using LPF and HPF to limit the output frequency range to give the sort of timbre I want, but, // I know that this could be better acheived. // // At the moment, it sounds more like a Koto. // I found the stk Sitar instrument to sound nothing like a Sitar or a Tambura, // Buuut, this is because of the reasons I listed above -- Sympathetic Strings & real Resonant Cavity. // // In closing, I want to thank: // The ChucK community, I love this language (and you all!) so much, // and I hope to be able to contribute to it's development in the future // My wonderful partner, Michelle, who doesn't mind me staying up until 3am working on this stuff! // All my local friends in synthesis; Bill Harrison aka James Earthenware, Paul Perry, Robin Whittle & Jaymz // \=> Clae, All the Melbourne Dorkbot community, and all the other hardcore synthesists in Melbourne, Victoria, Australia! // All my online friends, Matrixsynth, Sealed, SynthDiy and all my LiveJournal Buddies. // The Founding Fathers of this craft that I love so much. John Chowning, Max V Matthews, Steve Reich, Paul Lansky & Stockhausen, // // Enuff! On to the Code! [ 1, 0, 0, 1, 1, 0] @=> int beats[]; // 1 means play, 0 means skip [ 00, 00, 00, 12, 09, 04] @=> int notes[]; // Note pitch, relative to noteoffset 30 => int noteoffset; // this is the transpose, to make scales easier float variance[beats.cap()]; // this is for randomization of string pitches to achieve "thickness" // They are calculated once at startup, to simulate real string tuning .05 => float waver; // range for variance in NOTES 72 => float tempo; float click; 30000 / tempo => click; <<<"Click length", click,"">>>; int numsteps; beats.cap() => numsteps; LPF lpf; HPF hpf; JCRev jcrev; 2550 => lpf.freq; 300 => hpf.freq; .05 => jcrev.mix; StifKarp tambura[numsteps]; lpf => hpf => jcrev => dac; //------- Hook up all tamburas to the chain & set them up the way we want them. // .pickupPosition - ( float , READ/WRITE ) - pickup position [ 0.0 - 1.0] // .sustain - ( float , READ/WRITE ) - string sustain [0.0 - 1.0] // .stretch - ( float , READ/WRITE ) - string stretch [0.0 - 1.0] // .pluck - ( float , WRITE only ) - pluck string [0.0 - 1.0] // .baseLoopGain - ( float , READ/WRITE ) - ?? [0.0 - 1.0] // .clear - ( ) - reset instrument for (0 => int stab; stab < numsteps; stab++) { tambura[stab] => lpf; .03 => tambura[stab].pickupPosition; 1 => tambura[stab].sustain; 1 => tambura[stab].stretch; .99 => tambura[stab].baseLoopGain; Std.rand2f(1-waver, waver) => variance[stab]; <<<"tambura #",stab,"hooked up","">>>; } //------ Hookups done. <<<"pre-comparison","">>>; if (beats.cap() == notes.cap()) { <<<"Steps in our sequence", numsteps,"">>>; //------------------------------------ The Sequence Plays! ---------------------- while (true) { for (0 => int stab; stab < numsteps; stab++) { if (beats[stab] == 1) { <<<"Stab",stab,"">>>; tampluck (stab); } click * 1::ms => now; } } //------------------------------------ The Sequence (never) Ends! ---------------------- <<<"End of Playing!","">>>; } //------------------------------------------------------------------------ // Error, stop the program else { <<<"ERROR IN SEQUENCER DATA", "";>>>; <<<"Item count mismatch","">>>; } //------------------------------------------------------------------------- // This is the sporkage for our note playing. fun void tampluck (int step) { float npitch; variance[step] + noteoffset + notes[step] => Std.mtof => npitch; npitch => tambura[step].freq; <<<"Pitch",npitch,"">>>; 1 => tambura[step].pluck; } -- www.loscha.com/chuck

2 1

Re: [chuck-users] De-Lurk Pt II. I forgot my spork!
by Loscha 11 May '07

11 May '07

I feel like a bit of a fool after that posting. I forgot to put back the "spork ~" in the section of code I was working on. Please revise code as follows: Should have posted link to code stored as a ck on my server, I could have fixed it in a jiffy, and saved y'all have to cut and paste it to get it working. sorry for the chatter. -Edward //------------------------------------ The Sequence Plays! ---------------------- while (true) { for (0 => int stab; stab < numsteps; stab++) { if (beats[stab] == 1) { <<<"Stab",stab,"">>>; spork ~ tampluck (stab); // <= this is the updated line! } click * 1::ms => now; } } //------------------------------------ The Sequence (never) Ends! ----------------------

2 1

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