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

Scale & diatonic
by Hans Aberg 12 Oct '11

12 Oct '11

I have made a program, scale.ck, that admits one to work with scales, including tuning stretch, céleste tremulant, retune them, and then save to a file, with a line of code that can be pasted back into the source, available at next program startup. Scale tunings can be put into tuning banks, and otherwise defined by your favorite method. Details in the file. I have also updated my program for diatonic tuning systems, diatonic.ck. Just a few changes: adding some common tunings, fixing typos. The files are available here: http://www.math.su.se/~haberg/tuning_systems/ Hans

4 6

pulse width modulation
by Michael Heuer 08 Feb '10

08 Feb '10

I'm trying to model the following in ChucK "OSC1, OSC2, and an LFO (Low Frequency Oscillator) Modulation: OSC1 produces a simple square wave tone, the pulsewidth of which is modulated with OSC2, and then amplitude modulated with the LFO oscillator." I think I understand the LFO amplitude modulation part, but I don't understand what pulse width modulation with osc2 means. SqrOsc osc1; SqrOsc osc2; SqrOsc lfo; Gain master; lfo => blackhole; osc1 => master; 220.0 => osc1.freq; 0.8 => osc1.gain; 20.0 => lfo.freq; 0.9 => lfo.gain; fun void updateAtSampleRate() { while (true) { ((lfo.last() + 1.0) / 2.0) * 0.8 => osc1.gain; 1::samp => now; } } master => dac; spork ~ updateAtSampleRate(); 2::second => now;

3 2

Difference between .freq and .sfreq
by Sean Sawyer 26 Jan '10

26 Jan '10

Probably a noob question, but I'm not sure of the difference between these two parameters. I see from the documentation that one is "phase-matched" and the other is not, but after messing around a bit I've been unable to come up with a scenario in which behaviour differs when using one or the other. Can anyone shed some light on the difference? Cheers, Sean

1 0

a koan (and a bug request)
by Robert Poor 25 Jan '10

25 Jan '10

Quiz: what will happen when the following code is run[*]? ================= class Trait { fun void announce() { <<< "I am generic." >>>; } fun void invoke() { announce(); } } class Legacy extends Trait { fun void announce() { <<< "I am legacy." >>>; } } class Lunacy extends Trait { public void announce() { <<< "I am lunacy." >>>; } } (new Legacy).invoke(); (new Lunacy).invoke(); ================= If you predict that it prints: "I am legacy." : (string) "I am lunacy." : (string) then here's a hint: there's a typo in the definition of Lunacy's announce() method where it says "public void announce()..." instead of "fun void announce()...". If you predict that it gets a compiler error when it encounters the typo, well, you'd be wrong there as well. What happens instead is that it compiles without any error messages, and the result is: "I am legacy." : (string) "I am generic." : (string) It took me a LONG time to find this one (and an even longer time to boil it down to a succinct example). Will the powers that be please take this as a request to beef up the parser? Thanks. - Rob [*] in particular, chuck v 1.2.1.3 mac os x : intel. I'm guessing that this is platform independent, though...

3 2

accessing static methods through an instance?
by Robert Poor 24 Jan '10

24 Jan '10

[Coincidentally, Stefan's message about identically named (instance) methods arrived as I was composing this note. It's possible this is the same thing, but with a different twist...] One might expect that an instance reference calls an instance method and a class reference calls a static method even if they have the same name, but it ain't so. And the compiler doesn't issue any warning. Consider the following: ==== file: fn.ck public class F { fun static void method() { <<< "static method()" >>>; } fun void method() { <<< "instance method()" >>>; } } F.method(); // call method via class (new F).method(); // call method via instance ==== produces: "static method()" : (string) "static method()" : (string) ==== I can convince myself that this isn't really a bug, if "static" really means "make this variable or method shared by all instances", but it would be nice if the compiler warned you about identically named methods. (Note that the compiler DOES issue an error for identically named variables.) - Rob

2 1

Identical functions
by Stefan Blixt 24 Jan '10

24 Jan '10

You can declare identical functions, with the first one apparently taking charge: fun void g(int i) { <<< "fddf" >>>; } fun void g(int i) { <<< "fdfd" >>>; } g(3); I have a feeling this is old news, but I can't recall this specific issue being mentioned. It doesn't feel right. It's the same if the functions are inside classes. Could it have something to do with enabling cross-shred referencing? Cheers, Stefan -- Release me, insect, or I will destroy the Cosmos!

2 1

got .deb?
by mike clemow 24 Jan '10

24 Jan '10

Hello Fellow Chuckists, Is anyone maintaining a .deb package for chuck/mini? Best, Mike -- http://michaelclemow.com http://semiotech.org

3 3

in need of some starter tips...
by Suvash Thapaliya 24 Jan '10

24 Jan '10

Hello Chuck-ers ! …want to begin with a big HI to everyone here ! I came to know about this software(programming environment) sometime ago, a couple of years i guess. And i want to make some serious use of it. I plan to use chuck as a sound engine coupled to another program which would feed data to chuck(in real-time), primarily targeted for musical exploration. It would be great if someone would set me some pointers to begin with. wanna-be chucker suVasH.....

2 1

Re: [chuck-users] wishlist for the new year
by Kurt Kotheimer 14 Jan '10

14 Jan '10

Happy New Year!!! I couldn't resist making my own wish-list: 1) Garbage collection or something like a .destroy() method for UGens so we can create UGens in a loop without worrying about memory. 2) A way to write our own UGens without building them in C++ and compiling the source. 3) Namespaces and an import mechanism beyond Machine.add(). 4) Revival of some of the old ChucK shell plans and more shell development, the shell is one of the coolest things about ChucK IMHO. (BTW- shell crashes the Mini for me, I can only use it on the command line) 5) This has been discussed in depth before but I still think some kind of syntax like: SinOsc m => blackhole; SinOsc c => dac; m => Gain g => c.freq; //this line!!! 440.0 => g.gain; ...might be cool, although it is not very "ChucKian". Right now we can use UGen.op to choose if we want AM or FM but I dont think there is a way to have both without explicitly chucking a value within a time loop :( Correct me if I am wrong about this. 5 b.) A Dc UGen to add offset gain would be nice with the above "syntax" for setting center frequency. 6) I could see some kind of anonymous function thing being pretty powerful. ( I like the curly braces {} approach of SC). Thanks All and happy ChucKing in 2010! Kurt ........................................................ http://www.kurtKotheimer.com .......................................................

3 4

PitShift
by Scott Hewitt 13 Jan '10

13 Jan '10

Hi, Just wondering what the .shift parameter of PitShift is measured in cents, hz, something else? all the best Scott

2 1