|
|
|
|
|
|
Q:
MOTU Issue: Beat clocks and tempo hiccup when playing back in memory cycle mode
A:
This FAQ deals with the setting "First Clock is Time 1 (not time 0) in the Basics menu/Transmit Sync window. This setting can be enabled for older tempo based MIDI devices that require a special start message sent with beat 0.
For newer drum machines, hardware sequencers and other MIDI instruments with tempo sync options this setting enabled can be problematic at the start of a sequence. The start message can stagger the tempo at the beginning as the true tempo of the Beatclock message is not sent with this start message. This is especially problematic when using the memory cycle option in the main transport window. You may have a 4 bar MIDI Bass line sequenced in Digital Performer and you would like to sync a drum machine to this Bass line by transmitting beat clocks. At the same time you would like to have the Bass line repeat using the Memory Cycle option in the main transport window. If you run into a hiccup or stutter at the memory cycle's beginning, go to the Basics menu/Transmit Sync window and disable the "First Clock is Time 1 (not time 0)" option.
Other Popular Articles:
MOTU Issue: Why can't I choose custom colors in DP? MOTU Issue: Where is my "Remove Duplicates" Plug-in or my Plug-ins folder? MOTU Issue: Printing text on single pages with Quickscribe MOTU Issue: Why am I having trouble with my QuickTime movie in DP? MOTU Issue: Custom brush patterns in the Drum Editor |