Virtual Inputs/Outputs
Without these, we would only have simple In → Out pipelines:
Virtual Inputs/Outputs allow us to do more complex branching
(from this tutorial)
by giving us copies of the event streams which we can bring together as we choose and use filters to split a stream for different purposes
Virtual Mappings
A common request from users was for mappings to be scale-able, ie. to take the MIDI CC/Note value/velocity to be used for a mapping and modify it.
@Giedrius built this into the firmware about a year ago.
Until then, none of the techniques mentioned in the (unfinished) Virtual Mapping Techniques topic were possible without resorting to physically patching a cable from Midihub back to itself.
At its simplest,
- if the full range of a CC is OK for your needs, it’s fine to use a “traditional” mapping from a physical port
- if you want to your mapping to be based on some CC/Note you modify within Midihub, use a virtual mapping