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

questions about the Bowed UGen
by Daniel Chapiro 12 Oct '14

12 Oct '14

Hi - I am using the Bowed UGen, and after reading the docs, trying to hear what's going on, and looking at Chuck's src, I still have some questions: (1) rate: Chuck complains that the rate method is not valid for Bowed. However, it's mentioned in some docs, and the source code has an ADSR inside, whose rate is set by noteOn/Off (but not by start/stopBowing). Also, this ADSR has reasonable decay and sustain values, but they are fixed. Is there any way to at least set the rate from Chuck code? (2) volume: it is a multiplicative factor, completely independently of whatever amplitude one sets with start/stopBowing set, right? (3) start/stopBowing: does the model have a transient, during which the string is vibrating with a different spectrum than in steady state? If not, to control the attack/decay, should I leave it bowing constantly, and control the attack/decay by adding an ADSR after Bowed, which would "gate" the sound? (4) in STK there's an asymptotic decay - is there anything like that in Chuck? (sometimes one may want a dampened, quick stop, but others one may want to let the string decay asymptotically, just as with plucked strings, regardless of having enertgized the string with a bow). Thanks! Daniel

1 1

Forgetting parenthesis in function calls yields no error
by Stefan Blixt 10 Oct '14

10 Oct '14

Hello list! I just spent a little time scratching my head over these little functions: fun void startRecording() { <<< "Record! ", index >>>; true => lisaLeft.record; true => lisaRight.record; } fun void toggle() { !active => active; paintActive(); if (active) { startRecording; } } Everything seemed to be in order, I added a lot of print statements, and could for the life of me figure out why the startRecording function wasn't executed from toggle(). There was no error message, everything seemed to be in order. Then I peered more closely and saw that I had forgotten to put parenthesis in the function call: startRecording(); After that everything started working. My question is: shouldn't a function name all by itself result in an error of some kind? Cheers, Stefan Blixt -- Release me, insect, or I will destroy the Cosmos!

4 3

Really basic question
by Philipp Blume 18 Sep '14

18 Sep '14

I'd like to call a .ck program from the Mac OSX Terminal command line, and feed values to variables in the given program. For example, here's my program 'fooprint.ck': =begin program <<< foo >>> ; =end program So on the command line I'd like to write &> chuck fooprint.ck --foo=25 or whatever. What do I add to the program, and/or what do I add to the command to make this happen? -- Philipp Blume

2 1

. Re: Chuck's capture of Midi broken? (Daniel Chapiro)
by Perry Cook 15 Sep '14

15 Sep '14

Could we be looking at a running status problem? It's legal in MIDI to skip the status byte if it doesn't change. Not sure how ChucK/RTMidi handle this. I sold my WX7, or I'd check it. Prc

2 1

Chuck's capture of Midi broken?
by Daniel Chapiro 15 Sep '14

15 Sep '14

Hi - I think that Chuck's Midi methods seem not to be working (except for very simple examples), as Chuck is dropping Midi events - I'm using the pre-compiled version of Chuck 1.3.0 (gidora), on a Mac Mini (2.7GHz I7), with OSX 10.7.5 (Lion). The only type of ON/OFF sequence in which Chuck seems not to "swallow" any notes is of the form Note1 ON, Note1 OFF, Note2 ON, Note2 OFF… Instead, I'm generating Midi streams in which there are new note On events before the prior note goes off. They happen when I play legato with a Yamaha WX5 wind controller, but any Midi keyboard would also generate such sequences if one presses a new key before releasing another one that is already sounding. I captured the following short sequence with the "MIDI Monitor" app (http://www.snoize.com/MIDIMonitor/). Also it sounds fine with different sound generators): 20:34:33.026 From In Note On 1 E2 22 20:34:33.030 From In Control 1 Breath Control (coarse) 20 20:34:33.036 From In Control 1 Breath Control (coarse) 25 20:34:33.041 From In Control 1 Breath Control (coarse) 27 20:34:33.071 From In Control 1 Breath Control (coarse) 29 20:34:33.182 From In Control 1 Breath Control (coarse) 30 20:34:33.207 From In Note On 1 F2 30 20:34:33.208 From In Note Off 1 E2 0 20:34:33.534 From In Note On 1 G2 30 20:34:33.535 From In Note Off 1 F2 0 20:34:33.664 From In Control 1 Breath Control (coarse) 32 20:34:33.845 From In Note On 1 A2 32 20:34:33.846 From In Note Off 1 G2 0 Capturing the same with Chuck only shows the 1st Note ON (and all the CCs, which are correct), but the rest of the Note ONs/OFFs vanish (BTW, playing very slowly makes no difference). To make sure it was not some bug in my code, I captured the Midi using just Chuck's example in miniAudicle->File->Open Example->MIDI->gomidi (the numeric output is converted below, just for readability): Note On E2 22 CC BC (msb) 20 CC BC (msb) 25 CC BC (msb) 27 CC BC (msb) 29 CC BC (msb) 30 CC BC (msb) 32 Only by fully ending each note before playing the succeeding one, all the Note ONs/OFFs show up. But that's not useable... Any help on incantations for Chuck, workarounds, or a fix would be great! (particularly since after learning to ChucK from Rob Poor's Oxygen8, the rest of my ChucK code seems to be working nicely :-) Thanks! Daniel

3 7

Chuck on windows7 64-bit - OTF and OSC not working
by Rich Caloggero 12 Sep '14

12 Sep '14

I'm using latest chuck 1.3.4.0 on windows7 64-bit. I can’t seem to get chuck to deal with the network at all. * -- probe crashes chuck; * any otf command like + crashes chuck; * chuck –loop seems to work, but subsequent otf commands like + cause a crash, even when specifying host and port explicitly The looped process crashes with the windows error (unexpected error – program needs to close)... The chuck + command reports “remote operation timed out”. I’ve tried with various combinations of --remote and --port in the "chuck +" command and combinations of --port and --loop and --server in the initial process. I also happen to be blind, so the miniaudical doesn't work for me at all! THe --probe command crashes chuck so its difficult to get an error report, but windows just says that a critical error has occured and the program needs to close; no other info is given. I've not been able to find any info on similar crashes online.

2 2

GUI builders?
by Peter Lutek 11 Sep '14

11 Sep '14

greetings... it's good to be back in touch with the ChucK community! i'm re-examining ChucK after a number of years since i experimented a little bit with it, as a possible alternative platform for a live performance instrument which has been implemented in pd until now. so far, i have one question which i don't see addressed directly in the various docs: is there some facility, native to ChucK, for building any GUI elements for use during performance?... things like sliders, knobs, and toggles, for both input (from keyboard or mouse) and to display values incoming from various MIDI controllers. i guess a front-end could be built in pd, but that just seems silly. somehow, i'm beginning to suspect that such a visual front-end might be a little outside the "ChucK paradigm"?! please let me know if you guys have some good approaches to this kind of thing! thanks... cheers! .pltk. -- Peter Lutek improvising musician in Toronto, Canada http://peterlutek.com

5 10

Console font size
by Daniel Chapiro 04 Sep '14

04 Sep '14

Hi - is there a way to change the font size that ChucK uses for the console window? (I'm using size 14 for the ChucK source windows, but I can barely read the ~11 fonts of the console…). Thanks! --Daniel

1 0

trouble with --probe again on osx
by Michael Heuer 01 Sep '14

01 Sep '14

Hello, I'm having trouble with ChucK being able to locate my Apogee ONE USB device again $ chuck --probe ... Message response timed out [chuck]: system error: (kAudioHardwareUnspecifiedError) getting device manufacturer... [chuck]: ------( audio device: 3 )--------------- [chuck]: device name = "" [chuck]: probe [failed] ... This is with git head built using libc, which describes itself as chuck version: 1.3.5.0-beta-4 (chimera) mac os x : intel : 64-bit http://chuck.cs.princeton.edu/ http://chuck.stanford.edu/ If I attempt to run with audio device 3 it blows up $ chuck --in:1 --out:2 --dac:3 --adc:3 --srate:48000 --loop Plug in failed to register with daemon Message response timed out [chuck]: system error: (kAudioHardwareUnspecifiedError) getting device manufacturer... [chuck]: unsupported sample rate (48000) requested... [chuck]: | (try --probe to enumerate available sample rates) [chuck]: cannot initialize audio device (use --silent/-s for non-realtime) michael

1 1

limit on number of OSC addresses you can listen to?
by Ben Steinberg 25 Aug '14

25 Aug '14

I've posted about this to the electro-music forum: http://electro-music.com/forum/viewtopic.php?p=402793 In trying to write some code for the Illucia dtr, I found that adding addresses to an OscIn object appeared not to work after twelve addresses. I wrote a test program that wasn't illucia-specific; the following code starts 16 OSC transmitters and 16 receivers. When you run it, you can see that transmitters 0-15 all transmit, but only receivers 0-11 receive. for ( 0 => int i ; i < 16 ; i++ ) { spork ~ output(i); spork ~ input(i); } while ( true ) { 1::second => now; } fun void output(int number) { 12008 => int port; "localhost" => string hostname; OscOut xmit; xmit.dest(hostname, port); while (true) { Math.random2f(5.5, 8.5) => float wait; wait::second => now; xmit.start("/tester/what/" + number); Math.random2f(0.0, 1.0) => float temp => xmit.add; xmit.send(); <<< "sent", number, temp >>>; } } fun void input(int number) { OscIn oin; OscMsg msg; 12008 => oin.port; oin.addAddress("/tester/what/" + number + ", f"); float val; while (true) { oin => now; while ( oin.recv(msg) != 0 ) { msg.getFloat(0) => val; <<< "received", number, val >>>; } 5::ms => now; } } I'm running ChucK 1.3.4 on Mavericks, with and without miniAudicle.

3 6