The DPS12 can be synchronised with a variety of other equipment through MIDI. For example, if it's synchronised with a MIDI sequencer, any MIDI parts can be played live without having to be recorded. Sync is achieved in one of two ways:

• Sync Master

If the DPS12 is the sync master, it sends out a sync signal from its MIDI OUT port, and all connected devices (slaves) synchronise themselves to the DPS12. This sync signal can either be MIDI Clock or MTC (MIDI TimeCode). As far as syncing goes, always use MTC if you can, it's by far the best way of working. This works irrespective of tempo, so you can have tempo changes right through the song and the sync will be flawless. Always check that the MTC frame rates match between the sequencer and DPS, otherwise the sync will drift (well, the sync is fine, but the effect is that the two will drift apart). Also, don't change sync settings after you've made a start on your song (ie, if you record a bass part at 29.97fps and then change to 30fps, it won't stay in time).

If you absolutely must use the DPS12 as a master with MIDI clock only (say if your sequencer doesn't support MTC), then the tempo is regulated by the DPS12. You must set a tempo map to define the tempo the DPS12 should output clock at, which the sequencer will follow. You won't be able to use tempo changes in the sequencer - these must be defined in the tempo map on the DPS12, which is rather course. Don't change any tempos after you've started recording - if you record a  bass part with the DPS outputting 121 bpm, changing the tempo will mean that the audio and sequencer will drift.

• Sync Slave

In slave mode, the DPS12 listens for an incoming sync signal, and locks its timing to that. You must send MTC to the DPS12 as it doesn't support external sync using just MIDI clock only. In fact, in this mode, it is preferable to send both MTC and MIDI clock. Ths is because in MTC slave mode, you have to press "PLAY" on the DPS12 before it will listen for MTC (the display shows "waiting for timecode"). If you transmit clock as well, the clock start command effectively puts the DPS into play mode for you, so you don't have to keep pressing play on the DPS12 for the sync to work (you'd think the MMC play would do this, but it doesn't...)

Most sync problems are due to not knowing which methods of sync are best and supported by a particular device, and which are active at any one time. MTC is common now among software sequencers, but still might be unsupported by stand alone sequencers or sequencers built into modern keyboards.

• One device should be a master, all others should be slaves.
• Making one device a master usually means turning "SYNC ON", or "TRANSMIT SYNC/CLOCK". In addition, a master should usually be set to "INTERNAL CLOCK", so it's not listening to an external clock.
• Making a device into a slave means putting it into "EXTERNAL SYNC" mode. Usually you will have to specify either MIDI clock or MTC, if the device supports both. If set to MIDI clock, the slave device's tempo settings are irrelevant, as the tempo is derived from the incoming clock signal. If you using MTC, you must set a tempo on the slave device, because MTC has absolutely nothing to do with tempo.
• Many software sequencers have a variety of sync options and settings. Make sure you're transmitting clock when you need to, and that it's being routed to the correct MIDI output.
• MMC (MIDI Machine Control) is not required, but is nice. This basically lets you control transport functions (play, stop, record, locate, record select on tracks etc) from a remote device. If in doubt, turn it off.
• It's preferable to leave a bar or two of silence before the music starts when using sync, as there will always be a finite time taken for all devices to lock together. Use this space to setup default mixer settings, program change all your synths and effects units etc. Don't put any MIDI data right on the first beat at the start, as this might be missed and not replayed before the sequencer locks to external sync.

MIDI Machine Control is a protocol supported by the DPS12, which allows many of its transport functions to be controlled from a remote device. Many software sequencers support MMC, and in addition to start/stop/play/record and locate features, they can also record enable/disable specified tracks. MMC is nice to have. For example, the DPS12 is in MTC master mode, and sends MTC to the sequencer when you press PLAY on the DPS12. With MMC, when you also press PLAY on the software sequencer it sends an MMC play command to the DPS, which starts the DPS12 playing and outputting MTC which the sequencer detects, locks to, and starts playing.

The DPS12 on its own does not offer much in the way of automating mixes - you can save and recall mix scenes, which are snapshots of the mixer's current settings, but not when the DPS12 is playing. However, all faders and pan pots can optionally output MIDI controller data, meaning that in conjunction with an external sequencer, mixes can be automated (changed in real-time while the music is playing).

In order for mix automation to work, your sequencer must be capable of recording and playing back MIDI controller data (most do). On the DPS12's mix setup page, you must enable transmission and reception of MIDI controller data. Now, when you move a fader or pan pot (either real or the on-screen, "virtual" ones), the DPS12 will output those movements over MIDI, which can be recorded in the normal way in the sequencer, and played back. It's a good idea to always do a "send mix data" before the song starts, to make sure all faders etc are at the correct start position for the song. All the "send mix data" button does is transmit the current values of all automatable parameters out via MIDI.

Currently, it is only possible to automate via MIDI the levels, pans, aux send levels and the master level. Akai have said in a future OS version the DPS12 will support MIDI system exclusive access to many other parameters, meaning that those will be able to be controlled and recorded by a sequencer too (hopefully including all control panel and EQ settings).

And now that MESA has arrived, I have access to the sysex commands that DPS12 supports - these will be documented here when I can document them all!

Previous FAQ page

Next FAQ page