![soundplant tempo sync soundplant tempo sync](https://d29rinwu2hi5i3.cloudfront.net/article_media/8cd22ad7-cdb2-4697-bc7a-116bfa46267a/screen_shot_5.jpg)
Instead with Sonar set to the master, you can transmit not only the midi sync tempo, but SPP (song position pointer) for Kronos. Another inconvenience of setting Sonar as the slave to midi sync is always having to press play in Sonar to start listening for midi sync. This way, your audio in Sonar will look correct in regards to the grid set by BPM. If you want the timeline for audio in Sonar to match bars of BPM in Sonar it's probably a lot more intuitive to use Sonar as the master and create your tempos in Sonar and have the Kronos be the slave. So if you record 1 minute of audio in Sonar at the start of the timeline it is always going to be 1 minute of audio regardless of what the tempo is set at. However, audio is HMS (hours minutes seconds). Changing the mode back and forth is inconvenient because it is buried deep in menus.īPM (beats per minute) is midi sync. If the instrument is changed to enable external clock, then the tempo disappears and says EXT.
![soundplant tempo sync soundplant tempo sync](https://i1.wp.com/media.boingboing.net/wp-content/uploads/2019/08/sale_19873_primary_image_wide.jpg)
It is less convenient, because the tempo for each program is part of the program settings.
![soundplant tempo sync soundplant tempo sync](https://s.getwinpcsoft.com/screenshots/5597/5597845_1.jpg)
Isn't the whole idea of external sync supposed to prevent simply matching the tempo settings and hoping they don't drift too much? Making Sonar the timing master may be the only solution. If I set the tempo in Sonar to match the keyboard, expect it will drift out of sync eventually. What steps are necessary to get Sonar to use the MIDI clock tempo as the project tempo? My test demonstrates that they are not locked currently. Also the Sonar metronome runs at 120, which shows it is not locked to MIDI sync. But the recorded audio clip is about 6 1/3 measures long, which corresponds to the tempo 120 in Sonar. At the end of the recording, the Now marker is at the start of measure 5, which is where it should be. I record 4 measures of audio based on the pattern from the source keyboard at tempo 90. To test whether Sonar is using the MIDI clock tempo, or its own, I intentionally set the Sonar project tempo to 120, while the MIDI clock tempo is 90. However the tempo in Sonar is not locked to the MIDI clock. When I press record the time display changes to "Waiting for MIDI Sync" until I start the instrument playing.
![soundplant tempo sync soundplant tempo sync](https://s3.amazonaws.com/izotopedownloads/docs/nectar300/en/images/delay/tempo-sync.png)
I tried clicking it anyway, but the basic problem of Sonar not following the MIDI Sync for tempo still exists. I am assuming that the correct setting in the Sync Module is to set the Sync Type control to "MIDI Sync" and the state of "Transmit MIDI Sync" doesn't matter. If step 5 is correct, it is highly non-intuitive, and this section needs a lot of additional explanation. The help for the Transmit MIDI Sync button on the Sync Module says "Transmit MIDI Sync to external MIDI devices, such as drum machines, stand-alone MIDI hardware sequencers, and sequencers built into MIDI keyboards (only available when using the Internal or Audio clock)." If Sonar is the slave, the external device is providing the MIDI sync to Sonar, so Sonar will not be sending it to an external device. I'm assuming that this statement should read "Make sure that your MIDI interface is selected in the Inputs list, and click OK." Second in step 5 it says "Click the Transmit MIDI Sync button in the Sync module to use the MIDI Sync clock source." The next time the Preferences dialog is opened, the "highlight" is no longer present. It is possible to left-click on a MIDI interface and it will highlight, but that is a non-persistent setting. Normally, MIDI devices that are checked are active, and those that are not checked are not active. Make sure that your MIDI interface is highlighted in the Inputs list, and click OK." The use of "highlighted" is puzzling. Two things in the help file are questionable: First in step 4 it says "4. I checked the help file for MIDI Sync with Sonar as a slave. Why is Sonar using the internal tempo when set to external clock? How do I get it to use the MIDI tempo? At a 3X tempo of 120.0, there is 20mS between clocks (1/3). If the Kronos is set to a tempo of 40.0, there is 62mS between clocks. I verified that the MIDI clock generated by the Kronos does follow the tempo. Shouldn't the tempo come from the MIDI clock? As I understand it, a MIDI Clock is related to the tempo as there are 24 MIDI clocks per quarter note. I'm running the Kronos pattern at a tempo of 120, but if the tempo in Sonar is at 90, the metronome and M:B:T ruler will operate at a tempo of 90. But the timing in Sonar does not match the Kronos. In Sonar, the recording waits (displaying Waiting for Midi Sync) until the pattern starts on the Kronos. The Kronos generates patterns with its internal Karma system, and I want the M:B:T timing in Sonar to match that used by Karma. I have Sonar configured to use external MIDI clock provided by a Korg Kronos. Syncing Sonar tempo to match external MIDI clock