I've just completed an alpha firmware release that implements MIDI clock. I haven't added any of the other 1.4 features yet, but MIDI clock involves some drastic changes and I wanted to get it tested ASAP.
Even if you're not using MIDI clock, I could sure use the help in testing this to make sure I didn't break the standard MIDI sending & receiving code.
There's a new parameter in the MIDI settings menu: MIDI Clock. It can be set to off (the default), slave and master.
If MIDI clock is set to slave, it just passes any incoming clock data out its MIDI outputs. For example, clocks coming in from USB will be passed out the MIDI output. Clocks coming in from the Remote In will be passed out both the MIDI output and the USB port.
If MIDI clock is set to master, the current tap tempo rate is sent out both the MIDI and USB outputs.
I've tested this in the following ways:
- Master mode to an Eventide Timefactor
- Master mode to Apple Mainstage
- Slave mode, passing clock from Mainstage to the GT and on to the Timefactor
Please let me know how this works for you - bug reports and feature requests are welcome!
Even if you're not using MIDI clock, I could sure use the help in testing this to make sure I didn't break the standard MIDI sending & receiving code.
There's a new parameter in the MIDI settings menu: MIDI Clock. It can be set to off (the default), slave and master.
If MIDI clock is set to slave, it just passes any incoming clock data out its MIDI outputs. For example, clocks coming in from USB will be passed out the MIDI output. Clocks coming in from the Remote In will be passed out both the MIDI output and the USB port.
If MIDI clock is set to master, the current tap tempo rate is sent out both the MIDI and USB outputs.
I've tested this in the following ways:
- Master mode to an Eventide Timefactor
- Master mode to Apple Mainstage
- Slave mode, passing clock from Mainstage to the GT and on to the Timefactor
Please let me know how this works for you - bug reports and feature requests are welcome!