Counter , 0 step always ommited on first play

gentleclockdivider
gentleclockdivider Member Posts: 297 Advisor
edited June 16 in Reaktor


Here I have a counter ( see screenshot one )
It's ramp wave converted to event , reading a table
When the counter is set to 0 , it always ommits the first step (value 0 ) when the sequencer is started for the first time .

The table is correctly read with an order first into rx , then r
I suspect that's because of the values preceding step 0 , whcih are always tiedd to 0

1.jpg 2.jpg


3.jpg

Here's the test ens

testcounter.ens

Comments

  • dreason85
    dreason85 Member Posts: 85 Member

    I think the Set input of the Counter module should not be 0 at the beginning, but -1. And I have found a problem that the G input of the ADSR module is not triggered during initialization, regardless of any value events it receives. This is also why you cannot hear the first step at the beginning. So it is precisely by taking advantage of this that the Set input of the Counter module is set to -1, which initializes the sending of an event with a value of -1. Combined with the processing of the Modulo module, the result is 15, which is equivalent to reading step 16 of the Event Table; I just said that the G input of ADSR does not immediately affected by the initialization event, so step 16 was ignored. So next step is to start from step 1.

Back To Top

Categories