Router Issue

Pan65
Pan65 Member Posts: 3 Member
edited October 2024 in Reaktor

Does anyone know why this doesnt work?

I am trying to make a simple macro to control the decay of a HiHat. The upper part works fine If the pitch is either 66 or 70 the gate goes out trough the G output. But the lower part does not work. It is supposed to select the decay time provided by the Op and Cl inputs, if the incomming pitch is 66 the Cl decay should go trough and if it is 70 the Op decay should go through. But it doesnt, I get the same decay time whatever pitch comes in.

Comments

  • PoorFellow
    PoorFellow Moderator Posts: 5,459 mod

    If you want more people to take a look at something Reaktor layout then it is always a good idea to attach the Reaktor .ens save file both to save other people time but also to make sure that people are looking at exactly the same as you do layout wise !

  • colB
    colB Member Posts: 1,012 Guru
  • Pan65
    Pan65 Member Posts: 3 Member

    @colB

    The Op and Cl are connected to knobs, one for the closed decay and the other for the open decay.

  • colB
    colB Member Posts: 1,012 Guru

    OK, that's the problem.

    Router only route events. KNobs only generate events at initialisation, or when you turn them. So with the knobs just set at a constant value, different note values will change the route, but there are no events being routed, so nothing actually happens.

    What you need is a latch for each knob value that is driven by the note event, that way every time a new note arrives, it also generates an even for each knob, which will be sent through the router. Look up latches in the core manual to see how they work. Best read up on the core even model too ;)

  • Pan65
    Pan65 Member Posts: 3 Member

    Thanks

    That solved the problem, I thought the values from the knobs would be readable all the time without having to store them into latches.

  • gentleclockdivider
    gentleclockdivider Member Posts: 243 Helper

    Knobs can't be read , they send .

    If they would send all the time that would be an immense and needless cpu overhead

This discussion has been closed.
Back To Top