i've been trying to use the M-audio Uno for MSC on the road hog. sometimes it works, but most of the time it doesn't. it is supposed to be hot swap, but i have to restart the console a bunch of times before it works (if it does). is anyone successfully using midi on the road hog? any info is appreciated. i bought an expensive show control program, and spent lots of hours programming it, and can rarely use it. totally bugging me. thanks.
The way the uno works is there are a couple steps..
First, upon the initial connection the device only has enough firmware loaded to be able to talk to the OS and load its normal firmware contained within the driver. Once that occurs, you will see the USB LED illuminated. That means the OS discovered the device and loaded the proper driver and it has uploaded its firmware. This method allows the firmware to be upgraded through a new driver release.
Second, now that the device is running code and connected the Midi In/Out LED's imply the firmware received the midi message. Midi In is just a serial connection and the firmware simply retransmits that message to the driver then it sends it on to the application. Midi Out is the same in reverse.
So to ensure the driver is properly communicating, the application needs to send it a midi out command. If the Midi Out Led flashes then the message made it all the way through the driver and was processed by the firmware in the device.
If you see the Midi In LED flash and not the Midi Out LED means the driver is either not loaded or not communicating. Our application goes through the OS to interface with driver as do all applications.
If the Midi Out LED flashes but the Midi In LED does not flash means it is the connection or source.
Given all that.. When it does not seem to work please try to report back the LED in/out status when you attempt to both midi out and in. Keep in mind you must have both MSC In/Out enabled when you run the test.
We look forward to the results of the test and can hopefully deduce where the problem lies and guide us to a solution.
The way the uno works is there are a couple steps..
First, upon the initial connection the device only has enough firmware loaded to be able to talk to the OS and load its normal firmware contained within the driver. Once that occurs, you will see the USB LED illuminated. That means the OS discovered the device and loaded the proper driver and it has uploaded its firmware. This method allows the firmware to be upgraded through a new driver release.
Second, now that the device is running code and connected the Midi In/Out LED's imply the firmware received the midi message. Midi In is just a serial connection and the firmware simply retransmits that message to the driver then it sends it on to the application. Midi Out is the same in reverse.
So to ensure the driver is properly communicating, the application needs to send it a midi out command. If the Midi Out Led flashes then the message made it all the way through the driver and was processed by the firmware in the device.
If you see the Midi In LED flash and not the Midi Out LED means the driver is either not loaded or not communicating. Our application goes through the OS to interface with driver as do all applications.
If the Midi Out LED flashes but the Midi In LED does not flash means it is the connection or source.
Given all that.. When it does not seem to work please try to report back the LED in/out status when you attempt to both midi out and in. Keep in mind you must have both MSC In/Out enabled when you run the test.
We look forward to the results of the test and can hopefully deduce where the problem lies and guide us to a solution.
