1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Autoscaler

Discussion in 'REAKTOR' started by MuShoo, Aug 17, 2007.

Thread Status:
Not open for further replies.
  1. MuShoo

    MuShoo Forum Member

    Messages:
    26
    So I'm a relative noob at Reaktor 5 - been using it for about 2 weeks now. However, I'm very good at Max/MSP/Jitter, so most of the concepts aren't bothering me too much (though I hafta say, Reaktor is the strangest way of thinking I've come across to date).

    Anyway, my longterm project is to create a dbGlitch clone in Reaktor, with some of my own tweaks. Currently I'm... not very far. I have about half of the tape-stop effect completed.

    But, I took a break from it because I was getting somewhat frustrated at the lack of some of my most-used Max/MSP plugins (namely a Scale macro, and an Autoscale macro). So.... I built them.

    Scale is very simple, you give it your input range, your output range, and an input stream, and it does all the work.

    Autoscale is a bit different (and still needs a little work). It analyzes the stream of input events, and stores the maximum number and the minimum number in separate event tables (easiest way to store data I could think of). It then uses those values to define it's input scale, while you define the output scale.

    The problem with it is that if there are spikes in the data, like a jump from 1 to 100 that never happens again, the '100' value is still stored as the maximum input range, and your output scale gets all wacky.

    So... anyone have any ideas how to make the autoscaling min/max inputs slowly fall back towards zero? I've attached a copy of the macro.
     

    Attached Files:

Thread Status:
Not open for further replies.