So sonar actually plays the sound 12ms early so I hear it in sync with the GUI, but wait, my input latency is 14ms so that would put the new track down 14ms late, but Sonar is smart enough to use that input figure and puts my new track 14ms back so it's now in perfect sync. Look at your Audio settings in Preferences and note what Sonar is saying your input and output latency is. This sound has to pass through a few things before it gets to our speakers. We are looking at a note in piano view or a waveform in track view and we expect to hear the sound instantaneously as the now time scrolls past it. All systems have latency in and out which added together we call Round Trip Latency It sort of starts with the GUI.
#AUDIO LOOPBACK TESTING DRIVER#
This is about the way the driver looks at your input and output latency and reports this to Sonar so Sonar can apply delay compensation to the newly recorded tracks. Larry, this not really about round trip latency even though it is connected. Your welcome to try the test and see what happens when you add a "look ahead" effect to your master bin. Of course for the test we use a brand new project with absolutely no effects. You can use your lowest and highest buffer and the results will not change other that run the risk of an audio engine dropout at the lower settings.
And as I said buffers have no bearing on the results. The loop back test will show you if your driver is performing correctly, Sonar can only calculate based on what the driver reports.
#AUDIO LOOPBACK TESTING DRIVERS#
Some audio drivers "lie" to Sonar and the offset is calculated incorrectly. This is why it's important to perform this test. If the compensation is consistent, you might be able to correct it by setting the delay manually. A too large buffer or processing delay would result in the looped back signal being recorded after the original. If so, then the problem must be some sort of delay compensation that is overcompensating. Slartabartfast Maybe I am reading the screenshots wrong, but it looks like you are "recording" the looped back audio earlier in the timeline than the original in some tests. I tested using different buffer settings and this had absolutely no bearing on the results. Repeat for as many modes and interfaces as desired. Try for a good almost over the top level. Hit play and adjust your level at the interface. ( double insurance) Now pick an audio track, name it and set it to REC. Then set output to "none" to avoid feedback loop.
For the audio tracks other than the synth set input to match your patching. Assign the synth audio output to MASTER or which ever output your going to send from. Notice it should line up with the midi track. Then insert an Audio track for each interface or mode you want to test. insert a MIDI track and draw a few snare or kick notes. You can use headphones if you want to listen, but your eyes are more important. I unplug my monitors from 1/2 to avoid mishaps and used output #1 into input #1. First set up you interface with a short cable running from an output to an input. and WDM mode a little late, MME mode WAY late. The test results were exactly the same on all 3 computers ASIO mode bang on ( even if you zoom way in. The Tascam must have WDM drivers or the Scarletts drivers are not stable in this mode. I can change to these modes and run the wave profiler, but the minute focus is on the project the Audio Engine stops. Main DAW and Laptop running Sonar Plat latest build ( my signature) Old DAW Sonar studio x3e It was interesting that my Scarlett 6i6 will not run on any computer in WDM or MME mode. I ran the test using 3 different computers, My main DAW ( W10), Laptop (W7) and my old DAW (W7). And it is very clear why MME mode is to be avoided for anything but playback. Don't unless you test! Not all interfaces will pass the test under WDM mode. Especially if you've been advised to use WDM mode. This is why I'm posting this thread here. Now it is bang on, but, only in ASIO mode. In my test prior to the new drivers the Tascam was off time. Mostly to see if the new drivers for my Tascam us1641 are really as good as I was experiencing. I did this test a few years ago and thought I run it again. The importance of the Loopback test and using Sonar
0 kommentar(er)
