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

Re: [chuck-users] The ChucK Show
by Les Hall 07 Apr '09

07 Apr '09

Hi folks, This week the ChucK show was a mess, heh! It started out with technical difficulties and choppiness which eventually got better, though my recording has gaps all through the show. The good news is that I'll be improving things by rebooting the machines before the show and testing before the show, plus buying a decent mic and a nanokontrol for the sliders. But we all recognize that we are new to this and such problems are inevitable. I'd like to ask for code submissions as we will be running out of material in a week or two. You can email code or recordings to inventor-66(a)comcast.net (that's me). Thanks and have a great week! Les

3 2

memory exhausted
by Gregory Brown 05 Apr '09

05 Apr '09

Hello all, I have written a script that uses a rather data file to generate a chuck file that is about 24000 lines long and 564KB. When I run the script I get a "memory exhausted" error. Are there chuck-imposed limits that I am running into? Is there a way to allocate more memory to chuck? I have tested this on two machines, both running OS X, ChucK 1.2.1.2, 2GB of RAM. It does not seem to matter what other processes are running or how much memory is available (real or virtual)… it always exits at the same line. Also -- when I cut the file down to a few thousand lines, it runs fine. Any thoughts would be great. Thanks, - Greg

2 3

segmentation fault / OSC
by Bozelos Dimitris 04 Apr '09

04 Apr '09

Hi again guys, I've run into some more problems in my brief acquaintance with ChucK (although it's definitely fun!). For some reason I constantly get a "segmentation fault" fatal error sometimes just after some seconds I run my shreds. What does this mean? I do something that might be silly, I send/receive parameters between shreds using OscEvents, can this cause the problem? Is there another way of communicating (exchanging control signals in this case) between processes? Once or twice I had an "OSC packet ...: buffer (or stack) overflow" error. Is there a buffer or a limit on the messages you send / receive? Can I somehow declare global variables? I checked the documentation and I didn't find anything. If the problem is because of excessive use of OSC I could maybe read/write global variables. Cheers, Dimitri ___________________________________________________________ Χρησιμοποιείτε Yahoo!; Βαρεθήκατε τα ενοχλητικά μηνύματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων http://login.yahoo.com/config/mail?.intl=gr

4 7

The ChucK Show
by Les Hall 03 Apr '09

03 Apr '09

Hi folks, Here is the description of the ChucK Show: The ChucK Show producer: Inventor (Les Hall) ChucK is a freeware music programming language from Princeton University. Those who program in ChucK, called ChucKists, share their code freely with each other under the GNU General Public License. Everyone enjoys each other's programs and all are free to copy and modify code with reckless abandon. The ChucK Show features programs written by Inventor, kijjaz, Kassen, wppk, Frostburn, Slinky, and others. You can learn about ChucK by visiting the ChucK forum on www.electro-music.com, where we all congregate to share code, help each other, and joke around a lot. Some ChucK links: http://chuck.cs.princeton.edu/ http://electro-music.com/forum/forum-140.html http://wiki.cs.princeton.edu/index.php/ChucK http://www.freedomodds.com/music/ Please post all ChucK Show submissions to the chucK forum, thanks. To hear the ChucK show, just click on over to www.electro-music.com and select "Radio". The show will be 7pm to 9pm EST, which is 23:00 - 1:00 GMT, or 4pm to 6pm left coast time. And we need more ChucK code! Please post code submissions to the ChucK forum, thanks! Les

4 3

Re: [chuck-users] chuck-users Digest, Vol 45, Issue 1
by Les Hall 01 Apr '09

01 Apr '09

On Apr 1, 2009, at 12:00 PM, chuck-users-request(a)lists.cs.princeton.edu wrote: > > Fellow ChucKists, > > The .quine() member function of the Shred object (which returns the > code of the shred in question as a string) doesn't correctly include > comments for sporked functions. > > To demonstrate, this works; > =========================== > //this is a comment > <<<me.quine( )>>>; > ======================= > > Yet this; > > ===================== > fun void foo() > { > //this is a comment > second => now; > me.quine(); > } > > spork ~ foo(); > hour => now; > =================== > > only prints this (notice the removed comment); > > [chuck](VM): sporking incoming shred: 1 (unnamed1)... > "second => now; > me.quine();" : (string) > > This is of course quite inconvenient. > > Yours, > Kas. > Kas, I am deeply concerned about the .quine() bug. Upon further testing, it appears to ignore every other comment yet print the others. Surely we must address this blatant problem somehow. Les

1 0

Shred.quine() bug
by Kassen 01 Apr '09

01 Apr '09

Fellow ChucKists, The .quine() member function of the Shred object (which returns the code of the shred in question as a string) doesn't correctly include comments for sporked functions. To demonstrate, this works; =========================== //this is a comment <<<me.quine( )>>>; ======================= Yet this; ===================== fun void foo() { //this is a comment second => now; me.quine(); } spork ~ foo(); hour => now; =================== only prints this (notice the removed comment); [chuck](VM): sporking incoming shred: 1 (unnamed1)... "second => now; me.quine();" : (string) This is of course quite inconvenient. Yours, Kas.

1 0