Posted
Is it perhaps possible to route one MIDI port/controller to one track, and another to another track? I assume this is not possible, and that would be OK. Just checking whether perhaps I missed something in the docs, because in the current project such a feature would help me.
Thanks!
Di., 22.04.2025 - 18:27 Permalink
I assume you are talking about input?
All input ports go to the current midi through target (the selected track). Only exception is a port that was tagged as control surface which goes to remote control.
Di., 22.04.2025 - 19:20 Permalink
input
Sorry for not being clearer, yes I am asking whether it is possible to have MIDI input from different controllers routed to different tracks (e.g., having keyboard 1 playing the instrument on track 1; and keyboard 2 the instrument on track 2).
No worries if that is not possible. For now, I am just trying to use a standard DAW like Cubase for such workflows.
So., 27.04.2025 - 11:38 Permalink
Thanks. In this case, I am using one MIDI keyboard as a controller to change on the fly the tuning of instruments played by another keyboard (via MTS-ESP, https://oddsound.com/mtsespsuite.php ).
No worries, I can try things out in realtime with another DAW that supports routing specific MIDI ports to specific tracks, and then in Synfire I can edit tracks accordingly in non-realtime. After all, playback including retuning then works just fine in Synfire.
Mo., 28.04.2025 - 09:45 Permalink
Wow, this Oddsound utility looks awesome. I can only imagine what a challenge it must be to deal with all the oddities and intricacies that are involved with micro tuning.
Does it send/receive sysex or CC data? Maybe Synfire could handle its data stream as a controller so you can record both alongside each other.
Mo., 28.04.2025 - 10:28 Permalink
In a nutshell (AFAIK), by default OddSound MTS-ESP communicates via some global tuning table, which all currently used instrument supporting it (which are quite a few already, including many big names) read in order to dynamically update their tuning during the course of the music. So, Synfire already works well with it, no need for any custom support.
I am using the OddSound Master plugin in a separate Synfire track and use standard MIDI events like notes and CC to change global tuning settings on the fly, and all the instruments are then automagically retuned.
Beyond this default native mode, there are also some alternative communication modes with instruments not supporting this MTS-ESP protocol natively. For example, any instrument supporting MPE can also be used by having a special MTS-ESP MIDI FX plugin "massaging" the MPE MIDI stream. To have this working in Synfire (which does not support MIDI FX plugins) I am using plugins that are also hosts (like Unify or BC's Patchwork), and this host plugin then hosts both the OddSound MTS-ESP MIDI FX plugin (preprocessing MIDI) and the actual instrument, and perhaps further FX plugins for good measure. Again, this also all works with Synfire, no need to have MPE MIDI data already as input coming from Synfire.
In another DAW with actual MPE support, this approach can also be used with data from an actual MPE controller, and then this MIDI FX plugin also still works and just changes the pitchbend information as required (once it is set up correctly). Now, this is not possible with Synfire. Synfire does not yet support MPE, as Synfire does not support multiple MIDI channels per track, AFAIK.