MIDI-OX User Forum - Print Page


    
      
        MIDI-OX User Forum
        (http://www.midiox.com/cgi-bin/yabb/YaBB.pl)
      

        MIDI-OX >> Questions and Discussion >> Custom port names not sticking with physical ports
        
(Message started by: chrisfostertv on Jan 11^th, 2012, 3:42am)

Title: Custom port names not sticking with physical ports
Post by chrisfostertv on Jan 11^th, 2012, 3:42am

Setup:

Motu Midi Express 128 (USB) x 4 (Latest 4.0.4.8697 drivers)

2 x Echo AudioFire12 Firewire audio interfaces with 1 pair of Midi Ports

1 x ESI @Julia Audio card with one pair of Midi ports

Various hardware Synths, controllers and FX

Windows Vista (Latest SP2 Build)
MidioX 7.0.0.365 32Bit
Reaper DAW

Problem:

The custom port names are not following the actual midi physical ports after a re-boot/ when USB cables are rearranged on the computer side.

This means all the 'Midi Port Routing' are misconfigured.

Info:

4 identical Midi patch bays that Midiox names as

Express 128: Port #
2 - Express 128: Port #
3 - Express 128: Port #
4 - Express 128: Port #

Device manager reports the four units as 'Motu Midi Device (WDM)'

So I identify all the equipment hanging off each port and 'custom port name' accordingly.

Then what seems to happen, is Midiox (or the Motu Driver reporting to Midiox) decides to rearrange the devices so that the routing are no longer correct.

At present, 'Device Manager/ USB Serial Bus Controllers' reports the devices as:

Port_#0001.Hub_#0001

Port_#0002.Hub_#0001

Port_#0001.Hub_#0007

Port_#0002.Hub_#0007

I guess this is dependent on the physical usb ports the devices are plugged into and is possibly the info that Midiox is utilizing?

Network interfaces have hardware MAC adresses which are unique to each device, but maybe USB Midi Devices do not have such a scheme and can only be recognized via firmware/ and physical USB port ir there are identical devices.

Is it going to be the case, that I will need to label every USB cable and physical port as to ensure correct port routings in Midiox?

Title: Re: Custom port names not sticking with physical p
Post by 4x4uk on Jan 11^th, 2012, 4:17pm

its aknown issue see the bug reports

Title: Re: Custom port names not sticking with physical p
Post by chrisfostertv on Jan 11^th, 2012, 10:08pm

Thanks for the reply.

"I noticed the "Customize Port Names..." function doesn't remember the names upon restart in MIDIOX's latest version, 7.0.2

It seems to work fine in version 7.0.0 "

So yourself and bichuelo who reported this bug are using the 'Beta 2010' release and confirm that this particular issue was not apparent in 7.0.0.365

I think the issue I have, is maybe more related to having 4 identical and dumb midi boxes, connected via usb as the custom port names are sticky, but get assigned to the wrong hardware should a reconfigure of USB cables occur on the PC.

My guess is that Midi-ox only knows how to distinguish between these identical midi boxes via the physical USB port ID.

It's not a deal breaker, but if Jamie could confirm this as a limitation rather than a bug, I will colour code all USB cables and USB ports on the PC to save my hair..

I'm not sure how hardware musicians got by, before MidiOx came along, the ability to route controllers to sound sources is brilliant.

Title: Re: Custom port names not sticking with physical p
Post by 4x4uk on Jan 12^th, 2012, 6:03am

they used to use physical hardware routers