From the original SynthMaker forum (2004–2014), with its members’ names and dates.
sequencer ·
Hi
I assume that within the MIDI In component (the component where you select what MIDI interface you have, e.g. Keyboard, ESI M4U1, ESI M4U2 etc in my case) the incoming MIDI data is merged together ?
Is there any way that this data can be unmerged within this component (or have the differant MIDI In's as seperate inputs to the schematic) and merged later at the MIDI Output instead.
This might sound somewhat bizarre a request however, I would like to able to "treat" a controller input and a keyboard as completely differant MIDI In's without having to go thru' a myriad of filters.
If this is not possible just now but would be possible in the future, I'd like to request a MIDI UNmerge component and a MIDI Merge component. 😉
jorge ·
sequencer wrote: If this is not possible just now but would be possible in the future, I'd like to request a MIDI UNmerge component and a MIDI Merge component. 😉
What about allowing several instances of the Midi In component? wouldn't that be even better?
sequencer ·
Ah..Forgive my ignorance Jorge. I should have known there would be an easier way of carrying this out. 😊
As an example:
I have MIDI In 1 from a keyboard going through a minimal part of a schematic and coming out on MIDI Out 2.
I also have MIDI In 2 from a controller going to another part of the schematic and coming out on MIDI Out 2.
If I were to create a standalone application would this still be the case for routing ? I am assuming it would be.
Thanks for the help, great response as always.
jorge ·
sequencer wrote: If I were to create a standalone application would this still be the case for routing ? I am assuming it would be.
Good point about the exe export. I guess the Midi In menu on the exported exe would have to allow you to select the Midi devices to use on each of the Midi In components, I think that could become confusing.
Might be better to just change the Midi In component to have a Midi output for each of the Midi devices. We'd have to think of issues related with compatibility with older schematics, maybe leaving the first output as it is now and adding the individual ones under it or creating a new MidiIn component and eventually deprecating the old one.
Your idea to unmerge the Midi events is not bad either and might actually be the easiest one to implement.
sequencer ·
Ok...Thanks for the reply and thoughts Jorge.
My vote (for what that's worth) is for the Unmerge component option to allow maximum flexibilty for routing and to leave the current MIDI In component (at least for a while) for backwards compatibilty.
Hey! That almost sounds like I know what I'm talking about...I'll shut up now.
Thanks Jorge 😀
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker