Kassen wrote:
Anyways, this is the content of for instance 01_SinOsc.ck, do you think it looks sane?
Yeah, that looks "by the book" to me :¬)
Ok, thanks.
One thing that has me wondering now is the cost of a non-playing SndBuf; that's very low indeed, lower than a gain. Some optimisation must be going on there; nice.
OR: it wasn't connected to dac :-) I'm not sure it was on purpose, but agree it's confusing at least by looking at the filename (I suspect you didn't look at the chuck code). With it connected it looks different: file x10 x50 x100 x1000 -------------------------------------------------------- 02_SndBuf.ck 2.6 7.5 15.2 96.7 02_SndBuf_loaded_not_playing.ck 4.6 24.2 53.0 97.2 02_SndBuf_loop.ck 5.3 24.7 53.2 97.0 03_Gain.ck 2.6 7.3 14.4 96.2 A different story: Do you have any ideas about how to test stuff like multiplication vs division? These results lead me to believe that the usual rave about division being expensive it totally irrelevant as soon as you connect even a single UGen in your chuck code :-) file x10 x50 x100 x1000 -------------------------------------------------------- 11_cast_float_to_int.ck 2.2 2.2 2.2 2.2 11_divide_integers.ck 2.5 2.3 2.5 2.4 11_modulo_integer.ck 2.2 2.2 2.2 2.4 11_multiply_integers.ck 2.4 2.2 2.2 2.2 atte@vestbjerg:~/music/chuck/performance_tests$ cat tests/11_divide_integers.ck 0 => int instances; if(me.args()) me.arg(0) => Std.atoi => instances; int i; repeat(instances){ while(true){ 1::samp => now; 10 / 2 => i; } } 1::week => now;
PS; As a side note; GMail users can enable a google labs extension that will allow them to view selected emails in fixed-width font. This makes looking at tables like this a lot more convenient.
I'm using thunderbird... -- Atte http://atte.dk http://modlys.dk