Difference 1 : Virtual Mappings are “safe”
Loopbacks are potentially dangerous, cos you can get into infinite loops if you’re not careful with filters.
Midihub Virtual pipes were always designed so that any chain could not branch back to itself…
…so loops are impossible.
(only Virtual pipes not in the chain are allowed)
“safe?”…
...yet to be decided:
It might be just possible for a mapping event to create an event feedback cascade.
I’ve tried and failed but not yet convinced myself that this is impossible.
Hopefully another user can settle this issue.
TBD
\
Difference 2 : The number of Virtual Mappings “stages” is limited
Sometimes, an event passing through one pipeline needs to map to a Virtual I/O and go on a new pipeline for further manipulation and then to a new mapping…
…and so on.
Each time you do this, a Virtual I/O is “used up”.
With Loopback, as long as you could keep track of the filters there is (was?) no such limit.
My hunch, however, is that
-
Most virtual mapping scenarios won’t push this envelope, and
-
Some old loopback patches may well be simplified in translation to virtual mapping presets