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

example use of Modulate Ugen
by Graham Coleman 09 Feb '06

09 Feb '06

ChucK rockers, Hi list! I'm Graham. I like ChucK. Can someone give a working example of the Modulate Ugen? I hooked it up in the output of an STK instrument, but got no noise. Is it something you must poll for values, perhaps? Here's my unsuccessful try: -- Scale sc; //this is some utility code Wurley w => Modulate m => dac; m.vibratoGain( 0.5 ); m.randomGain( 0.5 ); m.vibratoRate( 1.0 ); int i,j; [0, 1, 2, 4, 5, 1, 2, 4, 3] @=> int mel[]; [1, 1, 3, 2, 1, 1, 2, 1, 1] @=> int dur[]; for (0=>int i; ; i++) { i%mel.cap() => int ind; sc.scaleFreq( mel[ind]+2, sc.mixo, 4, 0 ) => w.freq; w.noteOn( 0.4 ); 250::ms => now; } -- I'm running with the latest audicle and chuck on WinXP. best, Graham

2 2

Feature request
by Mike McGonagle 08 Feb '06

08 Feb '06

Hello Ge, I was wondering if it would be possible to include some method of determining if a function returns 'nan'? In working with fractals, some of the results that I get during a search for a new parameter set may produce a 'nan' value, but there seems to be no way of testing for that condition. As a result of this, several classes of fractals that I am working on don't complete a search because I can't test for this. I was thinking how this might go, and there were basically two forms that could work... // static constant if (result == math.nan) { doSomethingWith(result); } else { reportError(result); } or // a function call if ((result) => math.isNan) { ... Thanks, Mike

2 2

Question on Class and Inheritance
by Mike McGonagle 07 Feb '06

07 Feb '06

/* This one was a doozey... it took me about 2 hours to figure out this one, as I had rewritten some code, not thinking this could be the trouble... Anyway, it would appear Chuck doesn't differentiate between floats and arrays of floats when finding the proper function to call. I would think that this code would produce an output with a call to the B1, but when run, it actually calls the E1. Does ChucK treat floats and arrays of float the same when making this function determination? Well, yes it does, but should it? I would think, that if object oriented is a goal, then floats and arrays of floats would be treated differently. */ class B1 { fun void f(float f[]) { <<< "in B1.f", "" >>>; } } class E1 extends B1 { fun void f(float x, float y, float z) { <<< "in E1.f", "" >>>; } } class B2 { fun void f(float x, float y, float z) { <<< "in B2.f", "" >>>; } } class E2 extends B2 { fun void f(float f[]) { <<< "in E2.f", "" >>>; } } B1 b1; B2 b2; E1 e1; E2 e2; [ 0.1, 0.3, 0.7 ] @=> float myArray[]; b1.f(myArray); // in B1.f - correct e1.f(myArray); // in E1.f - wrong - should this actually call B1.f(myArray) e1.f(0.7, .553, 77); // in E1.f - correct b2.f(0.7, .553, 77); // in B2.f - correct e2.f(0.7, .553, 77); // in E2.f - wrong - should this actually call B2.f(0.7, .553, 77) e2.f(myArray); // in E2.f - correct //******* The following Java program illustrates what I was thinking should happen. Will ChucK follow what Java is doing? class Base1 { public String f(double x[]) { return "Base1"; } } class Ext1 extends Base1 { public String f(double x, double y) { return "Ext1"; } } class Base2 { public String f(double x, double y) { return "Base2"; } } class Ext2 extends Base2 { public String f(double x[]) { return "Ext2"; } } public class doit { public static void main(String[] args) { Base1 b1 = new Base1(); Ext1 e1 = new Ext1(); Base2 b2 = new Base2(); Ext2 e2 = new Ext2(); double myArray[] = { 0.7, .533, 75 }; System.out.println("b1: " + b1.f(myArray)); // b1: Base1 System.out.println("e1: " + e1.f(myArray)); // e1: Base1 System.out.println("e1: " + e1.f(0, 1)); // e1: Ext1 System.out.println("b2: " + b2.f(0, 1)); // b2: Base2 System.out.println("e2: " + e2.f(0, 1)); // e2: Base2 System.out.println("e2: " + e2.f(myArray)); // e2: Ext2 } } Thanks, Mike

2 2

Question regarding Sample level timing.
by Mike McGonagle 06 Feb '06

06 Feb '06

Hello all, I wrote this test this morning, and something seems amiss here with timing. Or am I understanding this wrong? /* The following code doesn't seem to work properly, as there appears to be a 2 sample delay from when the impulse is triggered from what is expected. as the 'doit' function is started at time 0.0, I would think that each and every impulse would be generated at 100::ms intervals, starting at 0.0, and not 2.0 The code generates the output below... */ impulse i => blackhole; fun void doit() { while(true) { 1.0 => i.next; 100::ms => now; } } now + 1::second => time later; spork ~ doit(); while(now < later) { i.last() => float val; if (val != 0.0) { <<< now, i.last() >>>; } 1::samp => now; } /* 2.000000 1.000000 4412.000000 1.000000 8822.000000 1.000000 13232.000000 1.000000 17642.000000 1.000000 22052.000000 1.000000 26462.000000 1.000000 30872.000000 1.000000 35282.000000 1.000000 39692.000000 1.000000 */ Thanks, Mike

2 3

Release schedule for 1.2.0.5
by Mike McGonagle 06 Feb '06

06 Feb '06

Hello Ge, Thanks for looking into the impulse bug so quickly. I was wondering if the development team has a regular schedule under which you are working? I was just curious at how often there will be updated releases for ChucK are being made. Thanks, Mike

2 1