• SONAR
  • How to get tight sync with MIDI/VSTi?
2016/10/06 10:19:52
bigfrog
Hey everybody,
I spent the past week or so building and tweaking a new computer and am really trying to get everything tightly synced and need a little help. I've searched the internet, this forum, other forums, Sonar help, etc. and tweaked most of the settings that I could find both for my soundcard and Sonar but I still have the following:
 
- MIDI devices are a hair behind the built-in metronome. A hair being around 830 samples. When I record MIDI as audio, the audio recording and the MIDI are completely in sync with each other so I do have that under control.
 
- I have two external Elektron devices, the Analog Four and Analog Rhythm, connected via Elektron's Overbridge software which shows up in Sonar as VST instruments (64-bit). They are a bit of a bigger hair behind the built in metronome. Both devices are physically connected to my mobo via USB and are completely in sync with each other but a bit behind my MIDI devices and a bigger bit behind the built in metronome. I cant tell how many samples behind as when I attempt to record the audio via the VSTi, it records the audio but does not display the waveform. [That's next week's problem to fix, but if anybody has any suggestions...] Incidentally when I bounce the audio (via Bounce to Track...) the audio is in time with the built in metronome.
 
I would love to find some online tutorial, book, utility anything that could help me get a really tight sync while at the same time help me understand what's going on a little better.
 
CPU: Intel i7-6700K
Mobo: Asus Z170 Deluxe
Video Card: currently onboard but ordered MSI GeForce GTX 1060
OS: Win10 64-bit
Soundcard: RME Fireface 400 (Sonar timing master) via SIIG DP FW 800 PCIe
DAW: Sonar Platinum 64-bit
Overbridge: 1.10.1 64-bit
RYTM OS: 1.30D
A4 OS: 1.23C
 
All software, drivers, firmware has been updated with what was available on the vendor's sites as of this week.
 
Fireface settings:
Fireface Buffer Size (latency): 128 samples (anything lower causes pops)
Sample Rate: 44.1
Clock Source: Fireface
 
Sonar:
Driver Settings:
Playback Timing/Record Master: ASIO Fireface
Audio Driver Bit Depth: 24
64-bit Double Precision Engine: Enabled
Sample Rate: 44.1
ASIO Reported Latencies: Input: 3.9ms, Output: 5.1ms, Roundtrip: 9
 
Audio Playback and Recording
Driver Mode: ASIO
 
Sync and Caching:
Record Latency Adjustment: Manual Offset: 3
Use ASIO Reported Latency: enabled with 397 in the box
 
MIDI Playback and Recording:
Prepare Using 256 MS Buffers
 
I have not messed around with anything in the Configuration File.
 
Any help would be appreciated but I would love to find some sort of resource that would help me help myself.
 
Thanks!
 
John
2016/10/06 18:07:11
brundlefly
Try changing 'Machine Sequencer Sync' from Tempo to Clock in Overbridge per this video:
 
     https://www.youtube.com/watch?v=q0zaHT8Wae8
 
For the record, I know nothing about these synths; I just googled 'Elecktron Analog Latency', and this was the first hit.
2016/10/06 18:33:05
bigfrog
Hey Brundlefly - Thanks for the suggestion but it's already set to Clock.  :)
 
Thanks!
2016/10/06 21:13:07
pinguinotuerto
Why do you have a manual offset if you also have Use ASIO Reported Latency: enabled with 397 in the box?
2016/10/06 22:03:07
bigfrog
Just troubleshooting. 
2016/10/06 22:09:12
pinguinotuerto
bigfrog
Just troubleshooting. 

Set it to 0, and leave the box checked. If that doesn't solve it, let me know. There's something else we can try.
2016/10/07 02:17:40
brundlefly
pinguinotuerto
Why do you have a manual offset if you also have Use ASIO Reported Latency: enabled with 397 in the box?



Most interfaces need a Manual Offset to compensate for hidden/unreported latency that SONAR doesn't know about.
2016/10/07 08:44:53
bigfrog
I started off with the Manual Offset as zero but set it at 3 after testing with Centrance Latency Test software.  It tests additional latency that happens outside of the driver I believe.  You route a patch cable from the physical out of your soundcard to the physical in, it sends a test signal and measures the difference in samples with the result being the manual offset.  I believe the offset is for recording audio only.
 
Thanks!
2016/10/07 10:00:08
pinguinotuerto
bigfrog
I started off with the Manual Offset as zero but set it at 3 after testing with Centrance Latency Test software.  It tests additional latency that happens outside of the driver I believe.  You route a patch cable from the physical out of your soundcard to the physical in, it sends a test signal and measures the difference in samples with the result being the manual offset.  I believe the offset is for recording audio only.
 
Thanks!

Did you set the manual offset to 3 after having this problem or because of your results after running the Centrance Latency Test?

Have you played around with the MIDI offset settings Under Synch and Caching? I'm not at the computer right now, so I can't remember exactly all the details. Do a forum search and there's a thread on which Brundlefly and I were discussing how it works. I think it was titled "MIDI early." Sorry, but I'm in bed on my phone. Haven't had my coffee yet.
2016/10/07 10:14:21
pinguinotuerto
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account