Hi all!
I wanted to sync the fantom with logic 7.2. So I heard about MMC and MTC. I'm still confused how I set it all up in logic and the fantom.
In the fantom you have this menu inside system setup called "Sync/Tempo"
Now I understands MMC takes care of the transport controls, so the fantom G must send MMC signals and logic must listen to MMC signals. I managed to operate logic's transport controls with the fantom, yes, but then here is where the confusion starts.
I understand MTC stands for Midi Time Control. So this takes care of the synchronization of tempo. I am unsure as to who should be the master and who should be the slave. I thought the fantom should be the master, because the fantom is also the one who controls the transport. But when I press play the tempo in logic jumps insanely fast around the tempo it is supposed to be keeping (fluctuations of about 0.01 BPM). So does anybody know the correct settings for this?
totally confused about MMC and MTC
-
- Posts: 1012
- Joined: 19:02, 15 November 2007
- Location: Hollywood, CA
Re: totally confused about MMC and MTC
Most people completely bastardize the term "sync". If you indeed want Logic and the Fantom's sequencer to play at the same time/tempo, yes, you do want to sync. If you want Logic to trigger and sequence the Fantom-G's sounds (a much more common procedure), that has nothing at all to do with sync.
However, if syncing is what you really want to do:
MIDI Clock: Tempo-based sync. Logic must be set to generate MIDI beat clock (done on a per-project basis) and the Fantom must be set to "Slave MIDI". In this case, the Fantom will follow any transport commands and tempo changes within Logic.
Press play in Logic and the Fantom will start automatically.
NOTE: Setting the Fantom to "Remote" means it responds to the SPP (Song Position Pointer) and transport element of the MIDI Clock signal, but it ignores the tempo portion.
MTC (MIDI Timecode): SMPTE (hours:minutes:seconds:frames:subframes) sync. Logic must be set to generate MTC and the Fantom must be set to "Slave MTC". In this case, both devices will play at their own tempo (say, Logic at 90.5634 bpm and the Fantom at 122 bpm), but will still sync up. Therefore, it is not tempo-based.
With MTC, you must first press play on the Fantom, which sorta tells it to wait for MTC. Then press play on Logic, and the Fantom will start.
MMC (MIDI Machine Control): Remote control protocol only. One device can be used to start, stop, fast-forward, rewind, etc. the other, but they're never truly synchronized.
It's not uncommon to use multiple sync signals simultaneously. This was my studio in the late 90s:
1. Press PLAY on a Mackie Digital 8•Bus. MMC remote control commands would be sent across the room to an Akai DR16 hard disk recorder, telling it to start/stop/return to zero/jump to a marker.
2. The Akai would send MIDI timecode to a Mac running Logic (MIDI tracks only). Both the Akai and Logic would have to be set to the same tempo and time signature, as MTC isn't tempo-based.
3. A few ports on my Unitor•8 MIDI interface would send MIDI clock signals to various effects processors for syncing delay times or synths for syncing LFOs.
4. A different port on the Unitor would send MIDI timecode from Logic back to the Mackie D8B for timing reference for its automation.
MIDI Clock is the easiest to deal with. Just set Sync Mode to "Slave MIDI" and you're done. Ignore everything else on the Sync/Tempo page.
MTC is generally considered to be a "tighter" sync, and is used when tracking individual elements into the computer for mixing later (not all that necessary unless you're taking the tracks to another studio).
It's strongly recommended to have your DAW the master. In fact, starting with Logic 8, you can't slave Logic to MIDI clock; only MTC.
However, if syncing is what you really want to do:
MIDI Clock: Tempo-based sync. Logic must be set to generate MIDI beat clock (done on a per-project basis) and the Fantom must be set to "Slave MIDI". In this case, the Fantom will follow any transport commands and tempo changes within Logic.
Press play in Logic and the Fantom will start automatically.
NOTE: Setting the Fantom to "Remote" means it responds to the SPP (Song Position Pointer) and transport element of the MIDI Clock signal, but it ignores the tempo portion.
MTC (MIDI Timecode): SMPTE (hours:minutes:seconds:frames:subframes) sync. Logic must be set to generate MTC and the Fantom must be set to "Slave MTC". In this case, both devices will play at their own tempo (say, Logic at 90.5634 bpm and the Fantom at 122 bpm), but will still sync up. Therefore, it is not tempo-based.
With MTC, you must first press play on the Fantom, which sorta tells it to wait for MTC. Then press play on Logic, and the Fantom will start.
MMC (MIDI Machine Control): Remote control protocol only. One device can be used to start, stop, fast-forward, rewind, etc. the other, but they're never truly synchronized.
It's not uncommon to use multiple sync signals simultaneously. This was my studio in the late 90s:
1. Press PLAY on a Mackie Digital 8•Bus. MMC remote control commands would be sent across the room to an Akai DR16 hard disk recorder, telling it to start/stop/return to zero/jump to a marker.
2. The Akai would send MIDI timecode to a Mac running Logic (MIDI tracks only). Both the Akai and Logic would have to be set to the same tempo and time signature, as MTC isn't tempo-based.
3. A few ports on my Unitor•8 MIDI interface would send MIDI clock signals to various effects processors for syncing delay times or synths for syncing LFOs.
4. A different port on the Unitor would send MIDI timecode from Logic back to the Mackie D8B for timing reference for its automation.
MIDI Clock is the easiest to deal with. Just set Sync Mode to "Slave MIDI" and you're done. Ignore everything else on the Sync/Tempo page.
MTC is generally considered to be a "tighter" sync, and is used when tracking individual elements into the computer for mixing later (not all that necessary unless you're taking the tracks to another studio).
It's strongly recommended to have your DAW the master. In fact, starting with Logic 8, you can't slave Logic to MIDI clock; only MTC.
Re: totally confused about MMC and MTC
Hi The Audacity Works,
thanks for the lecture, this explains alot. I think MIDI-clock is the way to go for me.
So I should slave the fantom to logic with midi-clock, and slave logic to the fantom with MMC.
Again thanks for your help, really appreciated. I am gonna try this setup friday.
thanks for the lecture, this explains alot. I think MIDI-clock is the way to go for me.
So I should slave the fantom to logic with midi-clock, and slave logic to the fantom with MMC.
Again thanks for your help, really appreciated. I am gonna try this setup friday.
Re: totally confused about MMC and MTC
R4uz did you get your transport working? I'm using Logic 8 and I can't figure out how to get the Fantom G's Transport to control Logic...In Sync/Tempo I have:
Sync Mode: Slave-Midi
Sync Output: On
Clock Source: USB
MMC: Master
MMC Output: ON
MTC Sync Output: OFF
in Logic I have:
Transmit Midi Clock checked--destination Fantom
Transmit MTC checked
Listen to MMC Checked
Can you point me in the right direction?
Sync Mode: Slave-Midi
Sync Output: On
Clock Source: USB
MMC: Master
MMC Output: ON
MTC Sync Output: OFF
in Logic I have:
Transmit Midi Clock checked--destination Fantom
Transmit MTC checked
Listen to MMC Checked
Can you point me in the right direction?