Replies: 1 comment 2 replies
-
Velocity as a motion sequence I think I can do at some point. It should just need pointing the motion sequence function at the velocity data (maybe). Using the groove function instead could allow setting the depth of velocity modulation. I had a motion sequence outputting as MIDI CC at one point but it needs a lot more work before it's useable (if it ever is). Motion sequences are interpolated 96 ticks per step, which caused a crash. Jamming assembly instructions into time critical code is asking for trouble. Sending LFO as MIDI would face the same issues. I'm not sure recording them to the sequencer is worth trying. Motion sequences record only one value per step, so only slow modulations can be recorded with any accuracy. It may be worth it for the event recorder where everything is timed to the ms, I haven't looked at how it works yet. I will do some work on the modulation section. There will be a sine wave LFO and I'll try to make things like key sync configurable via SysEx. |
Beta Was this translation helpful? Give feedback.
-
So to me one of the biggest missed opportunity of the electribe 2 is putting the modulation "post sequencer"
So what I wish korg had done was simply allowed the MODULATION section to output midi. Then you could motion record the modulation and move to the next modulation.
So I have worked around this with pure data or axoloti to send lfo to midi cc and then record it in on the electribe. Also would be nice to have velocity as a modulation source. Ie velocity to filter cutoff. Once again I work around this with pure data.
Also huge would be motion record midi cc out!!
If possible. 🤞🏽
Beta Was this translation helpful? Give feedback.
All reactions