By stereoroid
Mon Oct 04, 2004 2:04 pm
I've seen a few questions on this, and I wasn't all that clear on it myself until I did some more research, and a few tests with Sonar. I thought I should write up a few words on the topic so it shows up in searches, etc.
Short version: if you have a powerful MIDI/Audio sequencer, like Sonar, Logic, or recent Cubase/Nuendo versions, then they will want to use time-based synchronisation, usually MIDI Time Code (MTC). These sequencers do not (generally) work as MIDI Sync (aka MIDI Clock) Slaves. This will dictate the Master/Slave relationship you set up when you link them to another sequencer like a MPC.
The reason for this is simple once you think about it: digital audio is played at a fixed sample rate, which means that audio playback in a sequencer like this can't follow a MIDI Clock that could vary at any time, without warning. If it did, and the tempo varied, MIDI tracks would go out of sync with the audio tracks. In theory, it could keep them in sync by varying the audio sample rate, but that would be audible (the audio would detune). I've never heard of anyone doing that, nor would I want that to happen.
So, you will generally find that these sequencers will handle MIDI Clock as the Master only. Examples:
- Cakewalk Sonar 2 (Online Help): "When MIDI Sync is the clock source, SONAR operates in response to incoming MIDI messages. In this case, SONAR is the slave, and an external MIDI device is the master. Note that audio playback is not supported when using MIDI Sync with SONAR as the slave."
- Steinberg Cubase SX 3's Operations Manual says (pg 678): "MIDI Clock is not suitable as a master sync source for an application like Cubase SX/SL. Therefore Cubase SX/SL will transmit MIDI Clock signals to other devices, but it will not receive MIDI Clock."
This also applies to audio editors like WaveLab, SoundForge and Adobe Audition. (e.g. Audition speaks MTC only, no MIDI Clock at all.)
Some MPCs can use both MTC and MIDI Clock, so you could make a MPC2000XL or MPC4000 the Master using MTC. (The MPC4000 even supports SMPTE as standard, it's an option on the 2000XL.)
However, the MPC1000 is why the question came up: it supports MIDI Clock only, send and receive, so it will work better as the Slave in such a setup. That is generally not a problem, you don't have to change the way you work. There is no need to transfer audio or MIDI data between sequencers: it just dictates who's the timing master when the two sequencers will work together at mixdown.
Short version: if you have a powerful MIDI/Audio sequencer, like Sonar, Logic, or recent Cubase/Nuendo versions, then they will want to use time-based synchronisation, usually MIDI Time Code (MTC). These sequencers do not (generally) work as MIDI Sync (aka MIDI Clock) Slaves. This will dictate the Master/Slave relationship you set up when you link them to another sequencer like a MPC.
The reason for this is simple once you think about it: digital audio is played at a fixed sample rate, which means that audio playback in a sequencer like this can't follow a MIDI Clock that could vary at any time, without warning. If it did, and the tempo varied, MIDI tracks would go out of sync with the audio tracks. In theory, it could keep them in sync by varying the audio sample rate, but that would be audible (the audio would detune). I've never heard of anyone doing that, nor would I want that to happen.
So, you will generally find that these sequencers will handle MIDI Clock as the Master only. Examples:
- Cakewalk Sonar 2 (Online Help): "When MIDI Sync is the clock source, SONAR operates in response to incoming MIDI messages. In this case, SONAR is the slave, and an external MIDI device is the master. Note that audio playback is not supported when using MIDI Sync with SONAR as the slave."
- Steinberg Cubase SX 3's Operations Manual says (pg 678): "MIDI Clock is not suitable as a master sync source for an application like Cubase SX/SL. Therefore Cubase SX/SL will transmit MIDI Clock signals to other devices, but it will not receive MIDI Clock."
This also applies to audio editors like WaveLab, SoundForge and Adobe Audition. (e.g. Audition speaks MTC only, no MIDI Clock at all.)
Some MPCs can use both MTC and MIDI Clock, so you could make a MPC2000XL or MPC4000 the Master using MTC. (The MPC4000 even supports SMPTE as standard, it's an option on the 2000XL.)
However, the MPC1000 is why the question came up: it supports MIDI Clock only, send and receive, so it will work better as the Slave in such a setup. That is generally not a problem, you don't have to change the way you work. There is no need to transfer audio or MIDI data between sequencers: it just dictates who's the timing master when the two sequencers will work together at mixdown.
http://stereoroid.com/music/mpc1000/ for PGMs, samples, FAQ, and waffle.