Sequencer with a twist (in Primary)

https://community.native-instruments.com/discussion/comment/19007#Comment_19007

well dear friend, there is no "should do as this, or that", as far as something is working perfect 😋 ...and it is working perfect!

...check by yourself: https://www.native-instruments.com/en/reaktor-community/reaktor-user-library/entry/show/14527/

Here's a simple example using selector/scanner...

sequencer variable restart.zip

Should be easy enough to extend this

https://community.native-instruments.com/discussion/comment/19021#Comment_19021

Any questions about how it works, just ask!

Mostly I avoid Primary, but in general, it's all about order, value and merge modules. The separator is also very useful, more so than compare in many situations, because compare gives logic outputs whereas separator compares, then passes the input to an output based on the outcome.

The Freq. divider is just a simple way to make the midi clock usable for driving the sequence.

Yes you can use it (in general, anything on the forum is fair game IMO, if it's in the UL or elsewhere, then definitely ask permission... IMO of course - everyone else has their own opinion on that stuff), it was a good exercise - more fun than a sudoku ;). The only sticky bit was getting the lamps to turn off - the logic for that is quite nice.

All comments

As a simple solution, try to use an ST Gate (Monophonic single-trigger source) instead of a typical Gate

There must be some reset logic where the sequencer checks if a counter is greater then or equal to 16 (for a 16 step sequencer), then it will jump back to the start position. If you stick in a clipper at that point you can force the start position to never be less than your desired reset position... probably ;)

EDIT: not with the blocks '8 STEPS' sequencer. That is based on a modulo counter, so it doesn't do a compare/jump to restart when it gets to the end.

I'm sure there will be sequencers out there that do have restart logic that can be modded this way - there are some useful features that just wont work with a modulo based wrap. E.g. having separate modulatable start and end points for the sequence - there are some hardware step sequencers that have this, and there is at least one generative technique that depends on this feature (I read about it and wanted to try it, but I cant with my rig - Doepfer have a sequencer that can do it if you use the extra expander...) In this case for your idea, A trigger sent on the last step could feedback a level to the start position. You would reset this on song start. Doesn't help though because I don't think there is a sequencer in Reaktor that does this... although there might be something in the UL?

Maybe easier to build your own though? As long as its a very basic sequencer based on selector scanner or similar?

https://community.native-instruments.com/discussion/comment/18972#Comment_18972

Thank. But this circuit doesn't reset the counter to a number different than 1 or 0. I need the reset to be let's say 4 or any other number within the range of the sequencer steps. Also the modulo module (hehe) should be connected to the sequencer using the 'Mod' output, not 'Div'.

https://community.native-instruments.com/discussion/comment/19007#Comment_19007

well dear friend, there is no "should do as this, or that", as far as something is working perfect 😋 ...and it is working perfect!

...check by yourself: https://www.native-instruments.com/en/reaktor-community/reaktor-user-library/entry/show/14527/

Here's a simple example using selector/scanner...

sequencer variable restart.zip

Should be easy enough to extend this

https://community.native-instruments.com/discussion/comment/18978#Comment_18978

Yes. The logic behind this is obvious. But I don't know how to reset the counter to zero at the first run and to the selected number in all other runs. Also, the Clipper doesn't work since it sends the lower value several times until it reaches numbers within the loop range. It clips the end value of the loop accordingly.

https://community.native-instruments.com/discussion/comment/19007#Comment_19007

I'm sorry, it wasn't polite. But I tried your approach and it didn't work. Going to check the JP 8000 ;-)

https://community.native-instruments.com/discussion/comment/19014#Comment_19014

Oh, so many modules I don't know, or use!!! :-D Thank you so much! This is exactly what i was searching for.

May I use your work in my ensemble giving the credits to you?

https://community.native-instruments.com/discussion/comment/19009#Comment_19009

Wow, are you for real?

The OP asked for a solution for a specific well defined problem. Your answer didn't solve the problem. Can't you just accept that?

https://community.native-instruments.com/discussion/comment/19021#Comment_19021

Any questions about how it works, just ask!

The Freq. divider is just a simple way to make the midi clock usable for driving the sequence.

Yes, the Separator was one of the crucial modules I didn't use in any of my previous designs. The same goes for the Merge Module. Thank you so much! Also I have to find out how did you manage to create a feedback loop without the Unit Delay. Reaktor crashes every time I try to do anything like this. Is the Trig Module the key?

And of course, the logic behind lamps... :-D I'm going to investigate it later as soon as I integrate your Macros into my Ensemble.

And thanks for your permission to use it!

https://community.native-instruments.com/discussion/comment/19022#Comment_19022

you are funny! ....and you don't pay attention to the all comments... 😊 my second answer had nothing to do with his original question, but about his comment on my first answer (he wrote: "Also the modulo module (hehe) should be connected to the sequencer using the 'Mod' output, not 'Div'." referring to the configuration on the example in my photo)... and i just answered to him, that it worked fine, for me, not for him!

....it would be appreciated if you should be more careful in the future, before you write meaningless accusations... thank you 😉

https://community.native-instruments.com/discussion/comment/19039#Comment_19039

Nope, you quoted his whole reply, in which the part about MOD vs DIV is just an aside. Whether you meant it or not, it clearly reads as you refusing to accept that your answer didn't help. Maybe not what you meant, but folk can only read what you write, not what you mean.

...it would be appreciated if you should be more careful in the future, before you make a fool of yourself 😉😊