Am 03.09.2005 um 02:25 schrieb James Harkins:
You shouldn't have to prepare them. Select doesn't check the rate
of the first input so Select.ar(someKrInput, ......) should be fine.
hjh
No, it isn't. The rates of Select and its "which"-input must be the
same, it appears to me.
But you are right in that the error message complains about the
first numerical value in the array, not "which".
(BTW I came to ask this question while experimenting with TGrains
with audio rate triggering, except for the pan input where I put a
Select at control rate. But this led to some problem with
occasional false triggers)
Server.internal.boot;
{ Select.ar(Stepper.kr(Impulse.kr(5), 0, 0, 0, 2, 1), [-0.5,
0.5]) }.scope(1, 100);
/*
Select input was not audio rate: -0.5
ARGS:
which: a Stepper Stepper
array: -0.5 Float
2: 0.5 Float
ERROR: SynthDef 1810238137 build failed
...
*/
// the same error as above:
{ Select.ar(Stepper.ar(Impulse.ar(5), 0, 0, 0, 2, 1), [-0.5,
0.5]) }.scope(1, 100);
// but this works:
{ Select.kr(Stepper.kr(Impulse.kr(5), 0, 0, 0, 2, 1), [-0.5,
0.5]) }.scope(1, 100);
// (this would work too)
{ Select.kr(Stepper.ar(Impulse.ar(5), 0, 0, 0, 2, 1), [-0.5,
0.5]) }.scope(1, 100);
On Sep 2, 2005, at 3:41 PM, Stephan Wittwer wrote:
Hello,
How do people usually prepare simple numbers to get accepted
inside the array of a Select ugen running at audio rate?
Computationally cheap? (Numbers are okay at control rate)
Thanks for any hint, Stephan W.
_______________________________________________
sc-users mailing list
sc-users@xxxxxxxxxxxxxxx
http://www.create.ucsb.edu/mailman/listinfo/sc-users