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

User Action Capturing
by jason burnside 07 Dec '06

07 Dec '06

Hey Ge, Let's say I'm using a program like joy-noise.ck (under chuck/examples/hid), and I want to capture the input from the controller for later use, or looping, or whatever. Is there a way to do this in Chuck? If not, can Chuck write control data (midi note integers, joystick positions, etc.) to a .txt file, then read from the file later? Also, I went to your seminar at Tulane. It was very good. Thanks, Steve --------------------------------- Want to start your own business? Learn how on Yahoo! Small Business.

2 1

SndBuf functions - valueAt ??
by Laurie Hollander 04 Dec '06

04 Dec '06

I see the following functions in the Chuck manual, for SndBuf: .read - (string, WRITE only) - loads file for reading .chunks - (int, READ/WRITE) - size of chunk (# of frames) to read on-demand; 0 implies entire file, default; must be set before reading to take effect. .write - (string, WRITE only) - loads a file for writing (or not) .pos - (int, READ/WRITE) - set position (0 <p <.samples) .valueAt - (int, READ only) - returns the value at sample index .loop - (int, READ/WRITE) - toggle looping .interp - (int, READ/WRITE) - set interpolation (0=drop, 1=linear, 2=sinc) .rate - (float, READ/WRITE) - playback rate (relative to the file's natural speed) .play - (float, READ/WRITE) - play (same as rate) .freq - (float, READ/WRITE) - playback rate (file loops/second) .phase - (float, READ/WRITE) - set phase position (0-1) .channel - (int, READ/WRITE) - select channel (0 <x <.channels) .phaseOffset - (float, READ/WRITE) - set a phase offset .samples - (int, READ only) - fetch number of samples .length - (float, READ only) - fetch length in seconds .channels - (int, READ only) - fetch number of channels I am now trying to use the .valueAt function, but am getting errors. The program is something like.... SndBuf a ; ...etc I read a soundfile into sndbuf a and play it - that much works.... int samp_pos ; float samp_val ; for (0 => int j ; j < 10000 ; j++) { j => a.pos ; j => samp_pos ; a.valueAt() => samp_val ; // <<<a.pos() >>> ; // <<< samp_pos, samp_val >>> ; } Here's the error message: [trigplay2calc.ck]:line(151): arguments type(s) do not match: [trigplay2calc.ck]:line(151): ... for function 'SndBuf.valueAt(...)' ... [trigplay2calc.ck]:line(151): ...(please check the argument types) When I change the type of samp_val to int, I get the same message. When I leave out the parentheses, it complains that it's a function. Does the .valueAt function work? Thank you! -Laurie

3 2

figuring out what causes a crash
by Atte André Jensen 02 Dec '06

02 Dec '06

Hi While playing with my setup tonight chuck crashed (seg fault) on me a couple of times, and I'm very interested in finding out why. Instead of crawling through my 18000+ lines of chuck code I'd like chuck to be a little more outspoken when it crashes. Now it just gives me the line where I call chuck from a bash startup script. I tried the verbose setting, and although I haven't made it crash yet, I don't really need all the debugging info when running, so I suspect I'm looking for something slightly different. Is there anything I can do (a hack in the source, a switch I should try, any suggestions) to investigate a bit further? BTW: I'm pretty sure it's my code and not chuck that's to blame, although one must never say never:-) -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

2 1

miniAudicle problems
by Atte André Jensen 01 Dec '06

01 Dec '06

Hi Just installed miniAudicle 0.1.3.6 (and the included chuck) on my debian/unstable laptop. Something seems wrong with miniAudicle, since some examples (just tried a few under basic) make no sound. Here's what I tried that makes sound in both chuck and miniAudicle: fm2, fm3, curly++ And the following only make sound in chuck: blit, moe, moe++, chirp, chirp2, larry, larry++ However the ones actually sounding in miniAudicle, only sound in one channel (left)... Both miniAudicle and chuck are compiled using make linux-alsa. Any idea what could be the cause of this? Did I miss something? -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/composition

4 22

examples/hid/kb.ck
by Atte André Jensen 01 Dec '06

01 Dec '06

Hi I wanted to check out the hid interface, but: atte@ajstrup:~/music/chuck/examples/hid$ chuck kb.ck [chuck]: HidIn: couldn't open HID device 3:0... What am I doing wrong? This is under linux... I don't know if it's relevant, but heres what "chuck --probe" has to say: atte@ajstrup:~/music/chuck/examples/hid$ chuck --probe [chuck]: found 6 device(s) ... [chuck]: ------( chuck -- dac1 )--------------- [chuck]: device name = "hw:I82801DBICH4,0" [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]: 16-bit int [chuck]: 32-bit int [chuck]: supported sample rates: [chuck]: 8000 Hz [chuck]: 9600 Hz [chuck]: 11025 Hz [chuck]: 16000 Hz [chuck]: 22050 Hz [chuck]: 32000 Hz [chuck]: 44100 Hz [chuck]: 48000 Hz [chuck]: [chuck]: ------( chuck -- dac2 )--------------- [chuck]: device name = "hw:I82801DBICH4,1" [chuck]: probe [success] ... [chuck]: # output channels = 0 [chuck]: # input channels = 2 [chuck]: # duplex Channels = 0 [chuck]: default device = NO [chuck]: natively supported data formats: [chuck]: 16-bit int [chuck]: supported sample rates: [chuck]: 48000 Hz [chuck]: [chuck]: ------( chuck -- dac3 )--------------- [chuck]: device name = "hw:I82801DBICH4,2" [chuck]: probe [success] ... [chuck]: # output channels = 0 [chuck]: # input channels = 2 [chuck]: # duplex Channels = 0 [chuck]: default device = NO [chuck]: natively supported data formats: [chuck]: 16-bit int [chuck]: supported sample rates: [chuck]: 48000 Hz [chuck]: [chuck]: ------( chuck -- dac4 )--------------- [chuck]: device name = "hw:I82801DBICH4,3" [chuck]: probe [success] ... [chuck]: # output channels = 0 [chuck]: # input channels = 2 [chuck]: # duplex Channels = 0 [chuck]: default device = NO [chuck]: natively supported data formats: [chuck]: 16-bit int [chuck]: supported sample rates: [chuck]: 48000 Hz [chuck]: [chuck]: ------( chuck -- dac5 )--------------- [chuck]: device name = "hw:I82801DBICH4,4" [chuck]: probe [success] ... [chuck]: # output channels = 2 [chuck]: # input channels = 0 [chuck]: # duplex Channels = 0 [chuck]: default device = NO [chuck]: natively supported data formats: [chuck]: 16-bit int [chuck]: supported sample rates: [chuck]: 48000 Hz [chuck]: [chuck]: ------( chuck -- dac6 )--------------- [chuck]: device name = "hw:Modem,0" [chuck]: probe [success] ... [chuck]: # output channels = 1 [chuck]: # input channels = 1 [chuck]: # duplex Channels = 1 [chuck]: default device = NO [chuck]: natively supported data formats: [chuck]: 16-bit int [chuck]: supported sample rates: [chuck]: 8000 Hz [chuck]: 9600 Hz [chuck]: 16000 Hz [chuck]: [chuck]: ------( chuck -- 1 MIDI inputs )------ [chuck]: [0] : "Midi Through Port-0" [chuck]: [chuck]: ------( chuck -- 1 MIDI outputs )----- [chuck]: [0] : "Midi Through Port-0" [chuck]: -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

3 8

control envelopes
by Atte André Jensen 01 Dec '06

01 Dec '06

Hi I played a bit with the new LPF ugen. Thanks alot for adding this, it's really, really great! Working with this made me think about how to control a filter over time. Supposed I want a really simple, classic sound of a SawOsc ran through a LPF controlled by a (dare I say it) envelope. I have an instrument like this: fun static void moog_bass(float note, float dynamic, dur length){ Event off; spork ~ moog_bass(note, dynamic, off); length => now; off.broadcast(); .2::second => now; } fun static void moog_bass(float note, float dynamic, Event off){ .13 => float volume; //0 => volume; SawOsc osc => LPF f => dac; Std.mtof(note) => osc.freq; 1 => f.Q; 400 => f.freq; Mixer.bass * volume => f.gain; while(f.freq() > 80){ f.freq() * .9 => f.freq; 10::ms => now; } off => now; while(f.gain() > .000001){ f.gain() * .99 => f.gain; .1::ms => now; } } This instrument works with both midi (where we don't know the length before noteoff) and from code (where I prefer to use a length). Only problem is that if the length is too short, the off-event is broadcast before the first while is finished. This means that the off-event is never received, which in turn makes the instrument click. Any ideas how to solve this? I still find myself wishing for ADSR's to be able to control stuff, but that won't happen, right? Another related situation: Supposed I want to modulate both panning, volume and filter by different predetermined "curves"s. I can't get my head around how that is done nicely. A multi breakpoint envelope that could controll stuff (like csounds expseg and linseg) would be really great in some situations, since they are so easy to setup and experiment with the different timings/levels. But how could something like this be solved with chuck? -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

2 2