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

osc to keyboard
by Alpha Core 19 May '08

19 May '08

hello Ive been working on triggering Osc by the use of the keyboard and im still a having trouble I read the kb.ck file in the hid folder to figure out how it triggered and output the keys so i came up with the below syntax. // setting up the keyboard to trigger Osc // this should trigger a middle c tone when A key is pressed { if (msg.is ButtonDown()) and if (msg.my_keynumber = 65 then SinOsc s => Dac; 261 => s.freq; 1::second => now } it still giving me errors ? even when i running the kb.ck file in chuck any help would be great thanks Gabriel --------------------------------- Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how.

11 21

(windows) Mini-Audicle keeps running after exit..
by Renato Fabbri 03 Feb '08

03 Feb '08

Hi Chuck List, Being my first post, thanks for all. I have been reading the list for a while already, and thanks that too. I am trying chuck on windows and it is being quite nice as all goes well and smooth. Mini-audicle is the only noty boy here. When i exit it, by alt+F4, clicking on the little X on top right, or by Alt+X, it visually quits, but it still keeps a process "mini-audicle" in task manager. I am using Windows XP and mini-audicle 0.1.3.8 (alpha). I had no similar problems in Ubuntu. Have anyone seen something similar? cheers, renato

4 3

/examples/event/event_extend.ck
by Renato Fabbri 31 Jan '08

31 Jan '08

hi Chuckers, I have two questions regarding the example bunddled with chuck in /examples/event/event_extend.ck (attached for convevience) first, if the function hi is sporked four times, why does it run only once? i mean, in each loop that takes one second i only see one integer being printed. Anyway, i have removed 3 of the 4 spork statements and it seems to run just the same way. second, why is the return type of hi specified as int when it doenst return anything? I have exchaged the return type for void and it seems to run normally as well. can anyone help me to understand these things? thanks, cheers, renato

2 1

Mac OS X on-the-fly issue
by David Posey 26 Jan '08

26 Jan '08

I'm unable to get the on-the-fly features of ChucK working. I can do one thing at a time from the command line, i.e. %> chuck foo.ck or %> chuck --loop But I cannot do, say, "--loop" followed by "--add bar.ck" to add a shred. The problem is that once I do "--loop" no prompt reappears for me to type in "--add bar.ck", unless I ctrl-C out of it first, which kills the first process anyways. What's the catch? How do I run a second shred from the command line? (I'm running Chuck 1.2.1.1 on Mac OS X 10.4 using the command-line interface.) Any help would be greatly appreciated. --David

4 3

Looped sample playback rate
by Ollie Glass 25 Jan '08

25 Jan '08

Hello ChucKers, I'm using SndBuf to loop samples. I read a sample and call .loop(1) to do this, but if I call .freq(x) nothing plays, where 0.25 < x < 4. Is this an issue with SndBuf or am I missing something? Thanks, Ollie

2 1

giving birth made easy (and head-hitting)
by Kassen 24 Jan '08

24 Jan '08

Dear list, It turns out that for a VM that has been running for a arbitrarily long time it's still easy to find the time of it's birth. considder the following; ================= time birth; now - (now /samp)::samp => time start; if (start == birth) <<<"Yay">>>; ============================= *hits head* So, it's possible after all to define objects of type time wthout using time after all; adding durations to a "fresh" time object will in fact do. Next up; a poor man's casting; ============================= //demo <<<dtot(second)>>>; <<<ttod(now)>>>; //the meat //time to duration and dur to time by Kassen. //considered trivial once I thought of it //no rights reserved fun time dtot (dur input) { //duration to time //probably leaks memory time garbage; input +=> garbage; return garbage; } fun dur ttod (time input) { //time to duration //here we go again with the strong typing return ( input/samp )::samp; } ==================================== *hits head again* Cheers, Kas.

2 2

Help!
by mike clemow 21 Jan '08

21 Jan '08

I'm suddenly, for no apparent reason, getting this error: [Untitled]:line(1): ugen's of type 'DAC' have no input - cannot => from another ugen my patch is: SinOsc s => dac; 2::second => now; Any hints here? This is... just... wrong. -Mike -- http://semiotech.org http://blog.deadlylittlepills.com http://www.murderkills.com http://shadowofaculture.blogspot.com

4 12

winxp problems?
by miya6611 20 Jan '08

20 Jan '08

hello. I downloaded "chuck-1.2.1.1". But --version is as follows. Chuck version: 1.2.0.8 (Dracula) Exe target: Microsoft win32 http: //chuck.cs.princeton.edu/ example/analysis does not operate :( and... chuck --bufsize950 [chuck]: no input files... (try --help) -- miya6611 http://mindblast.jp/

2 3

Chuck used in NYC tonight
by mike clemow 19 Jan '08

19 Jan '08

Hey there, fellow Chuckists! Just wanted to let you guys know that Chuck is getting some public exercise tonight at the Heart and Soul Gallery in Brooklyn, NY from 6-10pm EST. My band, Murder, is collaborating with another band, Stars Like Fleas, to create an interactive sound sculpture from found-objects that uses Chuck as part of its technology stack. Sensors -> Microcontroller -> Python -> OSC (via simpleOSC) -> Chuck It's nothing terribly complicated on the Chuck side, since we're using it to listen for OSC messages and play back sound samples from the bands in interesting configurations, but I thought it deserved mention, so at the very least, since you folks helped me learn Chuck ;-), honor is due. Plus, if anyone is in the area and totally bored, you should stop by. Here are the details, links: http://www.heartandsoulpilates.com/showing.html http://www.murderkills.com http://slf.praemedia.com/ (I hope it works!) Cheers, Mike Clemow -- http://semiotech.org http://blog.deadlylittlepills.com http://www.murderkills.com http://shadowofaculture.blogspot.com

2 2

LiSa zero-crossing snap how-to
by Kassen 14 Jan '08

14 Jan '08

Dear ChucKists. (particularly Dan who asked me for examples of LiSa usage a while back) Below you'll find a example of how to make LiSa's loop points snap to the next positive zero crossing in her buffer, provided the buffer was loaded from a recorded file using SndBuf. This has many uses, particularly to glitch-free loop a sample that's not noisy enough to hide clicks and/or particularly bass heavy in situations where the overall structure of the program loops at a different rate then the sample loop length and crossfading would mean adding shreds..This is a polite way of saying it's especially good for cheap & easy stuttering kick-drums. Mind that this will change the loop's length and thus pitch and/or timing, it's much cleaner sound-wise though. In some situations this may be cleaner or lead to cleaner code than the methods in the examples/docs but it would be a bad idea to think this is the best way to avoid clicks in all cases as it isn't. It's a interesting option though and one I found to work well compared to it's complexity. With lots of comments, I hope others will find this as usefull as I'm finding it now. Yours, Kas. ================================================== //Zero crossing detection and snapping for LiSa by Kassen //Permision granted for redistribution, modification, etc. //no waranties, no refunds, please mind your speakers. //Remixing strongly encouraged. SndBuf buf => LiSa l => dac; //your sample goes here //this patch is primarily meant for low drum beats or notes //clicks aren't as objectionable for claps and the like //may be impractical for lengthy soundscapes..... buf.read("kick.wav"); int n, m; float last; int crossings; 2::second => l.duration; //detect the number of positive zero crossings in the file //we do this faster than realtime //if you try this for long samples while other stuff is running //there may be glitches as this likely maxes out the cpu //due to not advancing time for (0=> n; n<buf.samples(); n++) { if ((last < 0) && ( buf.valueAt(n) >= 0)) { crossings++; } buf.valueAt(n) => last; } <<<crossings, "positive zero crossings in sample">>>; //make a array of this length int zerocrossings[crossings]; //create a index of their locations 0 => crossings; 0 => last; for (0=> n; n<buf.samples(); n++) { if ((last < 0) && ( buf.valueAt(n) >= 0)) { n => zerocrossings[crossings]; crossings++; } buf.valueAt(n) => last; } //go LiSa! l.record(1); buf.samples()::samp => now; l.record(0); //save cpu buf =< l; //loop forever to demo //here we only snap loopEnd() to the crossings, //loopStart() may be treated in the same way, //at which point only using positive crossings becomes usefull. while(1) { //start at the beginning 0::ms => l.playPos; l.play(1); //modulate loop length for (1 => m; m < 8; m++) { m* (2::second /16) => l.loopEnd; //don't bother trying to detect crossings if we already passed the last one if ( (l.loopEnd()/samp)$ int < zerocrossings[zerocrossings.cap()-1]) { //find the next positive zero crossing... 0 => n; while( (((l.loopEnd()/samp) $ int ) > zerocrossings[n]) &&n< zerocrossings.cap()-1 ) n++; //snap to it zerocrossings[n +1]::samp => l.loopEnd; } second => now; } //get rid of clicks at the end, pause and start over l.rampDown(50::ms); second => now; }

1 0