Core duplicate filter events

gentleclockdivider
gentleclockdivider Member Posts: 183 Helper
edited September 30 in Reaktor

The core duplicate filter module (from reaktor 5 core ) filters out events with the same value as the previous one , only letting value through which differs from the previous
So when feeding it a square, the ouptut shoud be a spike when going from high to low , no ?

But the result remains a square

Comments

  • colB
    colB Member Posts: 936 Guru
    edited September 30

    When the steady value is -1, and a 1 arrives, the 1 is different, so the filter lets it throught…

    …after that, there are loads of 1s that are blocked by the filter, but the last value at the output was a 1, so it stays at 1….

    …until a -1 arrives. It is different from the last value, so the filter lets it through. Now the value at the output is -1…

    After that, there are loads of -1 at the input which are all blocked by the filter… but the last output there was a -1, so that stays until a different value arrives… then it will change to that new value…

    so you still get the good ol' square, just not an event at every tick…

    When this is pushed to the output, it will re-clock it with the audio clock

  • gentleclockdivider
    gentleclockdivider Member Posts: 183 Helper

    yeah , makes sense

    difficult to debug though

  • colB
    colB Member Posts: 936 Guru

    that's because there is no bug - everything is working correctly ;)

  • gentleclockdivider
    gentleclockdivider Member Posts: 183 Helper

    quote

    after that, there are loads of 1s that are blocked by the filter, but the last value at the output was a 1, so it stays at 1

    unquote

    Not a bug but verry hard to find out that 1 is the last value and not a stream of new numbers

  • Studiowaves
    Studiowaves Member Posts: 615 Advisor

    If you want to verify it use the merge. Apply this to the bottom and send an audio clocked signal with values other than 1 or -1 to any inputs above it. The bottom of the merge gets priority. So send in a low frequency square wave to the bottom thru the event filter and watch what happens on the output of the merge. The top events should pass thru and the bottom event will only pass when it changes value. That's how to find out.

Back To Top