surge icon indicating copy to clipboard operation
surge copied to clipboard

MIDI input quantize

Open ghost opened this issue 4 years ago • 3 comments

From Slack discussion 20200610

Jacky
With tempo-sync'd SEQs, what would be the level of difficulty in some future iteration of Surge, to evolve the code to have an option that quantizes each new voice note-on to whatever clock is selected in the SEQ?

For example, if a SEQ has a base clock duration set of 1/4 note, making it so that when new notes are played from the controller, that the note (can optionally) start and quantize at the beginning of the next 1/4 beat...

As we know, the way Surge works now, it is not possible to have each new voice and note-on quantize to the specified clock duration. Anyhow, just typing this as food for future thought, and it should really be an option between how it works now, and the above described, for in MIDI sequencing scenarios, where one might wish to quantize the MIDI performance note-on events to something other than the SEQ clock duration. Opinions? Drawbacks?

baconpaul
So like a built in quantizer? That’s a cool idea I don’t know any synth that has that

Jacky Yes!

baconpaul I like the idea It’s not in the LFOs - you would have to do it at the entire midi processor level but it would be a cool feature I’ve thought about midi transforms at the input (the midi chord idea is a similar one). I would add both as issues with a brief description and I’ll tag em 1.7.n

Jacky Really interesting to think of that being applied to LFOs too. Will add these to issues. Thanks for the discussion...

ghost avatar Jun 11 '20 11:06 ghost

Like #1737, I really like expanding the nature of the way that surge can respond to midi events. Cool idea.

baconpaul avatar Jun 11 '20 12:06 baconpaul

Basically MIDI input note quantize (doesn't quantize anything except note on/offs). Omnisphere has this separately adjustable for each of its 8 parts, so you can really do some intricate performances.

You don't really want this on the LFO at all, it should be applied on the incoming MIDI events instead.

mkruselj avatar Jun 11 '20 15:06 mkruselj

Link this one loosely to #3675 because it makes sense this way - so that your arpeggiator chord changes hit a downbeat etc.

mkruselj avatar Apr 06 '22 18:04 mkruselj