With the upcoming release feature-frozen I’ve started to think about future features.

I’ve implemented an experimental feature to allow IanniX to be slaved to an external midi sequencer or video editor using MIDI Time Code and MIDI Clock. The master’s transport provides the time base and controls start, stop, rewind, etc.

The IanniX user interface to enable or disable this is a button to the left of the transport slider (below the fps display) that brings up a menu where the sync type can be selected and in the case of midi clock, for the host tempo to be entered.

While slaved IanniX plays scores normally. The IanniX time display updates normally but echos the master’s time. The start/stop transport control is locked.

I have this fully working now with support of midi time code, midi clock and song position pointer. I’ve tested with Ableton Live for midi clock and with Numerology for MTC and it seems to work fine. These features should also allow control of IanniX with an external hardware sequencer.

The menu (and internal design) also provide for an option for slaving to a host using Open Sound Control. However I’m not aware that there is a standard for messages for remote control over OSC, or if anyone would use this feature if I implemented it. Is anyone aware of this being implemented elsewhere and if so what is the message format?

In the absence of an existing standard I propose to support OSC master-sync with a stream of messages to IanniX such as:

/iannix/timesync
/iannix/timesync
..
..

Where is a floating point number. IanniX would track the time.

Comments?

– Chris