Event Slew

Event Slew/Smoother macro

(18 Votes)
2.0 (Updated 14 years ago)
34.2kB
February 09, 2005
Reaktor 5 or lower

DESCRIPTION

This is contains two different event based macros that emulates the audio Slew module. It allows for comparison of CPU usage of these macros and the audio slew module. Turn off the Event Watcher, select the type of slew, play with the knob and record CPU usage. I'd appreciate people posting their CPU data in the comments, esp. Mac users.

One event module uses a speed limited Iteration module. It is based on Ernst Meyer's Smoother 2 but has several modifications to make it have characteristics closer to the audio Slew:

-Slewing is quantized to a step size set at input St, to ensure that it finishes precisely on targets that are multiples of St, say 0 or 1, without rounding errors, so you can do equality tests on the output.

-The in value is passed to out on startup

-If an event is repeated at in (say a 0 after the value is already 0), the event will be passed to the output, once.

The other event based macro does not use a speed limited iterator, but events fired at the control rate. As with above, it ends precisely at the target value, fires on start and repeats.

Here is my CPU data on a Pentium IV 2.4 GHz:
No Iterator, slewing: 1.7%, rest .8%
Iterator , slewing: 1.2%, rest .9%
Audio , slewing: 1.2%, rest 1.1%

This suggests to me that it might be hard to do slewing more efficiently than the audio slew, but you save CPU when resting when using event modules--and the speed limited iterator is better than a structure without it, unless my coding is just bad.

COMMENTS  (5)

Dietrich Pank
7 years ago
thank you!
ant stewart
13 years ago
I just had a look at it, I would rather make my own because it contains an audio module, it should only use about 10 modules including an accumulator
David Morris
14 years ago
...I was going with the claim in your Event Smoother that "The new one (smoother2) uses an iterator module with limited iteration speed, and theoretically this should be the lowest possible CPU. If not it is a Reaktor bug." Guess 4.1.3 changes that?
David Morris
14 years ago
Ernest, thanks for letting me know about that. Now I have go dig out a slewer that I did a long time ago that uses clocks and accumulators. Wonder where it is...
Ernest Meyer
14 years ago
Hi there :) Sadly you lose the cpu benefit somewhat, because in 4.13 the iterator uses cpu like an audio module when it is set to "imited speed."You'd get better cpu if you used an accumulator instead, and also, this would allow you to include logic which would adjust the step size based on event control rate.
now