Setup: M-Audio KeyStudio USB Class compliant MIDI keyboard (i.e no manufacturer driver is provided or should be required). iMac Retina 5K 27" i9 OS Ventura 13.1
I want to be able to route the output of a USB MIDI keyboard to a 'black box' virtual MIDI device to apply MIDI mapping etc within the Audio MIDI app - I don't want to have to fire-up Logic every time to simply route MIDI from the KeyStation to another MIDI destination. Simple idea but...
Problem: Audio MIDI setup incorrectly maps the USB MIDI ports of the KeyStudio and shows a device with a MIDI input and no output, not particularly useful for a keyboard (see grab). Because this device is grabbed on USB initialisation, it's not possible to manually add an output port ('add remove ports' and increment is greyed out). Therefore, it's not possible to route the KeyStation MIDI output in the MIDI Studio app. Deleting, rebooting and replugging the device does not clear the problem - it just reinstalls the faulty device mapping.
Observations: This keyboard works correctly with Logic, Garageband etc. and correctly presents itself as a MIDI source in the CoreMIDI API. It also works correctly outside of MacOS in Linux and Windows. Guessing there is a coding error in the Audio MIDI setup app. Apple or M-Audio's responsibility, one implements it with supplied data from the other I guess?
Qs: How does the Audio MIDI app build the MIDI default.mcfg file and would it possible to hook into the process to correct the error? Is there template code existing in the OS that is called when building the default.mcfg file when a device is encountered the first time?
Looked through the docs, lots of definitions but very little information on the process of creating an instance. Any hints welcome.
SMJ