Virtual MIDI not usable as clock/pmap source

[dstroud]

What the issue is:
MIDI system real-time (clock) messages received by the "virtual" RawMidi port are ignored when clock source is set to MIDI. Likewise, control change messages are ignored when mapping MIDI to parameters.

How to reproduce it:
I'm using CyberMIDI (MIDI over OSC) to send clock/cc over IP. These message types are retrievable in LUA via midi.to_msg().

Why it's worth addressing:

• If the virtual port is available as a MIDI clock out destination, it stands to reason that it should be available as a clock source.
• Ability to send MIDI clock has some advantages over Link in, e.g. distinct start vs. continue messages for transport.
• Allowing any script that sends CC to control parameters on-device or over the network via a generic virtual port would be handy.
• AFAIK, the virtual port was initiated as a path towards rtpmidi support but I don't know if that ever came to fruition. I imagine if that work continues, we would want this functionality.

[catfact]

Probably a simple oversight and shouldn't be too tricky to fix if anyone wants to have a go

[dstroud]

Would be rad if so! I'm way out of my depth here, but one thing I noticed working on the related mod is that the virtual port gets added later in the boot process than physical ports (after the "system_post_startup" mod hook). Probably tangential but I figured it's worth bringing up if anyone is interested in a more general effort to close gaps between virtual and physical ports.