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.
When sending a command from Qlab to the RH, then the "Midi In" led on the Uno lights up.
After disconnecting/connecting the main power and starting up the console i got the MSC setup finally working. But after that, when i logged off and launched the excising show, it failed. Then i had to launch a couple of time to get it work again.
On this moment it still works, hmm, but i wonder if it does when i need it?
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.
When it does not seem to work: only the LED-in blinks. Mostly after one time log-off/on it works and then both input and output LED's blink when i send a Go-command.
That means it the application driver is not communicating with our application or to the device correctly. Thankfully, M-Audio has recently released a new version of their drivers. We are currently trying to get an image with the updated drivers but on PC they behave as I would expect. Hopefully, we can get you an image to test sometime this week. Would you be up for that?
I have a problem with MSC out of a Road Hog through a M-Audio Uno. Hog3 software version 3.2.1.
At first everything works but after some time (1-2 hours) it just stops working without any obvious cause. Everything is still connected and the Hog is just running cues on a single cue list. But no more MIDI output is generated. (The receiving application (QLab2) doesn't respond and the MIDI OUT led on the Uno doesn't flash anymore. However the slow blinking status LED on the Uno is still slowly blinking.) When I disconnect the M-Audio at this point I get a BSOD an the Hog totally chrashes.
I had a similar problem in 2010 with 3.1.4. with a Uno that every once in a while suddenly stopped working. However that was sending plain MIDI strings - and with totally different hardware (another Road Hog, another Uno from different suppliers).
Does anyone have experiences like this or quite the contrary when working with Road Hog / M-Audio Uno?
Jorg, what version of the Windows XPE are you running? You can find that info under the info tab of the control panel.
Also does the device show up in the control panel midi drop down menu as "Midi Sport Uno 1x1" or "Midi Sport Uno"? This will tell us if you have the newer or older model of the device.
In any case they should both be able to be unplugged and replugged during show operation and still continue to output MSC.
It sounds like like something flakey is going on. Make sure you have the latest v1.8.2 Restore Image on your Road Hog as that will have the latest Uno drivers.
The XPE image version is 1.8.1. Is there any difference between this and 1.8.2. in MIDI drivers?
I was not able to unplug since this caused a complete console crash (BSOD and no more response on mouse and/or keys).
About the exact name of the Uno device I will get back to you asap. (It's a tour now touring with an operator, I just did the programming when it started up. They are touring without MSC since it is considered not show-safe because of this problem.)
Just bringing this topic back up- since the problem was never resolved. (The solution was not using MIDI on the RH, but that's a bit crude.)
Now a new production is coming up that will need a form of MIDI communication between a Road Hog and a computer running Ableton Live. I am wondering if there is any news regarding the stability of MIDI on the Road Hog?
I see the problems described by Abbe, Hans and myself, but no mention of any of them actually solved.
Is anybody succesfully (and more important: repeatedly) using MIDI and/org MSC on the Road Hog (plain vanilla) with the Midisport UNO? If so it would be nice to hear some things about it. Unfortunately a Full Boar is not an option due to availability, so now a certain dull Grey german console is under consideration because of the RH MIDI issues- a solution which I would like to avoid.
There are too many different versions of the uno to reliably say which will work, and which will not.
I believe MIDI Class support was added in the early 3.2.0 releases.
In order for the MIDI to work, on some RH consoles you may need to go into the BIOS settings and enable the on-board "HD Audio" controller and re-install the OS from scratch. The OS won't load the appropriate drivers if it doesn't see the audio hardware.
