Mixtreme and MIDI
MIDI header and backplate
The Mixtreme and Mixtreme 192 PCI audio cards feature a MIDI header that can be linked to the 9-Pin MIDI port on the back of the second backplate supplied with the card.
The location of the MIDI header is different on the “classic” Mixtreme (original model) and the more recent Mixtreme 192:
The 9-Pin connector on the second backplate must be linked to the 10-Pin MIDI connector (MIDI header) on the card via the attached ribbon cable.
For the “Classic” Mixtreme only, a modification is necessary. Due to the presence of test pins on the MIDI header, the capacitive coupling between the MIDI signals and test pin wires may cause the Mixtreme to reset or malfunction. Therefore the corresponding wires must be cut. They are the four wires in the middle of the 10-wire ribbon cable:
NOTE: There is no need to carry out this modification for the Mixtreme 192.
9-Pin to 5-Pin MIDI connections
The following diagram and table describe the pin connections needed to convert the 9-Pin connection to standard 5-Pin MIDI ports.
NOTE: At the time of writing, no MIDI functionality has been implemented for the Mixtreme or Mixtreme 192’s MIDI output. The only supported MIDI functionality is ASIO-2 synchronization via the MIDI input.
Using ASIO-2 synchronization
The MIDI input can be used for ASIO-2 synchronization of compatible applications (e.g., Steinberg’s Nuendo or Cubase)
The ASIO-2 specification allows for a variation in the Sample Rate according to changes in a MIDI Time Code (MTC) signal received via the MIDI input (Mixtreme, Mixtreme 192) or a Video Sync signal received via the RCA input connector (Mixtreme 192). This is useful for instance when the native audio workstation system is synchronized to an analogue video playback device.
The MTC Chase Slave or MTC Trigger Slave setting must be selected under menu: Settings|Synchronisation in the Soundscape Mixer software.
If “MTC Chase Slave” is selected:
- The Sample Rate varies according to changes in the MTC signal. The decoded MTC time information is passed to an ASIO-2 application where it can be used to guarantee sample accurate synchronization.
If “MTC Trigger Slave” is selected:
- The sample rate does not vary according to changes in the MTC. The decoded MTC time information is passed to an ASIO-2 application where it can be used to guarantee sample accurate synchronization.
|
|