MIDI-OX > LoopBe30 > Vienna Ensemble
« on: Aug 12th, 2017, 10:55am »
I have successfully used MIDI-OX as a filter/merge between hardware inputs and ViennaEnsemblePro, until quite recently.
I am now getting VERY bizarre data routings, where a simple one cable route between a PHYSICAL input and a VIRTUAL cable, remaps MIDI data to a completely different physical input. I have described the issue in full on VSL's website, including a step by step for Vienna Ensemble users to test. It could be a simple bug in listing ports, but I am not convinced.
Some images. Here is the MIDI-OX set up, with the hardware devices and virtual ports offered by LoopBe30. You will note a link between ESI port 2, and Virtual Cable 1.
Yet, despite this routing, VEPro6, the active input appears to be the Launchpad!!
Here are the options for the inputs in VEPro6.
So, if I start MIDI-OX first then VEPro6 I get this remapping issue.
If I start VEPro6 then MIDI-OX I get "out of memory" for TWO class compliant USB devices - a Novation LaunchPadS, and an ESI4x4 interface.
I am operating on Win10x64 Creators edition, and most everything is up to date. The bug is repeatable, if I reboot, clear VEPro's .INI file, it mismaps in the same way.
Q. Is anyone else hitting these kind of issues when MIDI-OX is used as a frontend to a virtual and VST system?
Q. Secondly, if there are breaking changes with Win10 and recent updates to the MIDI aspects of Windows...
1 ) Is MIDI-OX going to be updated to ensure it works in a 64bit Win10 world?
2 ) If not, could it be made open-source for the community to maintain it? (Preferred option, GitHub, GPL)
3 ) If this really is the end of the line, can anyone suggest a modern, maintained, retail alternative to MIDI-OX?