Demand
Related Docs:
class Demand
| package ugen
trigger. Can be any signal. A trigger happens when the signal changes from non-positive to positive.
a demand-rate signal (possibly multi-channel) which is read at each trigger
trigger. Resets the list of ugens (in) when triggered.
trigger. Can be any signal. A trigger happens when the signal changes from non-positive to positive.
a demand-rate signal (possibly multi-channel) which is read at each trigger
trigger. Resets the list of ugens (in) when triggered.
A UGen which polls results from demand-rate ugens when receiving a trigger. When there is a trigger at the
triginput, a value is demanded from each ugen in theininput and output. The unit generators in the list should be demand-rate. When there is a trigger at the reset input, the demand rate ugens in the list are reset.Note: By design, a reset trigger only resets the demand ugens; it does not reset the value at Demand's output. Demand continues to hold its value until the next value is demanded, at which point its output value will be the first expected item in the
inargument.Note: One demand-rate ugen represents a single stream of values, so that embedding the same ugen twice calls this stream twice per demand, possibly yielding different values. To embed the same sequence twice, either make sure the ugen is demanded only once, or create two instances of the ugen.
Warning: Demand currently seems to have problems with infinite sequences. As a workaround use a very large length instead. E.g. instead of
Dbrown(0, 1, inf)useDbrown(0, 1, 0xFFFFFFFF)!Warning: Demand seems to have a problem with initial triggers. For example
Demand.kr(Impulse.kr(0), 1)will have a spurious zero value output first.The argument order is different from its sclang counterpart.
TDuty
Duty