The ribbon cable that connects between the 10-pins header on the Mixtreme card and the 9-pins connector on the bracket needs the following modification: the 4 wires in the middle of the cable need to be cut, at the header connector. If this is not done, then these wires may pick up unwanted signals that could cause Mixtreme to reset, indicated by the display of an error message box. (see picture below for ribbon cable modification).
MTC chase slave and MTC trigger slave are only useful if the application supports ASIO-2 (e.g. Cubase VST, Steinberg Nuendo). In this case, the MTC has to be fed into the MIDI IN port of the Mixtreme 9-pin MIDI connector. (See below for the 9-pin MIDI connector wiring).
"Mixtreme's MIDI input is purely to provide sample accurate sync to MTC when used with VST or Nuendo. This means that the hardware 'chase slaves' to the timecode, and resolves the sample rate directly from the timecode rate. In the ASIO-2 driver the timing is directly passed to VST/Nuendo.With other packages that don't use ASIO-2, it still means that there's no need to use an expensive sync unit (ie. timecode in, wordclock out) to lock the sample rate exactly to the 'actual' frame rate. There's no drift when you use the Chase Slave mode, as Mixtreme's sample rate provides the sync source even when MME or GSIF drivers are used.
Mixtreme's MIDI input can also be used to lock the sample rate to the incoming MTC, even if you use applications other than VST or Nuendo. This means that for instance, if you use Cakewalk, as the sample clock which provides the timing for cakewalk comes from Mixtreme, it will accurately 'chase' timecode as the sample rate of Mixtreme is adjusted smoothly to match the actual frame rate.
The only difference with VST or Nuendo is that through the ASIO-2 driver, they can also get the accurate MTC position from Mixtreme. In other applications this must come from a separate MIDI port."
Mixtreme MIDI connection:
Mixtreme MIDI ribbon cable modification:
