[modstep] - Let's pool our knowledge of it's possibilities and utilise it most effectively

OscarSouth

This recent update has contributed massively to solving the problems we've been discussing. In particular I've had a lot less trouble working with the sequencers and clearly, AU/IAA problems are all but gone now. Three cheers!

Being an optimistic soul, I contacted them with my feedback on the solutions that this update brought, and included a few performance related suggestions for simple functions that I believe would massively increase the scope for Modstep in performance.

1. LOCK/PERFORM toggle, that disables editing in any capacity. I find it way too easy to add to, change and alter a project while in performance.

2. Some way to set a MIDI note to 'play until next note' in the step sequencer (it's very hard to get the notes length just right with the length parameter, especially when the notes are quavers).

3. A 'play with scene' toggle on a clips properties that allows you do designate it to not play with the rest of the scene.

4. A 'mute on scene play' toggle that would allow a clip to run with the scene without sending any MIDI data, so that on activation it would unmute on the next bar line and enter in correct sync with the currently playing clips.

I feel that these simple features would be a huge boost for live performers.

Richtowns

@OscarSouth said:

2. Some way to set a MIDI note to 'play until next note' in the step sequencer (it's very hard to get the notes length just right with the length parameter, especially when the notes are quavers).

I feel that these simple features would be a huge boost for live performers.

I dont perform but I agree, they look like common sense suggestions. My addition to point 2) ...

In the step sequencer the length tab/screen could be made more useful IMHO if there was a snap/grid option and/or an exponential/ non linear scale; half the scale allowing fractional note length changes while the other half offering multiple step length increases.

In my ideal world the snap/grid to lengths would be something like 1/8, 1/4, 1/2, 1, 2, 4, 8. Maybe exponential isnt necessary, maybe a snap/grid of quarter step note lengths would be enough.

Processaurus

I couldn't get modstep to slave to midi clock, when starting anywhere but from the first beat of the first bar. The solution (in Reaper, but may apply to other DAWs) was to, under preferences> midi devices > (port assigned to get pad) "disable song position pointer".

It's a bug where the song position pointer that makes it freak out, and think the bpm is 20bpm or 999bpm.

lukesleepwalker

@OscarSouth said:
This recent update has contributed massively to solving the problems we've been discussing. In particular I've had a lot less trouble working with the sequencers and clearly, AU/IAA problems are all but gone now. Three cheers!

Being an optimistic soul, I contacted them with my feedback on the solutions that this update brought, and included a few performance related suggestions for simple functions that I believe would massively increase the scope for Modstep in performance.

1. LOCK/PERFORM toggle, that disables editing in any capacity. I find it way too easy to add to, change and alter a project while in performance.

2. Some way to set a MIDI note to 'play until next note' in the step sequencer (it's very hard to get the notes length just right with the length parameter, especially when the notes are quavers).

3. A 'play with scene' toggle on a clips properties that allows you do designate it to not play with the rest of the scene.

4. A 'mute on scene play' toggle that would allow a clip to run with the scene without sending any MIDI data, so that on activation it would unmute on the next bar line and enter in correct sync with the currently playing clips.

I feel that these simple features would be a huge boost for live performers.

Excellent suggestions. All of them.