MIDI

MTC (MIDI Time Code) is an incoming timecode signal that uses MIDI as it's transport. You receive this timecode from another device and put together a list of what should happen at what time. You can also, whilst timecode input is present, learn the cues/subs/macros and they will be put into the list. Note that you can also run an internal clock to do all of this, but it is not transmitted out - it is only with the Ion.

MSC (MIDI Show Control) contains standardised incoming MIDI signals (SysEx) for GO, STOP, BACK, FIRE, and like that. Ion can listen and respond to these incoming signals as well as generate them for other devices to listen to.

So....it really depends on what else you have and what you are trying to do! You may want to look at using an internal clock to play the Ion cues in exactly the right place - similar to Follow/Hang but ultimately a lot easier to manage, as a change to the timing of Cue 6 doesn't affect that of Cue 55!

-luke-

MTC (MIDI Time Code) is an incoming timecode signal that uses MIDI as it's transport. You receive this timecode from another device and put together a list of what should happen at what time. You can also, whilst timecode input is present, learn the cues/subs/macros and they will be put into the list. Note that you can also run an internal clock to do all of this, but it is not transmitted out - it is only with the Ion.

MSC (MIDI Show Control) contains standardised incoming MIDI signals (SysEx) for GO, STOP, BACK, FIRE, and like that. Ion can listen and respond to these incoming signals as well as generate them for other devices to listen to.

So....it really depends on what else you have and what you are trying to do! You may want to look at using an internal clock to play the Ion cues in exactly the right place - similar to Follow/Hang but ultimately a lot easier to manage, as a change to the timing of Cue 6 doesn't affect that of Cue 55!

-luke-