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

Re: [chuck-users] sillyness witth file names
by Les Hall 15 May '09

15 May '09

Not to get off topic too far, but this reminds me of a funny situation back in college. Someone had managed to create an undeletable file, and even the superusers could not delete it. I think it had a single space character as the filename and the Unix of the day didn't let you surround a filename with quotes (this was close to 20 years ago). So the file lived on eternally, lol. Another funny story from college: One day the sysop asked me for my password. I replied sharply with what sounded to him like "bite me", an obvious rude remark. He said "No, really, I need it to fix some stuff." I replied by spelling out the password: "That's the password: byteme". Everyone had a great laugh. We now return you to your regularly scheduled ChucK mailing list. Les

1 0

Diatonic tuning system
by Hans Aberg 13 May '09

13 May '09

This code now allows defining diatonic tuning systems, which once defined, selects the intervals. It is very easy to add a new tuning system: just one line. Plus adding its name were you want to have it on the keyboard. A tuning system is defined by giving intervals, which can be given in different units (ratio, log, cents), and their diatonic coordinates, plus an octave which needs not be the interval ratio 2 or be equal to 2m+5M. Intermediate pitches are supported (but at most one for the moment). Also a function that computes all ETs, plus some other illustrating tuning systems. In order to illustrate that the octave needs not the interval ratio 2, Georgian style tunings have been added, which divides the perfect fifth into four equal steps, so that m = M and the octave is slightly sharp. Plus Bohlen-Pierce scales, dividing the ratio 3 into 13 steps, with the octave 5m+4M. And the intermediate pitches are illustrated by Just intonation relative Pythagorean (might also be used for Turkish music description), Turkish E53, and Persian style tunings. So with just one neutral second added, one can cover a lot. Details: see the file. Stay tuned! Hans

3 5

Re: [chuck-users] The ChucK Show
by Les Hall 13 May '09

13 May '09

Hello ChucKists! I have good news regarding The ChucK Show. We are now set up for live ChucK! That means instead of a playlist of pre-recorded ChucK mp3's, the show will feature actual ChucK programs running in real time. This allows me to do stuff like run interactive programs like Digitar, Generator, and Guitar Lab as well as play multiple ChucK programs simultaneously. I even coded up a ChucK program that uses my homemade DIY ChucK controller to permit hardware control of the microphone and I added a "Demonic Chipmunk" Vocoder to the program as well. You'll have to tune in to hear the Demonic Chipmunk Vocoder in action, it is funny! Cheers, Les (Inventor)

1 0

"pure"
by Tom Lieber 10 May '09

10 May '09

class X { fun void doit(); } [Untitled]:line(2): function declaration must contain code... [Untitled]:line(2): (unless in interface, or is declared 'pure') [Untitled]:line(2): ...at function 'doit' interface X { fun void doit(); } [Untitled]:line(2): function declaration must contain code... [Untitled]:line(2): (unless in interface, or is declared 'pure') [Untitled]:line(2): ...at function 'doit' class X { fun pure void doit(); } [chuck](VM): sporking incoming shred: 1 (Untitled)... Does anybody use "pure" or know what it does? The last example seems to be equivalent to saying "fun void doit() { }". -- Tom Lieber http://AllTom.com/

5 7

iPhone => ChucK
by Mark Cerqueira 10 May '09

10 May '09

Hi all, About a week ago I posted a message about one of many options, OSCTouch, to use an iPhone/iPod Touch as an interface device via OSC for musical performance. There were some responses on other apps that could be used, OSCemote and Mrmr, so I got all of them and played around with them. Fortunately, I also had a PLOrk final that involved creating a new instrument so I figured I might as well give it a go and see if I could get the iPhone to speak to ChucK directly. Here is the final product: http://wiki.cs.princeton.edu/index.php/PLOrk2009/MarkCerqueiraFinalProject I wrote a new class called OSCemote.ck that lets OSCemote speak directly to ChucK. The wiki page has links to the code, sample files to mess around with, implementation details, and known issues/future work. I figured some on this list could make good use of an iPhone that talks to directly ChucK. Enjoy! Any feedback on improvements/issues is, as always, very welcomed! Best, Mark

1 0

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

09 May '09

Hi folks, We had a really big big shew last week and we're up to show 7 now! Sunshine was a blast as always and her psychotic dog Ginger interrupted with barking as usual, haha! Last week we featured wmonk and the one and only Ge Wang as our two Chuckists of note! Will you be next? We need material so post away with code or mp3's, thanks! You can get recordings here: http://electro-music.com/radio/archives/ Peace Out! Les (Inventor)

1 0

Array out of bounds.... error usability
by Kassen 08 May '09

08 May '09

Fellow ChucKists, I have a ArrayOutOfBounds error and I'm quite sure that's one of my mistakes, not a ChucK one. This will require a bit of searching as I have rather a lot of arrays here and rather a lot of different things are done with them. Let's have a look at this; ArrayOutOfBounds: in shred[id=2:tr8or.ck], PC=[3565], index=[4] Ok, so it's a array that gets defined in my main shred and it's one that's 4 or less elements in size. That narrows it down considerably but we're not there yet. Now, I have the feeling that ChucK is trying to tell me something with the "PC=[3565]" but that bit is quite useless to me as I have no idea what it means. Questions; What does the PC bit mean? How is it useful? Can we consider ways of making it more useful? Yours, Kas.

4 6

other ways to live-code with time
by Tom Lieber 08 May '09

08 May '09

impromptu is a live-coding environment for OS X that looks very interesting, definitely something I need to try out once I've escaped the clutches of my end-of-year work. http://impromptu.moso.com.au/ I thought I'd bring it up not only because it's interesting, but because its tutorial on "time" contrasts impromptu's asynchronous model with ChucK's synchronous one: in impromptu, time passes while your code is running. You can read the tutorial here: http://impromptu.moso.com.au/tutorials/time.html Just think... you could load a WAV file without hanging the VM! It's interesting to see what you get when you trade one complication (waiting on slow shreds) for another (having "now" change beneath your feet). Here are some, from the tutorial: "There are a couple of gotcha's to keep in mind when doing schedule and forget programming. The first thing to keep in mind is that (now) is an airy fairy thing. In the example below the two notes may be scheduled to play on the same sample - but then again, they may not - (now) may have moved forward in time between the two calls (even if evaluated at the same time). (play-note (now) piano 60 80 *second*) (play-note (now) piano 72 80 *second*) "Often this lack of precision is fine (i.e. too small a change to be noticeable) but where absolute accuracy is required a time variable should be used. (let ((time (now))) (play-note time piano 60 80 *second*) (play-note time piano 72 80 *second*)) "This inaccuracy becomes more of an issue when amplified over time such as using (now) inside a recursive callback loop. We can avoid the problem by precisely incrementing a time value between each recursive callback (note that any arguments required by the function being called back must also be passed to callback). ;This is bad (define loop (lambda () (play-note (now) piano 60 80 *second*) (callback (+ (now) *second*) 'loop))) (loop) ;This is good (precise time arg is now incremented each recursion) (define loop (lambda (time) (play-note time piano 60 80 *second* ) (callback (+ time *second*) 'loop (+ time *second*)))) (loop (now)) "The second major gotcha in recursive callback loops is that (now) is now. Code requires some time to execute. If you are executing a call to evaluate a note (now) by the time the code is evaluated it will already be late. You should always try to schedule your code execution ahead of the scheduled time of your tasks. ;This is best (callback happens 4100 samples earlier than new time) (define loop (lambda (time) (play-note time piano 60 80 1.0) (callback (+ time 40000) 'loop (+ time 44100)))) (loop (now)) "In the this-is-good version of loop the time sent as an argument to loop is exactly the same time as the scheduled callback time. The problem with this is that the next note needs to be scheduled at exactly the same time that the function is called. The note will always be late. The this-is-best version schedules the callback just ahead of the time that we want to schedule the note. This gives us 4100 samples to execute the code to schedule the note before the note is required to sound." The last sentence reminds me of the thread a while back about benchmarking UGens. :) -- Tom Lieber http://AllTom.com/

7 20

Re: [chuck-users] The ChucK Show
by Les Hall 06 May '09

06 May '09

When do you need it by, Les? I have to put together something for my thesis presentation on Friday. The project involves data-sonification and ChucK is my weapon of choice. _mike mike, Anytime is fine, i'll just include it in the next show whenever I get it. Cheers, Les (Inventor)

1 0

WvIn on osx and linux
by jo 06 May '09

06 May '09

Hi, have been using WvIn for some while as a workaround to read a data file into chuck (this was suggested by someone in an earlier post), e.g. WvIn w => blackhole; "data.wav" => w.path; float n; repeat(20) { 1::samp => now; w.last() => n; <<< n >>>; } This works fine on my mac. However, when I try to do this in linux, it fails, sort of. The first value is the same as on os x, but then they deviate, not completely, but significantly (more than 10%), so it can't be a simple rounding error. I'm relatively sure that the values on the mac are correct because I write the data to the wav file myself. It's not obvious to me why the reading of any .wav file (using last()) should produce different values on different operating systems, but they do on my computers! Does anyone know what could be going on here? thanks, jo

3 8