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

Forum
by Kassen 13 Aug '06

13 Aug '06

Hi, list! After a sudden surge of interst in ChucK on the Electro-Music forum and with Ge's blessing we now have a brand new forum for ChucK and related matters like the Audicles; http://electro-music.com/forum/index.php?f=140 This is not meant as a substitute for the list but as a diferent format for discussion for those who prefer a forum over a list. It might (should?) also lead to more interest in our little language so feel free to chuck it out and maybe spork a account if you'd like. Take care, Kas.

1 0

towards sucking less in 64-bit
by Ge Wang 10 Aug '06

10 Aug '06

Hi! We want to, once again, look into getting chuck working correctly in true 64-bit. To that end, if you have a 64-bit machine that chuck crashes (more than usual) on, please consider compiling the attached program, which prints the native data type sizes for your system, and email/post the output. This will give us a rough idea of the various size discrepancies that are most likely causing things to crash horribly under native 64-bit. To compile: g++ -o platform platform.cpp To run: ./platform You should see something like: char: 1 short: 2 int: 4 long: 8 float: 4 double: 8 void *: 8 endian: small Copy and paste the output and send it back with the names of your cpu and operating system. Thank you very much! Best, Ge!

3 2

Pause the OSC receiver?
by Ollie Glass 09 Aug '06

09 Aug '06

Is it possible to pause the OSC receiver, ie. stop it listening for events for a while? I'd like to do something like this... //create our OSC receiver OscRecv orec; 6449 => orec.port; // start listening (launch thread) orec.listen(); // some more code ... // pause listener orec.pause(); // more code ... // resume listening orec.listen(); Ollie

2 1

syncing to jack
by Atte André Jensen 09 Aug '06

09 Aug '06

Hi I'd like to synchronize some chuck stuff to jack. I generate my own events that all chuck stuff runs from, so I need some way of grabbing jacks time (quite often, unfortunately) and generate the appropriate events. Is this possible, and if so some pointers to get started would be appreciated. Thanks in advance. -- peace, love & harmony Atte

2 1

Re: [chuck-users] A modest proposal (caps)
by Jim Hinds 06 Aug '06

06 Aug '06

To most humans, a Rose is a rose is a ROSE. To computers (who are our servants) these are completely different, and we allow them to push their limitations in our faces. Because, the programmer rightly brings to our attention all the illegal, illegitimate, immoral consequences of our wishes. Not to mention that it is too difficult to implement. And would give rise to a race of moron babies who cant chew their own food. A simple hack to the lexical scanner would be to force the comparison to lowercase for key generators. OR allow a prefix that tells the scanner to force the comparison to lowercasee for the next word. Probably might look like a C cast: (lc)sinOSC. This forces the user to give the scanner a clue to when it is allowed to deviate from its strict string matching rule. The (lc) would be a single lexeme. Jim > > From: Atte André Jensen <atte.jensen(a)gmail.com> > Date: August 5, 2006 12:54:35 PM HST > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] A modest proposal (caps). > Reply-To: ChucK Users Mailing List <chuck- > users(a)lists.cs.princeton.edu> > > > Ge Wang wrote: > >> Perhaps the way to go for now is to provide uppercase convention for >> the native chuck ugen's (SinOsc, Impulse, Gain etc), but also keep >> the lowercase versions (sinosc, impulse, others) for backward >> compatibility. It's extra stuff in the namespace for now, but >> overall that might make more sense. Thoughts? > > That sounds fine. > > -- > peace, love & harmony > Atte >

1 0

more filters
by Kassen 06 Aug '06

06 Aug '06

Hi, again, Can we return to filters again for a moment? I ordered -and read most of- Perry's book (actually I debated some of the trickier bits with a math-whiz friend while sitting on a beach...), I went through the relevant bits in the manual but it's still not clear to me how to go about creating a simple traditional LP filter in chuck. Bandpass and resonators and so on are fairly clear now and a simple averaging lp filter to take the sharp edges of the high end is within my reach as well but the 2 or 4 pole LP filter of traditional/commercial synth designs still elude me. I apreciate the versatility of what we have but I'd still like either some pointers on how to go about creating a sweepable LP filter or perhaps a ready-made Ugen for this. Please? Yours, (if beging ;¬) ), Kas.

3 3

Re: [chuck-users] A modest proposal (caps).
by Ollie Glass 06 Aug '06

06 Aug '06

> > Perhaps the way to go for now is to provide uppercase convention for > the native chuck ugen's (SinOsc, Impulse, Gain etc), but also keep > the lowercase versions (sinosc, impulse, others) for backward > compatibility. It's extra stuff in the namespace for now, but > overall that might make more sense. Thoughts? I think uppercase is the best way to go, I like the consistency. If you're thinking of dropping the lowercase names in the future perhaps you could allow them but print a deprecated warning when they're used. Ollie

1 0

A modest proposal (caps).
by Kassen 05 Aug '06

05 Aug '06

Ok, list... I realise this may be edging on dangerous teritory but I was just fooling around with the miniaudicle and some filters and had to type this; sawosc s => TwoPole f => dac; This works perfectly; that's not the problem. My problem is that it's "TwoPole" and not "Twopole" or "twopole" and yet it's not SawOsc but sawosc. I realise this is because we are borowing from the STK and also using new stuff but.... Well, to be honest I'd realy prefer a consistent use of caps. Frankly I'd be in favour of simply making it all lowercase or at least a consistent use of case because this -to me- is hard to remember. Yours, Kas.

4 6

arrays holding arrays?
by Kassen 04 Aug '06

04 Aug '06

Hi list, I have a slight issue. I'd like to have a array in which every object itself is a array. Particularly I'd like to have one of 8 locations each of which holds a array of length 32. I tried this; int[32] memory[8]; And the miniaudicle immediately complains. I know the manual doesn't explicidly say arrays can hold arrays but it didn't explicidly say functions can return arrays either so I thought I'd try anyway (and frankly I feel this should simply be possible). Theoretically speaking I could get by with a 2d array but I'd realy like to be able to go; if(some event dealing with storing patern memories) { patern @=> memory[4]; } if(some event dealing with recaling patern memories) { memory[3] @=> patern; } How to go about this? In the interest of staying readable and compact I'd much prefer no to have to loop over a 2d arrays row in order to copie values one by one. Should I use the asociative array features? Am I missing some syntax bit? Are there reasons not to store arrays in arrays? Yours, Kas.

3 7

miniAudicle success
by Atte André Jensen 04 Aug '06

04 Aug '06

Hi I installed xubuntu 6.06 on my new (used) T41 ThinkPad, and miniAudicle worked right away (after patching with the UTF patch, version 2). Looking forward to getting more into this nice IDE (and reporting requests:-)) soon! -- peace, love & harmony Atte

1 0