posted 01 August 2006 01:49            

So for example, 1 bpm: 120, which would normally trigger 120 times per minute, would in the above scenario trigger maybe 10 or 15 times, but always on the beat!

I'm trying to figure out a way to do this, any help would be much appreciated!

posted 01 August 2006 02:08            

((1 bpm: !BPM) nextRandom abs lt: !TriggerFrequency)

Now I'm wondering whether there is an equivalent of a 'duty cycle' for bpm: triggers?

It would be cool to specify the portion of each beat for which the trigger is to remain positive.

posted 01 August 2006 03:32            

There's two capytalk messages that might be helpful for what you're trying to do:

The triggerEvery: message would allow you to select how many triggers or beats it takes to set off the event. You could use a hotValue for this, such as triggerEvery: !NbrOfTriggers. The duty cycle will be 50% when you use this message.

To control the duty cycle on a sequence of triggers you can use the bpm: dutyCycle: message. So for example in your expression you could use:

((1 bpm: !BPM dutyCycle: !DutyCycle) nextRandom abs lt: !TriggerFrequency)

Cheers,