by CaBleman » Tue Oct 03, 2017 12:11 pm
Richard, all I mean is why you limit the MIDI target selection in Aerodrums to outputs only...
If you listed inputs as well, users could setup the routing to their discretion, often w/o a MIDI looper.
Example: assume an audio interface has MIDI IN and OUT. Both ports are registered ans Windows and available for third party. The MIDI Out port is usually being used to pass it to other hardware. Yet the MIDI IN port is usually used to get MIDI data from a MIDI generating device...
Now Aerodrums actually could be considered as such a MIDI generating device - it is a software, yes, but would you not naturally connect it to a MIDI IN port of your system to then route this to your VST Instrument in a DAW?
I don't get the idea why Aerodrums only sends to MIDI Output ports of a system, unless one would like to drive hardware drum extenders through that. To drive software instruments on the same system, an EXTRA routing or loop software is needed to achieve that. If Aerodrums would be capable to select MIDI Inputs of the host system as a sending target, all would be fine and much more flexible... is is clearer now?
Thanks for listening, CaB