06-19-2023, 08:15 PM
(This post was last modified: 06-19-2023, 08:31 PM by Jesse Johannesen.)
So I can't comment on the specific editors referenced above, but if I understand this situation correctly there are 3 probable ways that the editors could work:
1. they use MIDI CC and provide a visual interface in the software.
2. they use a direct USB connection and some proprietary communication protocol
3. they would send SysEx
In most cases I can imagine type 1 should work. No issues sending CCs (Unless they are sent through the MRCC Ctrl channel which filters data to control the MRCC).
Type 2 will definitely not work because the connection is MIDI and not USB protocol.
Type 3 may be MRCC compatible, however it hinges on the Sysex sender being able to limit packet size to 256 byte and include a small delay between packets. This may be the situation by default, but unfortunately we can't know without trying in most cases.
I haven't got either device to test with, but I will take a look around the web and see if I can discover any info on the editors. If you can post me a link that would also be helpful.
I took a quick look at the Editor and found this:
Note to Windows Users: The Minitaur Editor requires bi-directional MIDI communication with the Minitaur via
the Minitaur's USB MIDI connection. However, the two programs (The DAW and the Editor) cannot both
access the same USB MIDI device at the same time, unless you have installed the Minitaur USB Driver. This
driver is included with the Editor download, and requires that your Minitaur is running firmware v2.2.0. If the
Minitaur Editor plugin reports that the Moog Minitaur is unavailable for MIDI Input and MIDI Output (and the
Minitaur is connected and receiving MIDI from your DAW), then you may need to install the Minitaur USB
Driver. Make sure your Minitaur is updated to the v2.2.0 firmware before installing the Minitaur USB Driver.
1. they use MIDI CC and provide a visual interface in the software.
2. they use a direct USB connection and some proprietary communication protocol
3. they would send SysEx
In most cases I can imagine type 1 should work. No issues sending CCs (Unless they are sent through the MRCC Ctrl channel which filters data to control the MRCC).
Type 2 will definitely not work because the connection is MIDI and not USB protocol.
Type 3 may be MRCC compatible, however it hinges on the Sysex sender being able to limit packet size to 256 byte and include a small delay between packets. This may be the situation by default, but unfortunately we can't know without trying in most cases.
I haven't got either device to test with, but I will take a look around the web and see if I can discover any info on the editors. If you can post me a link that would also be helpful.
I took a quick look at the Editor and found this:
Note to Windows Users: The Minitaur Editor requires bi-directional MIDI communication with the Minitaur via
the Minitaur's USB MIDI connection. However, the two programs (The DAW and the Editor) cannot both
access the same USB MIDI device at the same time, unless you have installed the Minitaur USB Driver. This
driver is included with the Editor download, and requires that your Minitaur is running firmware v2.2.0. If the
Minitaur Editor plugin reports that the Moog Minitaur is unavailable for MIDI Input and MIDI Output (and the
Minitaur is connected and receiving MIDI from your DAW), then you may need to install the Minitaur USB
Driver. Make sure your Minitaur is updated to the v2.2.0 firmware before installing the Minitaur USB Driver.