Ahh "dark" takes some time...

Is controlling 12mic with midi supported now?

No, there is another tool to be released soon that does this.

Thanks for releasing MIDI Remote 1.80. We've regained full remote control of our M-32 DA and Octamic XTCs.

We were thwarted for several days by the presence of a MIDI keyboard (Roland A-49) that caused MIDI Remote's 'MIDI IO Setup...' dialog to be unusable. Its 'Output' menu was populated with something other than MIDI devices (Item 1, Item 2, Item 3?), and clicking its 'OK' or 'Cancel' button did nothing but flash the button.  We could only set the MIDI ports after we removed the keyboard.

In MIDI Studio, the device name was 'Roland A-49' (with a space and a dash), and its ports were named 'Keyboard' and 'MIDI OUT'.

We've known that when you save a MIDI Remote workspace (.mrew) file with a device or port whose name contains a space, it cannot be correctly loaded because the blank is seen as a delimiter. The full device name is obviously not loaded since we see partial device names in connection failure messages. MacOS often has device names with spaces and special characters, so we quit using .mrew files six years ago.

Yes, 1.81 beta(1) fixes both problems. The 'MIDI IO Setup...' works with the keyboard connected, and we'll save and use .mrew files on our studio and gig computers. Thank you.

MIDI Remote and TotalMix FX understandably interfere when both try to control the same MIDI device. We know to never run them at the same time, but we sometimes forget, causing critical Octamic XTC settings to change chaotically. It would be bad at a live performance.

Could MIDI Remote detect that condition? If so, could it defer (effectively disabling a la 'no response')?

We've never used MIDI Remote at a live performance, so I guess we won't start now