Pattern Mode: One of the 16 available patterns can be set/edited or used for jamming.
Song Mode: You can play patterns 1–16 in a loop.
Each pattern can be freely adjusted and repeated up to a maximum of 16 times.
Cool!! Good idea to add the randomize functions
1 Like
I’m not sure because I haven’t really used them, but can you use snapshots for this?
Song Mode with separate steps/steps offset.
Just ideas.
Cheers Dave, will post the template tomorrow. I have been trying to upload a pedalboard so you don’t have to mess with the mapping but I keep getting errors. So you’ll have to do the mapping yourself. The Page selector at the top sends MIDI so it swaps quite nicely from pitch to velocity display. I made 2 templates - one that is full range 0-127 and one that I call Bass that only goes 0-64.
Is there anyway you could make the direction MIDI controllable?
Uploading a pedalboard probably doesn’t work because this plugin is not in the store.
I’m not sure what you mean by direction MIDI.
1 Like
Ah that makes sense about the Pedalboard.
The direction control ie forward, back, random, if it was midi controllable I could have a control on the template or even randomize it too.
Not hugely important but might be cool
Cheers for getting bsck to me
1 Like
Here’s the layouts, feedback gratefully received
https://1drv.ms/f/c/0e39c4016cda07d8/EkYGlzvKk35Bqy9c4QGnItQBcZ2pgqrEtZLc404EKteGrA
Hope the link works out
1 Like
With freely assignable modulators such as LFO 4,5 khz, fast ADSR/DAHDSR, … . 
(Adjustable: Glide Time 0-127, Glide Curve Exp (-64) > Lin (0) > Log (64), Glide Legato, … .)
Glide vs. Glissando
Glide causes the pitch to slide between notes rather than changing in chromatic steps. Glissando provides a “stepped” glide, rather than providing a smooth glide between the start and end notes.
It looks like list controls are not MIDI assignable because it’s either not supported or it’s a bug.
If the list has two elements it is assignable though. But when there’s more than 2 list options it’s not assignable anymore.
You can see the same behavior in other plugins. For instance Fidelity control in the Capo plugin is not assignable. But the Chorus Type control in the DIE Fluid Synth is assignable because it has only two options.
I think Glide is not really applicable in a MIDI sequencer. In a CV sequencer it makes sense. With a MIDI sequencer I’d expect to set glide time and possibly curve on the synth/sound engine you’re sending the MIDI events to.
Thought as much. It’s a shame really as that’s where the fun is with some plugins - shiroverb being a case in point.
Thanks for the sterling work though, really appreciate your plugins. Looking forward to what is next!
1 Like
Tweaked the layout slightly.
Note ranges as follows
Red is 0-64
Green is 64-96
Blue is 0-127
Link for latest templates
https://1drv.ms/f/c/0e39c4016cda07d8/Erb3jqJTIHlBrU1ChUPo3fMBTNKoTBsNWFYUIZJkT2zTHA
1 Like
Another idea 
The external MIDI input can be assigned its own MIDI channel. This allows you to transpose selectively when multiple dm-Seq instances are open.
1 Like
If the synth/sound engine has a glide function, then yes; if not, then no.
If glide could be assigned per step, you could only play a single note in the pattern with glide.
Edit: Ah, that only works with CV control voltage, not with MIDI? Well then.
With these functions, you can create 16 different patterns—MIDI input for record playing $foobar—and run them in sequence.
Quickly edit manually.
Record the steps gate, pitch, velocity, length and gate delay in the pattern.
The values are also displayed in the UI on the right side, everywhere.
Since you can repeat each pattern - each with its own Steps/Steps offset, step duration, order, repeat mode - up to 16 times, you can create a song (Pattern (P)1 once, P2 four times, P3 eight times, …) and with functions such as probability, each pattern can have its own liveliness.
Randomize, Gate delay, Ratchet, Accent, Roll, Flam, … with a separate probability assignment per step.
With freely assignable modulators such as fast LFO (~4,5 kHz), fast ADSR/DAHDSR, … .
Sending MIDI CC.
This allows you to build up or play/control the song – MIDI input for setting the start/end point of the loop – the last pattern is the outro.
If you now have several dm-Seq instances running, you have a (externally controllable (omg)) band.
Control change, program change, pitch bend, aftertouch command.
(
Maybe CV i/o.
Use 14 bit instead of 7 bit for MIDI.
- standard display (0 to 127) MIDI 7 bit range
- decimal display (0 to 100) percent
- decimal display (0 to 1000) promille (recommended for 14 bit types)
- bipolar display (-63…0…+63) MIDI 7 bit range
- bipolar decimal display (-50…0…+50) percent
- bipolar decimal display (-500…0…+500) promille (recommended for 14 bit types)
- binary display (OFF = 0…63, ON = 64…127)
- decimal display (0 to 9999) direct value up to 9999 (recommended for 14 bit types)
MSB/LSB
)
I hardly ever use it.
I just tried snapshots. You can save different sequences, step offset etc. as separate snapshots and then switch between them. You can also control it with a MIDI controller: MOD Web GUI User Guide - MOD Wiki. So you might just give that a go.
I agree that specifying a MIDI channel for the MIDI input is desirable. So I will add that.
1 Like
I’ll give that a try. I’ve never used snapshots before.
Snapshots work surprisingly well. I’ll be using them more often now.
A definable loop of different patterns would be useful in a MIDI sequencer. That’s not possible with snapshots. IMHO
What about
tie - Force the current note to sustain until just after the start of the next step
skip - Skip over this step to the next un-skipped step
?
2 Likes