Sequencer example with step edit, user input by keyboard, save on card etc


#1

Hi,
Just a patch example of a sequencer i made for my project.
Its quite simple :
stepSequencerV1b.axp (40.7 KB)
-In record mode you can input notes with your keyboard in step by step mode, you can also insert REST (old school step by step sequencer).

-You can edit steps and insert a note anywhere defined by the step selector. Selecting a step with the radio control play the selected step as well.

-You can transpose sequence and change the number of step.
-you can save preset and load preset on SD card (you have to select a preset number)
-The sequencer is not triggered by a clock but by user input using a midi key for example. This is because i am using a version of this patch with my drummer who do not want to play with a click :smile: So you have to send a gate signal.



AX-101 sequencer
#2

hey! this looks like a more advanced version of what i'm building. For pretty much the same reason!


#3

This looks like a great sequencer. Can't wait to give it a try.


#4

Hi everybody

I am using the stepSequencer from sovietpop, mainly patch seq a. Sovietpop you've done great work! Thanks.
I implemented, that when there is a rest no gate is triggered.

I have a problem with the transpose function. Its not as easy as it looks. The transpose function is not really working. So I tried to solve it. But I gave up.

Can somebody explain me, how a real transpose function can be implemented?


#5

I'm not sure myself as I have only started learning the interface this week but am interested if someone has some insight on how it is implemented.


#6

Hi.
It was my first attempt at creating a sequencer and unfortunately, since im a dad, didnt have time to play more with the Axoloti :slight_smile:
The transpose function is quite simple. It take the note value from the table and add the input note value so the output is always the actual note value from input keyboard + note value from table .
I did another version because REST value cause problem (the implementation is wrong in the actual patch).
I will take a look this weekend.