User Forum    :: Powered by YaBB
  « MIDI-OX User Forum - MIDI-OX > LoopBe30 > Vienna Ensemble »
Welcome, Guest. Please Login or Register.
Aug 22nd, 2017, 8:22pm


Home Home Help Help Search Search Members Members Login Login Register Register


   MIDI-OX User Forum
   MIDI-OX
   Questions and Discussion
(Moderator: Jamie OConnell)
   MIDI-OX > LoopBe30 > Vienna Ensemble
« Previous topic | Next topic »
Pages: 1  Reply Reply Notify of replies Notify of replies Send Topic Send Topic Print Print
   Author  Topic: MIDI-OX > LoopBe30 > Vienna Ensemble  (Read 74 times)
s9dd
New Member
*



MIDI-OX Rules!

   


Posts: 8
MIDI-OX > LoopBe30 > Vienna Ensemble
« on: Aug 12th, 2017, 10:55am »
Quote Quote Modify Modify

Hi Folks
 
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.
https://www.vsl.co.at/community/posts/m260864-VEPro--MIDI-port-name-inde x-ISSUE-v6-16178#post260864
 
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.
http://studio.davidcday.co.uk/gfx/vepro/screenshot_16.png
 
Yet, despite this routing, VEPro6, the active input appears to be the Launchpad!!
http://studio.davidcday.co.uk/gfx/vepro/screenshot_15.png
 
Here are the options for the inputs in VEPro6.
http://studio.davidcday.co.uk/gfx/vepro/screenshot_17.png
 
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.
http://studio.davidcday.co.uk/gfx/vepro/screenshot_18.png
 
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?
« Last Edit: Aug 12th, 2017, 11:01am by s9dd » IP Logged
Pages: 1  Reply Reply Notify of replies Notify of replies Send Topic Send Topic Print Print

« Previous topic | Next topic »


MIDI-OX User Forum » Powered by YaBB 1 Gold - SP 1.3.1!
YaBB © 2000-2003. All Rights Reserved.