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

JACK Transport
by Esben Stien 05 Jan '07

05 Jan '07

Any attempt made at supporting JACK Transport? -- Esben Stien is b0ef@e s a http://www. s t n m irc://irc. b - i . e/%23contact sip:b0ef@ e e jid:b0ef@ n n

2 2

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

spice up your code
by Kassen 30 Nov '06

30 Nov '06

Hi, list, I'm a bit tirered of having to type "while(true)....." all the time. "true" as a concept may be dependable but it's purity makes it rather one-sided and boring. Back when I was taking language philosophy clases I was tought that any fact about the world we know to be true equates to the abstract platonic concept of truth (I'm not debating here and now wether that's true or wether I thought it made much sense). Sadly in chuck this only works for a select set of facts about the world which might be due to ChucK's youth and inexperience with the world. At least this one works; While (float rubber_ducky) { //loop goes here } ;-) Yours, Kas.

1 0

realtime priorities
by Atte André Jensen 29 Nov '06

29 Nov '06

Hi Is it correct that it isn't possible to run chuck/linux with realtime priority? When I start zynaddsubfx I see (in htop) one line with priority -51 and one with priority 15. Chuck I see two, one with priority 15 and one with priority 16. Renicing chuck to -19 or so helps alot, but still... If this is not currently possible, would it be a major request to implement? -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

1 0

is some_id runnig?
by Atte André Jensen 28 Nov '06

28 Nov '06

Hi Is it possible to ask (from within chuck) whether a given id is running, that is present in the VM? -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

3 5

function call syntax(bug?).
by Kassen 28 Nov '06

28 Nov '06

Hi, list! Let's asume we have this function; //---- fun void greeting() { <<<"hey, ChucKer!">>>; } //----- clearly we would call it like this; greeting(); and all would be well. However, if we asume we would be a fairly chaotic sort of person who would make a large amount of typos, especially at 4 in the morning while trusting the parser will catch them for him faster then proofreading will (this is purely hypothetical). In this case it could theoretically happen that one would by accident type; greeting; This compiles just fine and nothing is wrong except for ChucK not running the function. The question now is; should ChucK complain about such function calls? Is there some unforseen practical use in calling no-parameter functions without empty brackets? Yours, Kas.

1 0

removing shreds by name from within chuck
by Atte André Jensen 28 Nov '06

28 Nov '06

Hi I'm trying to write a little something that'll load/unload files from within chuck. I've assigned different filenames to each of the keys a-z and now when a key is pressed I want to: if(file_is_running(filename)){ machine.remove(filename2id(filename)); } else { machine.add(filename); } So basically: how do I figure out if a shred is running with a certain filename and how do I get the id? To be clear: This information is available in the terminal if I kick chuck with "chuck ^", but I want to access this information inside chuck... -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

3 6

file operations etc.
by Atte André Jensen 28 Nov '06

28 Nov '06

Hi again Are there any plans to include stuff like reading/writing text to files, saving/loading objects (ala tickle in python), navigating paths, getting directory contents and regular string operations like replacement, search? Actually, I'm thinking that if I need alot of stuff like this, maybe I should better make myself a python wrapper... OTOH it would be nice to have everything in pure chuck. Actually that's one of the reasons I tried out chuck in the first place (comming from years of csounding); that it's more like "a real" language... Any thoughts? -- peace, love & harmony Atte http://www.atte.dk | quintet: http://www.anagrammer.dk | compositions: http://www.atte.dk/compositions

2 4