Can someone elaborate how this works?


Version 2.6 adds support for third party MIDI over USB devices. In the ECU, you will need to enable their use in Settings>Local I/O>USB MIDI.

I activated it on my @5.  What devices/sources can I use to input midi over USB?

Or link a generic Midi interface I should look at?

6 Replies - Page 1 of 1

  • You can use any USB based Generic MIDI device. I've played with it and a keys/fader/button board. You need to configure show control to receive the messages. New show control list type network. New event MIDI string. This should get you to the MIDI event editing menu in the CIA where you can configure how it will respond to the type of MIDI message it gets. You then also need to configure the Action you want the message to trigger/control. Make sure you take advantage of the diagnostics tab(99) to see what messages the device you have plugged in transmits. I hope this helps you out!
  • In reply to Druuka:

    Hi Druuka.
    I'm trying a little something using a Korg nanokontrol with the eos software myself but I'm still strugling to understand some mechanics. After the above steps you've advised Jason, how would I make the console sync with the faders on the device?
  • In reply to Nandoaza:

    disclaimer: i havent' tried that myself.

    you can get the midi-messages from the nano to eos, but i don't think you can get the faders to move if you move them from within the eos software because Eos doesn't now which feedback to send. but you can get this to work with Luminosus. you can find more info at www.luminosus.org
    and there is a very informative video about exactly your situation here: www.youtube.com/watch
  • Hello,
    you can use your NanoKontrol with Eos 2.6 in USB only to drive events :
    a fader (ControlChange) upper a specific value will fire a Cue a sub or a macro.
    you can't control your subs, just activate it at a state level. to use faders from nano to drive fader EOS, you need to cross to OSC with Luminosus, that works.
  • I’ve got MTC working. You need to use a Windows7 class compliant interface, which does not require drivers to be installed.
    I can confirm the following usb midi interfaces work and receive Midi Timecode into the GIO just fine:
    - ESI Midimate eX
    - iConnectivity mio

    I tried a cheap $8 knock-off from HSI and it didn’t work. Some people had success with it but mine was faulty. I’m using the ESU Midimate eX as I write this, sending MTC from my laptop via a MOTU’s Clockworks software (using their Micro Express midi interface).
  • In reply to Druuka:

    Hey Andrew, as I experienced it, there is a way simpler method to trigger the console via MIDI. Once the USB-to-Midi option is activated in the shell, it will automatically respond to incoming MSC messages (when also MSC receive is activated in the desk settings). Except that you don't need to configure anything. An MSC command with the format <device ID> <lighting general> <go> <cue number> (<cue list number>) will do. In the software I use to send MIDI commands, I can simply put these messages toghter via dropdown menus, no need to convert anything to Hex by hand :).
    The only way to set faders (as Nandoaza would like it) is to use the MSC "set" command, but this only works step-based, not with fades. But to control channels (as submasters) outside of cues, this is a very handy feature, if sudden jumps to a certain level works for you.
Page 1 of 1