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

"make" not compiling -- Snow Leopard
by Andrew C. Smith 11 Sep '09

11 Sep '09

Don't really know who to turn to here, so I'm coming to you. I used to be able to very easily compile ChucK (plus the mini in a recent post) but "make" doesn't seem to be working for me now that I've got Snow Leopard. Would the new OS override or delete some previous compiler? Related but sort of unrelated question: why won't the xcode project for ChucK work? I get an error that it's missing its project.pbxproj file. But if there's a chuck.xcode file, it would seem that someone somewhere is building ChucK with xcode. Any takers or either of these? This is sort of an either/or question--if you fix one of my problems then I'll stop caring about the other one. Andrew

4 6

Re: [chuck-users] chuck shell... --> My vim usage
by Bill Nye 11 Sep '09

11 Sep '09

> From: kurt <sobrilliant(a)gmail.com> > I like the Mini but I really like Vim. That is > really the only reason I use the shell. When I heard mention of vim I thought I would share what I use to test chuck code snippets, directly from inside vim. To get alignment, be sure to view the following with a fixed-width font. It consists of one bash script, a symbolic link, and, on Win, a .bat file. In the main bash script below, the second 'cat' line returns the same stdin chuck code lines back into vim, followed then by chuck's stdout. (Of course, you also hear the chuck output, if any.) I'm sorry to say that after days of trying, I could not get chuck to play, and also deliver its stdout in just one invocation, hence the two chuck.exe lines. FILE ~/bin/chuck_execution_in_vi (Win version) #! /bin/bash # chuck_execution_in_vi -- Typically used in vi as: # :'a,.!chu to leave original lines and also # return Chuck execution output. tmp="/tmp/tmp.chu.ck.$$" cat > $tmp cat $tmp cmd /c start "`cygpath -w ~/bin/chuck.exe`" $tmp "`cygpath -w ~/bin/chuck.exe`" --silent $tmp \ 2>&1 | tr -d '\015' rm -f $tmp exit TESTS: Sit on next line in vim and type :.!chu <<< "Hello" >>>; You should see in vim after the '<<<' code line: "Hello" : (string) Sit on 'now' line and type :-,.!chu SinOsc s => dac; 1::second => now; FILE ~/bin/chuck_execution_in_vi (Mac version) #! /bin/bash # chuck_execution_in_vi tmp="/tmp/tmp.chu.ck.$$" cat > $tmp cat $tmp chuck $tmp 2>&1 rm -f $tmp On Mac and Win (cygwin) I have this symbolic link to cut down on typing: ~/bin/chu -> ~/bin/chuck_execution_in_vi On Win, I also need this parallel .bat file: (I set the 2 env vars in my .profile) FILE ~/bin/chu.bat @ECHO OFF PATH %WPROGRAMS%\cygwin\bin;%PATH% %WPROGRAMS%\cygwin\bin\bash %WHOME%\bin\chu %1 %2 %3 %4 %5 %6 %7 %8 %9 Of course, this only works well if the chuck code terminates on its own. I don't know what this can do for --loop or shreds but it may give you some ideas. Incidentally, on both Mac and Win I have QuicKeys, so I just do 'ma' (to mark the snippet beginning) move to the end, and type Ctrl-Shift-C , which simply types :'a,.!chu for me. -Bill

3 2

Problems compiling and running ChucK on Arch Linux
by Sean Sawyer 11 Sep '09

11 Sep '09

Hi, I'm a ChucK newbie running on Arch Linux (gcc 4.4.1, libsndfile 1.0.20, ALSA 1.0.20, flex 2.5.35, bison 2.4.1, make 3.81). When compiling ChucK, g++ complains that the function sprintf is undeclared in util_string.cpp. Sure enough, stdio.h is not included in util_string.h (or in chuck_def.h). After adding the following line to either util_string.h or chuck_def.h, ChucK compiles successfully - but I then get seg faults when running simple example code (e.g., examples/moe.ck). Any ideas? Verbose output from ChucK leading up to the seg fault is below. Thanks in advance, Sean [sean@zaphod src]$ ./chuck --verbose ../examples/basic/moe.ck [chuck]:(2:SYSTEM): setting log level to: 5 (INFORM)... [chuck]:(2:SYSTEM): initializing virtual machine... [chuck]:(2:SYSTEM): | behavior: HALT [chuck]:(2:SYSTEM): | locking down special objects... [chuck]:(2:SYSTEM): | allocating shreduler... [chuck]:(2:SYSTEM): | allocating messaging buffers... [chuck]:(2:SYSTEM): | real-time audio: YES [chuck]:(2:SYSTEM): | mode: CALLBACK [chuck]:(2:SYSTEM): | sample rate: 48000 [chuck]:(2:SYSTEM): | buffer size: 512 [chuck]:(2:SYSTEM): | num buffers: 8 [chuck]:(2:SYSTEM): | devices adc: 0 dac: 0 (default 0) [chuck]:(2:SYSTEM): | channels in: 2 out: 2 [chuck]:(2:SYSTEM): initializing compiler... [chuck]:(3:SEVERE): | initializing type checker... [chuck]:(3:SEVERE): | | adding base classes... [chuck]:(3:SEVERE): | | | class 'object' [chuck]:(3:SEVERE): | | | class 'array' [chuck]:(3:SEVERE): | | | class 'string' [chuck]:(3:SEVERE): | | | class 'ugen' [chuck]:(3:SEVERE): | | | class 'uanablob' [chuck]:(3:SEVERE): | | | class 'uana' [chuck]:(3:SEVERE): | | | class 'shred' [chuck]:(3:SEVERE): | | | class 'event' [chuck]:(3:SEVERE): | | | class 'io' [chuck]:(3:SEVERE): | | | class 'class' [chuck]:(3:SEVERE): | initializing emitter... [chuck]:(3:SEVERE): | loading built-in modules... [chuck]:(3:SEVERE): | | module osc... [chuck]:(3:SEVERE): | | module xxx... [chuck]:(3:SEVERE): | | module filter... [chuck]:(3:SEVERE): | | module STK... [chuck]:(3:SEVERE): | | module xform... [chuck]:(3:SEVERE): | | module extract... [chuck]:(3:SEVERE): | | class 'machine'... [chuck]:(3:SEVERE): | | class 'std'... [chuck]:(5:INFORM): | | initializing KBHitManager... [chuck]:(5:INFORM): | | starting kb loop... [chuck]:(3:SEVERE): | | class 'math'... [chuck]:(3:SEVERE): | | class 'opsc'... [chuck]:(2:SYSTEM): type dependency resolution: MANUAL [chuck]:(2:SYSTEM): initializing synthesis engine... [chuck]:(3:SEVERE): | initializing 'dac'... [chuck]:(3:SEVERE): | initializing 'adc'... [chuck]:(3:SEVERE): | initializing 'blackhole'... [chuck]:(2:SYSTEM): | initializing 'real-time' audio... [chuck]:(5:INFORM): | | initializing callback... [chuck]:(3:SEVERE): | allocating buffers for 512 x 2 samples... [chuck]:(3:SEVERE): starting compilation... [chuck]:(2:SYSTEM): starting listener on port: 8888... [chuck]:(2:SYSTEM): running virtual machine... [chuck]:(3:SEVERE): | initializing audio buffers... [chuck]:(3:SEVERE): | virtual machine running... Segmentation fault

3 9

static function overloading
by Kassen 08 Sep '09

08 Sep '09

Fellow ChucKists, Is there a reason why static functions can't be overloaded when the class they are a member of is extended? i don't (yet?) see why this would need to be so and it seems limiting. Yours, Kas.

4 7

The ChucK Show
by Les Hall 07 Sep '09

07 Sep '09

Hi folks, Last week on The Game Show we had plenty of ChucK. It was a hilarious time and we all enjoyed it. Next week: PLOrk and beans again! PLOrk as we all know is the Princeton Laptop Orchestra, and beans are the various ChucKists who contribute code. We'll have some most excellent music by Ben Zimmerman and a really good rendition of "Iron Man" by appleseedj and myself. Should be worth a listen at 7pm EST this Friday on www.electro-music.com radio. See you then! Les

1 0

One bit ChucK
by Hans Aberg 06 Sep '09

06 Sep '09

Have you discussed giving ChucK a 1-bit audio model? See for example: http://img3.harmony-central.com/Video/aes121/Korg_1-Bit_Recording_tutorial.… http://digitalmedia.oreilly.com/pub/a/oreilly/digitalmedia/2007/08/02/revie… It is essentially a raw format for audio. So it might help taking out those rough edges in the preprocessing. Hans

2 2

Good Moog, bad error (bug)
by Kassen 04 Sep '09

04 Sep '09

Dear list, Right now I'm having lots of fun with the Moog UGen, but when we mistakenly give it parameters out of range then the resulting error message is incorrect and potentially confusing; consider; Moog bob; 1.1 => bob.filterQ; this will give us; [chuck](via STK): Moog: Control value greater than 128.0! Yours, Kas.

2 1

chuck/[mini]audicle vs. gcc 4.4.x
by Fernando Lopez-Lezcano 04 Sep '09

04 Sep '09

This tiny patch makes chuck compilable under gcc4.4 (Fedora 11): ------- --- chuck-1.2.1.2/src/util_string.h~ 2008-07-16 02:55:17.000000000 -0700 +++ chuck-1.2.1.2/src/util_string.h 2009-06-11 18:24:55.349093274 -0700 @@ -36,6 +36,7 @@ #include "chuck_def.h" #include <string> #include <vector> +#include <stdio.h> // itoa -------- I'm also hitting this error in miniaudicle and audicle, any help?: gcc -D__LINUX_ALSA__ -D__CHUCK_STAT_TRACK__ `pkg-config --cflags gtk +-2.0` -O3 -c -I../lang/chuck-1.2.1.1/src -D__CK_SNDFILE_NATIVE__ ../lang/chuck-1.2.1.1/src/ugen_xxx.cpp ../lang/chuck-1.2.1.1/src/ugen_xxx.cpp: In constructor 'CNoise_Data::CNoise_Data()': ../lang/chuck-1.2.1.1/src/ugen_xxx.cpp:1183: warning: deprecated conversion from string constant to 'char*' ../lang/chuck-1.2.1.1/src/ugen_xxx.cpp: In function 'void sndbuf_ctrl_read(Chuck_Object*, void*, Chuck_DL_Return*, Chuck_VM_Shred*)': ../lang/chuck-1.2.1.1/src/ugen_xxx.cpp:2590: error: invalid conversion from 'const char*' to 'char*' make[1]: *** [ugen_xxx.o] Error 1 -- Fernando

3 4

Are array types really classes ?
by Cyrille.Damez＠laposte.net 04 Sep '09

04 Sep '09

Hi list, I am currently learning Chuck, so I this may sound like a silly question. The language specification states that arrays are objects, but I can't find the proper syntax to declare a class that extends an array type. Since, as far as I understood, float[] is a reference to an array of floats, I was not really surprised that Chuck does not accept "class foo extends float[]", but what would the proper syntax be, if that is possible at all ? Thanks

5 11

chuck and jack
by Bozelos Dimitris 03 Sep '09

03 Sep '09

Hello, I'm using chuck under linux with jack audio server. Although it is working generally fine, sometimes I get unexpected clicks with error messages in the jack window and I'm trying to figure out what's wrong. I suspect that it is a problem with how linux handles interrupts in real time. The reason I'm posting here is that I think that the cause might be that I'm often printing on the terminal with <<< >>>; and that, I think demands an interrupt. Because the request comes from chuck which is granted real time priority by jack, it might interrupt the audio and at some points I get these clicks. Does this make sense? Has anyone encountered a similar problem with chuck and jack? In this case, has anyone used any alternative way of getting feedback from chuck? Maybe, instead of formatting a string and printing on a terminal, send a string through osc to some other interface which would update a constantly displayed message or variable which might be less demanding and not real time priority? Any ideas of what this could be? That is similar to another problem I have encountered so far, many times I would like to keep an eye to various parameters, both current values and how they change over time, but printing the value on the terminal only when it changes is not enough. Any ideas welcome. Cheers, Dimitris ___________________________________________________________ Χρησιμοποιείτε Yahoo!; Βαρεθήκατε τα ενοχλητικά μηνύματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων http://login.yahoo.com/config/mail?.intl=gr

4 9