01-31-2022, 06:46 PM
The short answer is "It's hard to say". Of course we would like to have every device work with the MRCC, but the main idea was to be able to connect a simple MIDI keyboard and route it to all of your devices. it's been a nice benefit that many more complicated devices have also been successfully connected. We may be able to solve some issues if the gear is on hand in the Lab to do some testing, but even then there's no guarantee that the issue is solvable on our end at all. Just because a device says it's MIDI class compliant doesn't guarantee that it is unfortunately. I have a Zoom L-12 Audio Interface/ Mixer/ Recorder that claims to be class compliant, and what to you know, after 2 days of emails with the manufacturer it turns out this audio interface doesn't work with AMD based processors, or whatever. It can be totally frustrating when gear doesn't do what we hope.
Many MIDI issues can be solved, but there are usually 2 ends of the spectrum which control the outcome, money and time. If you have enough time you can solve anything, and for enough money you can basically solve anything, we've been looking for a solution that makes the amount of time needed short while not costing too much money. The solution we've come up with is a 4 in 1 out USB/DIN breakout boxes that would solve many such issues but it's still a little ways down the road.
In the end we have limited control over some aspects of the problem as the MIDI stack we are using (the set of code dedicated to USB interactions) is part of the hardware platform. If we can find what's causing a problem it's possible we can get changes to happen, but they have to happen across the whole of the platform, not just the MRCC, so it's not a trivial task.
Hopefully the 4x1 will provide a sensible solution to the majority of cases where a USB device is not compatible, and DIN ports are already spoken for.
Many MIDI issues can be solved, but there are usually 2 ends of the spectrum which control the outcome, money and time. If you have enough time you can solve anything, and for enough money you can basically solve anything, we've been looking for a solution that makes the amount of time needed short while not costing too much money. The solution we've come up with is a 4 in 1 out USB/DIN breakout boxes that would solve many such issues but it's still a little ways down the road.
In the end we have limited control over some aspects of the problem as the MIDI stack we are using (the set of code dedicated to USB interactions) is part of the hardware platform. If we can find what's causing a problem it's possible we can get changes to happen, but they have to happen across the whole of the platform, not just the MRCC, so it's not a trivial task.
Hopefully the 4x1 will provide a sensible solution to the majority of cases where a USB device is not compatible, and DIN ports are already spoken for.