This is a mono midi sequencer. The available features for this sequencer are:
Pitch and Velocity patterns can be configured with the knobs in the top left panel of the UI. The Gate buttons in the bottom left section are used to set which steps are activated.
Clock Mode supports a Trigger mode! Press the Trigger button to proceed to the next step. Host Sync and Free Running modes are also supported. Like in the Step Seq x42 plugins Free Running follows the BPM parameter of the plugin.
The Order parameter changes the order of the steps. Forward, Reverse, Random and Shuffle are the different modes available. Shuffle is like random but without repeats.
You can dynamically set the number of steps of the sequence. So with two instances of this sequencer you could create polyrhythmic patterns.
Repeat Mode supports a Legato and Retrigger mode. Legato ties notes together when a note is repeated. Retrigger will send a note off followed by a new note on
Step duration can be set to whole notes to 64th notes.
I’ve tested the plugin on my mod dwarf. The trigger button allowed to move between the gate. It is very nice ! Is it possible to have the number of the Gate on the Mod dwarf and another Trigger to open or close the actual gate ?
That’s very promising ! Thanks for your work
@Remy_D I need some more specific info about your feature requests. Do you mean you’d like to see the step number on the Dwarf device display? And could you clarify what you mean by a Trigger to open or close the actual gate. Because all separate gate buttons are assignable
You re right.
You press the trigger to choose the gate. The number of the gate appears on the mod dwarf.
Then You press another switch to open or close the gate You re on.
Is it ok for You ?
Allow to define the MIDI Channel independently for each gate (I think that there are use cases for this feature, I just can’t figure out if they are sufficiently common to justify the proliferation of ports)
Allow to define a combination of MIDI Channels for each gate (I think that this could be fun, but I guess that it would be complicated to make the parameter simple enough to not be confusing… It would be a parameter to choose among 65.535 combinations…)
The MIDI Panic trigger makes sense. Even though I think needing a panic button also indicates the plugin doesn’t function optimally. Have you run into needing a panic button already? Can you let me know when you do?
I have actually thought about per step midi channel configuration! Like you said, it means even more ports. Which kept me from adding it for now. But I’ll think about it some more. Would anyone else here like to see this feature?
A similar approach as the Tetr4 Switch could work I guess. But I think keeping it one channel per step (2) keeps it a bit more comprehensible
I once made a request for more functions of a sequencer. Sequencer with more functions? There are cirklon-manual-1.20.pdf a lot of nice ideas listed there about what can be musically interesting. Not everything has to be realized, but if you have one or the other idea ~easy to program it would be a dream.
Use 14 bit instead of 7 bit for MIDI.
A MIDI input as well as an additional gate/CV (in/)out would be cool.
By 14 bit, do you mean pitchbend CC? Or can you have 14 bit ranges on other midi messages too? And would you like to be able to sequence CC instead of midi notes in general too?
How do you expect MIDI Input to be processed?
And I think having CV input and output could be nice. I’m not sure how to map the output to CV though. Would the Pitch CV be mapped to -10V to 10V, should it be configurable?? The less controls the better in my opinion, unless it’s needed.
No promises on my side by the way. But I think it’s nice to gather these ideas and see what can be done.
As I said, these are ideas and I don’t expect anything. Keeping the plugin as simple as possible makes a lot of sense KISS principle, I fully agree. Maybe you can split it into several plugins if necessary and plug it together in a modular way, depending on your needs.
Selectable between note or CC$number. 14 bit for pitch bend and other CC values, so you can also use the sequencer to automate other plugins or external devices for the parameters.
MIDI input for example to record notes or CC values or to change them on the fly. Or to adjust a setting in the sequencer (e.g. order, step duration, note length, …)
+/- 10V for notes or CC values. I have no idea whether this should be configurable. That depends on what is technically feasible and sensible as well as the complexity of the plugin. Keeping it simple is a very good approach.
As I said, just ideas, many from Cirklon.
What you can implement is another matter and whether that makes sense/is important for the other users here. Collection of ideas.
The MIDI Panic trigger makes sense. Even though I think needing a panic button also indicates the plugin doesn’t function optimally. Have you run into needing a panic button already? Can you let me know when you do?
AFAIK, its purpose would be to stop other plugins (MIDI generators) to behave incorrectly: this can happen if you quickly change the midi channel while the sequencer is running: the sequencer will continue to send the correct midi message to Midi generators, but sometimes those plugins stuck, perhaps because they miss the note off message.
