I’d like to ask if there could be an option to only send the midi notes controlling the pads when pad mapping is enabled (let’s if base note is C4, then only C4 comes as midi out when hitting the corresponding pad)? This would ease integrating with external sequencers while still leaving the possibility to use the Synth as a playing device.
Right now I see no other option than sequencing the Synth’s pads directly in the external sequencer and filtering out all MIDI notes that comes out of the Synth.
Maybe the video in this topic might be of interest to you:
Essentially, i use one of the engines as a MIDI Engine to send MIDI to the external sequencer to build things.
This allows you to use atleast 2 engines for pad mapping and then the last one that you use as a MIDI Engine you can at the end change to whatever you want once you are done with the first two engines.
Let me know if this helps or if you want to talk about best practices other ideas afterwards
I guess I don’t understand the question about mapping; whether you’re sending MIDI IN to the synth, or OUT to an external device. The latter is already what the Synth MIDI engine does, and the former is standard operation if you configure the MIDI.
I’ll rephrase. When you set a synth with pad mapping, you can send midi from an external controller to control the pads (benefit over sending raw midi notes: this triggers smart grid for the”followers”). But when you hit a pad, the midi sent by the Synth is the corresponding midi note. I don’t see any option to send the corresponding pad mapping midi note instead.
