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

Bento seq.internal gate time , first gate ..inaccurate timing

Discussion in 'Building With Reaktor' started by gentleclockdivider, Feb 18, 2017.

  1. gentleclockdivider

    gentleclockdivider NI Product Owner

    Messages:
    744
    In bento's 8 step sequencer , when the gate time is set to internal , we have the option to adjsut the gate length.
    Sometimes the first gate has the duration of 2 gates .( when gate percentage is around 40 )
    TRy restarting the clock a few times if it isn't obvious from the first time.
    This happens when clock source is internal or ecternal
    Have a look here
    https://app.box.com/s/3ohz077uxb8t1jtzxlk5neg55oyoaob1
     

    Attached Files:

    Last edited: Feb 18, 2017
  2. mpl

    mpl NI Product Owner

    Messages:
    496
    It uses a timer to count the step time and needs 2 clocks to do it so the first gate is not what you've set,quite a few hardware devices do the same-clock dividers and korg sq1.
    for the sequencer to set a gate time it needs to know the step time,which would normally come from the clock generator, but the block clocks have no step time out
    there was a thread about this when blocks first released
    mike
     
  3. gentleclockdivider

    gentleclockdivider NI Product Owner

    Messages:
    744
    mkay ..

    It doesn't always happen when gate is set to internal , most of the time it does .
    So , there is some kind of variable involved .
    Could you post the link to the thread . ?
    Thanks
     
  4. mpl

    mpl NI Product Owner

    Messages:
    496
  5. gentleclockdivider

    gentleclockdivider NI Product Owner

    Messages:
    744
    SO , bug after all .
    I have built a sequencer in core , 64 steps , sample accurate ..from the first step/gate .

    Need more time to properly turn it into a block ( only on Reaktor 6 since a week , ;).
    I've noticed a lot of bugs/ wrong connections , the va filter macro is wired wrong , ( filter type connection goes into slope , and vice versa ...)