Hi!
I’ve noticed that Demand, Duty and TDuty share almost the same description:
Duty
Demand results from demand rate UGens.A value is demanded of each UGen in the list and output according to a stream of duration values. 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 and the duration are reset. The reset input may also be a demand UGen, providing a stream of reset times.
TDuty
Demand results as trigger from demand rate UGens.A value is demanded each UGen in the list and output as a trigger according to a stream of duration values. 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 and the duration are reset. The reset input may also be a demand UGen, providing a stream of reset times.
Demand
Demand results from demand rate UGens.When there is a trigger at the trig input, a value is demanded each UGen in the list 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.
What would be a better description for these UGens?
What would be a good definition for Demand UGens regarding their usage? Something like “some way to do sequecing fast enough (thus on the server side), so that one can perform operations like realtime controlled granular synthesis withing short timmings, sample accurate operations, etc” ?