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

(casting) in chuck?
by Jochen Hartmann 02 Sep '07

02 Sep '07

Hi, I am total newbie to chucK. been trying to make time to play with it more ever since last year but somehow that time didnt arrive until now. So for today's silly question I was wondering if there is some kind of implicit casting of objects in chuck? For instance I want to fill an array with specific UGens and then randomly retrieve one like so: //array of UGens UGen items[2]; SinOsc sin @=> items[0]; SawOsc saw @=> items[1]; //later in my loop Std.rand(0,1) => int item; items[item] @=> UGen mysteryOscillator; mysteryOscillator => dac; Obviously this is not working right now and I am wondering if I am doing something wrong syntactically or whether I am trying to do something that ChucK can't do. thanks for the help ! best - j

3 2

Re: [chuck-users] priorities for next release
by Adam Tindale 01 Sep '07

01 Sep '07

> > >Yes, we would all like this, I think. At least we have a WiKi page where >everybody can post additions, remarks and requests which should at least >decrease the strain on maintaining the manual. I believe Adam Tindale was >the last to be semi-officially in charge of the manual but other things >took his time. I'd volunteer but I'd need a proofreader as I'm not a native >English speaker and I still don't speak any Latex at all (the manual is >done in Latex) > >At least most things can be found by searching the list archives and the >manual isn't *that* out of date. Aside from the latest greatest stuff this >matter might be one of the worst missing bits. > > Hi All, I have been silent for a long while. I am always happy to proofread and hack stuff into the manual and make the commits (as long as Ge doesn't kick me off CVS). Like Ge, I just got a teaching gig and I am a bit swamped being new at all this. I have pleaded in the past for other people to submit tutorials or find mistakes in the manual and pass them on to me and the whole ChucK team. It now seems that there are so many experts that this dream is coming true. Most of what I did for the manual was to edit the original APIs into some semi readable form. A lot of that work was done by Ge and Phil and I just merely put it into LaTeX. There have been many people talking on the list about knowing how something works and not seeing it in the manual. If you do know and it isn't there, just write something up and tell me where you would like it be. The hardest part for me is starting something. If you get it started then the rest isn't so bad. I haven't worked on the manual in a long time and I am seeing that it is badly out of date. I will do my best to devote some time to it in the coming months (I am hoping to teach ChucK, so a good manual helps me too). If you have something you would like added to the official docs please send it along to me directly or via the list and I will be happy to add it. --art _________________________________________________________________ Former Police Officer Paul Gillespies TAKE BACK THE INTERNET tips and tricks, watch the video now http://safety.sympatico.msn.ca/

6 7

priorities for next release
by Ge Wang 31 Aug '07

31 Aug '07

Greetings! We are nearing the next very sporktacular release of ChucK and want to coordinate with you on organizing and prioritizing some bug fixes/ features/updates. We've been scouring through the forums, wiki pages, and posts and collected much good info. Thanks to all who have been kind and patient enough to enter requests, reports, and suggestions into the various pages. At this stage, we'd like to get your input on prioritizing them for the new release (in about 2 weeks). For this purpose, we've created two new wiki pages for feature requests/reports and bug reports/requests from here: http://wiki.cs.princeton.edu/index.php/ChucK/Bugs http://wiki.cs.princeton.edu/index.php/ChucK/Features Please enter full descriptions and concise accompanying code when helpful. While we can't guarantee that these would make it into the immediate next version, they are very helpful in getting a sense of disaster zones that needs more urgent attention, and is a chance to tidy up the information. If you don't want to deal with the wiki directly, feel free to post here or to chuck-dev, and our uh wiki specialists will transfer the text there. As for the manual, let's keep going here: http://wiki.cs.princeton.edu/index.php/ChucK/Manual Thank you very much! Let us know if you have any questions. Keep on ChucKin' Best, chuck team

11 22

chuck on linux-amd64?
by Robert Edge 28 Aug '07

28 Aug '07

I miss chuck. I was starting to get in to playing with last year, but I have since decided to go with a pure 64 bit system. I've got everything tuned and working the way I want now, but no chuck. I build every release I notice come out but still things do not work on Linux-amd64. What is the status of chuck and this architecture? I seem to remember talk of the issue being looked in to some time ago. Also, for what it's worth somebody is keeping a broken build in the Debian repositories, I've sent a bug report but no one seems to care. I think it's a shame that someone could get the wrong impression about this wonderful project.

1 0

heads up; follow up; up chuck
by Ge Wang 28 Aug '07

28 Aug '07

Greetings! As announced on the [chuck] list, we've just released a new major version (1.2.1.0) of chuck that introduces audio analysis in ChucK. For more details see: http://chuck.cs.princeton.edu/uana/ The paper: http://soundlab.cs.princeton.edu/publications/uana_icmc2007.pdf Just want to thank everyone for the recent discussion and also re- prioritizing of features. We are by no means done, and many new features outlined are underway. So please continue! We are hoping for several new releases in the coming weeks/months. Thanks again! Alrighty, go check out UAna, upchuck, and the new release! Let us know how it goes (or crashes)!! Best, chuck team

4 6

rec2.ck
by 2g 28 Aug '07

28 Aug '07

in another japanese chuck community i asked if somebody knows about "rec2.ck" which i cannot find in the examples dir and at last a person gave me the sample he found mm? this one seems to create 2 files instead of one stereo at this moment we cannot write stereo things to HDD? then i have to use sox to combine these maybe...? rec2.ck (not the original?): dac.left => WvOut wL => blackhole; dac.right => WvOut wR => blackhole; 4::second => dur l; now + l => time later; "./wavs/rec2L.wav" => wL.wavFilename; "./wavs/rec2R.wav" => wR.wavFilename; <<<"writing to file: ", wL.filename()>>>; <<<"writing to file: ", wR.filename()>>>; while ( now < later ) 500::ms => now; wL.filename() => wL.closeFile; wR.filename() => wR.closeFile; <<< "rec2 done." >>>; -- 2g http://micro.ispretty.com

3 7

list oriented ways to make this more simple?
by 2g 28 Aug '07

28 Aug '07

mmm...i seem to be writing same things too much can't any of these done in list[] oriented ways? sa.ck: SinOsc sun1 => Pan2 ps1 => dac; SinOsc sun2 => Pan2 ps2 => dac; SinOsc sun3 => Pan2 ps3 => dac; SinOsc sun4 => Pan2 ps4 => dac; SinOsc sun5 => Pan2 ps5 => dac; SinOsc moon1 => Pan2 pm1 => dac; SinOsc moon2 => Pan2 pm2 => dac; SinOsc moon3 => Pan2 pm3 => dac; SinOsc moon4 => Pan2 pm4 => dac; SinOsc moon5 => Pan2 pm5 => dac; .1 => ps1.gain; .1 => ps2.gain; .1 => ps3.gain; .1 => ps4.gain; .1 => ps5.gain; .1 => pm1.gain; .1 => pm2.gain; .1 => pm3.gain; .1 => pm4.gain; .1 => pm5.gain; 27.5 * Math.pow(2.0,(3.0/12.0)) => float oilsun; 27.5 * Math.pow(2.0,(5.0/12.0)) * 7.0/8.0 => float oilmoon; oilsun * Std.rand2(16,8) / 8.0 => sun1.freq; oilsun * Std.rand2(16,8) / 4.0 => sun2.freq; oilsun * Std.rand2(16,8) / 4.0 => sun3.freq; oilsun * Std.rand2(16,8) / 4.0 => sun4.freq; oilsun * Std.rand2(16,8) / 4.0 => sun5.freq; oilmoon * Std.rand2(16,8) / 8.0 => moon1.freq; oilmoon * Std.rand2(16,8) / 4.0 => moon2.freq; oilmoon * Std.rand2(16,8) / 4.0 => moon3.freq; oilmoon * Std.rand2(16,8) / 4.0 => moon4.freq; oilmoon * Std.rand2(16,8) / 4.0 => moon5.freq; fun void ga() { while(true) { 900::ms => now; Std.rand2f(-1.0,1.0) => pm1.pan; oilmoon * Std.rand2(16,8) / 8.0 => moon1.freq; Std.rand2f(-1.0,1.0) => pm2.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => moon2.freq; Std.rand2f(-1.0,1.0) => pm3.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => moon3.freq; Std.rand2f(-1.0,1.0) => pm4.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => moon4.freq; Std.rand2f(-1.0,1.0) => pm5.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => moon5.freq; 900::ms => now; Std.rand2f(-1.0,1.0) => pm1.pan; oilmoon * Std.rand2(32,16) / 8.0 => moon1.freq; Std.rand2f(-1.0,1.0) => pm2.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => moon2.freq; Std.rand2f(-1.0,1.0) => pm3.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => moon3.freq; Std.rand2f(-1.0,1.0) => pm4.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => moon4.freq; Std.rand2f(-1.0,1.0) => pm5.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => moon5.freq; } } fun void ma() { while(true) { 7500::ms => now; Std.rand2f(45.0,75.0) => oilsun; Std.rand2f(45.0,75.0) => oilmoon; } } fun void pa() { while(true) { 700::ms => now; Std.rand2f(-1.0,1.0) => ps1.pan; oilsun * Std.rand2(16,8) / 8.0 => sun1.freq; Std.rand2f(-1.0,1.0) => ps2.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => sun2.freq; Std.rand2f(-1.0,1.0) => ps3.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => sun3.freq; Std.rand2f(-1.0,1.0) => ps4.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => sun4.freq; Std.rand2f(-1.0,1.0) => ps5.pan; sun1.freq() * Std.rand2(16,8) / 4.0 => sun5.freq; 700::ms => now; Std.rand2f(-1.0,1.0) => ps1.pan; oilsun * Std.rand2(16,8) / 8.0 => sun1.freq; Std.rand2f(-1.0,1.0) => ps2.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => sun2.freq; Std.rand2f(-1.0,1.0) => ps3.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => sun3.freq; Std.rand2f(-1.0,1.0) => ps4.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => sun4.freq; Std.rand2f(-1.0,1.0) => ps5.pan; moon1.freq() * Std.rand2(16,8) / 4.0 => sun5.freq; } } spork ~ ga(); spork ~ ma(); spork ~ pa(); while( true ) { 3333::ms => now; } -- 2g http://micro.ispretty.com

2 2

what is this stk control change thing?
by Fitzpatrick, Denis F 25 Aug '07

25 Aug '07

My confusion is deep and multifaceted, but just to get started, I gather it's a way of setting various instrument parameters, but how does it differ from like-named (where they exist) method calls? I made a Googley effort to find this explained, but failed. I would gladly accept an answer in the form of a link. Denis Fitzpatrick Boys Town National Research Hospital (402) 498-6378 fitzpatrickd(a)boystown.org

2 1

TiltSensor on linux
by Cédric Krier 25 Aug '07

25 Aug '07

Hi, here is the patch updated (for chuck 1.2.1.0) for tiltsensor on linux. The driver for the sensor is now in the kernel version 2.6.22. I hope it will be add in the next release. Thanks

3 4

CurveTable strange behaviour
by eduard 23 Aug '07

23 Aug '07

The following patch shows either a misbehaviour or a misuse of CurveTable, dunno. Two different functions (rand_coefs1 and rand_coefs2) are used to assign coefficients to CurveTable.coefs(). While the first seems to do the job alright, the latter doesn't and throws the following error message: [chuck](via CurveTable): usage: size, time1, value1, curvature1, [ timeN-1, valueN-1, curvatureN-1, ] timeN, valueN) Maybe I'm doing something wrong that | don't see, but can't understand why this happens. Could anyone explain? Also, don't understand why the error message tells me the size needs to be supplied. The examples say that coefs are arrays of the type [time1, value1, curvature1, ..., timeN-1, valueN-1, curvatureN-1, timeN, valueN] and Gen's size, if I'm not mistaken, is hard coded as 4096. Thanks in advance, eduard The patch: fun void rand_coefs1( CurveTable table ) { [-1, 0, 1 ] @=> int curvature[]; [0., 0., curvature[ Std.rand2(0, 2)], 1, Std.rand2f(.5,1.), curvature[ Std.rand2(0, 2)], 2, Std.rand2f(.5,1.), curvature[ Std.rand2(0, 2)], 3, Std.rand2f(0.,1.), curvature[ Std.rand2(0, 2)], 4, Std.rand2f(0.,1.), curvature[ Std.rand2(0, 2)], 5, Std.rand2f(0.,1.), curvature[ Std.rand2(0, 2)], 6, Std.rand2f(0.,1.), curvature[ Std.rand2(0, 2)], 7, Std.rand2f(0.,1.), curvature[ Std.rand2(0, 2)], 8, Std.rand2f(0.,1.), curvature[ Std.rand2(0, 2)], 9, 0] @=> float coefs[]; coefs => table.coefs; <<<"\n", "CURVE 1:\n" >>>; <<<"\t index", " value", " curvature">>>; <<<"\t----------------------------------","\t">>>; for( 0 => int i; i < 8; i++ ) <<<"\t",coefs[i++], coefs[i++], coefs[i]>>>; <<<"\t", coefs[8], coefs[9] >>>; <<<"\t----------------------------------","\t">>>; } fun void rand_coefs2( CurveTable table, int n_breakpoints ) { // this function does not assign values stored in coefs correctly to // CurveTable.coefs(). Why? It also throws an error message. [-1, 0, 1 ] @=> int curvature[]; n_breakpoints*3 - 1 => n_breakpoints; float coefs[ n_breakpoints]; 0. => coefs[0]; 0. => coefs[1]; for( 2 => int i; i < n_breakpoints; i++ ) { curvature[ Std.rand2(0, 2)] => coefs[i++]; i/3 => coefs[i++]; Std.rand2f(0.,1.) => coefs[i]; } 0 => coefs[n_breakpoints-1]; coefs => table.coefs; <<<"\n", "CURVE 2:\n" >>>; <<<"\t index", " value", " curvature">>>; <<<"\t----------------------------------","\t">>>; for( 0 => int i; i < n_breakpoints-2; i++ ) <<<"\t", coefs[i++], coefs[i++], coefs[i]>>>; <<< "\t", coefs[n_breakpoints-2], coefs[n_breakpoints-1] >>>; <<<"\t----------------------------------","\t">>>; } CurveTable curve1; CurveTable curve2; 1024 => int size; <<< "\n*Assigning coefs via rand_coefs1()","\t">>>; rand_coefs1( curve1 ); 0 => float sum; for( 0 => int i; i < size; i++ ) { curve1.lookup(i) +=> sum; } if( sum > 0 ) <<<"Ok", "sum[i=0,N=1023] =", sum>>>; else <<< "Error:", "sum[i=0,N=1023] =", sum, ". Coefs were not assigned. All values are 0." >>>; <<< "\n*Assigning coefs via rand_coefs2()","\t">>>; rand_coefs2( curve2, 10 ); 0 => sum; for( 0 => int i; i < size; i++ ) { curve2.lookup(i) +=> sum; } if( sum > 0 ) <<<"Ok", "sum[i=0,N=1023] =", sum>>>; else <<< "Error:", "sum[i=0,N=1023] =", sum, ". Coefs were not assigned. All values are 0.\n">>>;

2 1