Configuring the Ion to receive MIDI commands

I'm trying to get the Ion to receive a MIDI input from Max/MSP, and despite following the instructions in the manual the desk doesn't seem to be responding to the signal.  We've tried using an MSC command in Qlab as well, but that doesn't seem to be making a difference.  I've set Show Settings to Enable the MSC Receive and set the MSC Receive Channel to 1 (the same in Max/MSP and Qlab, but it doesn't seem to receive the signal.  The signal is reaching the Midisport port, but not getting any further than that!  We've tried swapping the cable to the desk, but that hasn't made any difference.  Anyone got any ideas of anything else we can try? 

 

Thanks

 

Louise 

  • Technically speaking, midi channels are numbered 0 to 15, but some programs use 1 to 16.Maybe try using channels 0 or 2 or a combination in ion and max. Moreover make sure that the numbers for ACN midi Rx and Tx ID in setup > show control, match the numbers in Shell > settings > local I/O. MSC works across cue lists. Are you sure the specified cue in the specified cue list exists?
  • This brings up a good point/gripe. Why does the Eos system use completely non-standard and confusing names for the MIDI settings? What's wrong with calling them MIDI Channel and MSC Device ID? Not to mention using the actual numbers of 0-15 and 0-126? It seems like it just makes everything more complicated as we then have to translate real world MIDI to Eos MIDI...

  • uhm, Eos does use the numbers system as specified by the standard. channels are numbered 0-15 and the device ID 0-126. the MIDI Channel is not exposed as a setup setting, so there is no label for it anywhere, except at one single point in the Help system (where it's actually called Channel). the only thing labelled differently is the MSC Device ID which is MSC Receive Channel and MSC Transmit Channel.



    [edited by: ueliriegg at 2:05 AM (GMT -6) on Sat, Jun 14 2014]
  • Hmmm. In checking now, I seem to have been mistaken in the past. Apologies for the confusion. That being said, why add the extra confusion by using the term MSC Rx Channel, an already specified term, for the Device ID?

Related