Sevenduster
Max Output Level: -90 dBFS
- Total Posts : 20
- Joined: 2015/02/15 06:42:17
- Status: offline
Recording Latency Compensation Issue
Hello Everybody. I recently bought a new interface for my Sonar Platinum DAW. The reason is becaus i thought my old one, a Tascam Us-122 Mk II, had some old drivers and these are not properly supported under WIN 10. I thought this becaus when i recorded stuff on my station i always had issues with my recording delay compensation working not properly. The clips i recorded were alway a bit too late and i had to shift them after the recording. Trying to put a manual value in the field "manual offset" did not change anything. Now i bought a new Saffire USB6 interface and i got nearly the same problem: The clips i record are alway a little to early! I can do anything i like in the settings: Tick the checkbox for using the reported latency, or untick it in combination with any value entered in the field "manual offset": There is no effect. Even if i put ridicolous values in the offset, let's say 5000 samples, nothing is beeing added to the latency. Tried this with the checkbox ticked and unticked. Anybody any clue how to solve the problem. I am running WIN 10, got the latest Sonar Platinum Update, Saffire USB 6 interface, SSD Disk, 8GB of RAM, Core I7, USB 2.0 suport. Thanks in advance, Axel
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Recording Latency Compensation Issue
2015/12/29 13:07:45
(permalink)
Start by measuring the actual Round-Trip Latency, using the free CEntrance Latency Tester: https://centrance.com/downloads/ltu/ Normally, the Manual Offset needed would then be (CEntrance-measured RTL - SONAR-reported RTL). A positive value (the usual case) adds compensation to make up for the part of the actual latency that isn't being reported to SONAR by the driver. A negative number subtracts from the automatic compensation in the somewhat unusual case that the driver-reported value is over-compensating. If it's true that Manual Offset is having no effect, you might have something else going on, but the starting point for troubleshooting should be knowing the actual RTL. And if it is actually smaller than the reported value, Manual Offset will be negative.
post edited by brundlefly - 2015/12/29 13:20:31
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
Sevenduster
Max Output Level: -90 dBFS
- Total Posts : 20
- Joined: 2015/02/15 06:42:17
- Status: offline
Re: Recording Latency Compensation Issue
2015/12/30 07:05:57
(permalink)
Hi Brundlefly, i followed your tip and downloaded the tool and did measured my latency. Result: 819 samples . Sonar reports (actually the focusrite reports the value, if i remember right...) 962 samples. The buffersizes used were/are the same. From your calculation follows: 819 - 962 = -143 samples for the offset in sonar. Put the value there and did a recording. Result: The same. The offset is completly ignored. I can put any value in there, nothing changes. Even if i put a value, lets say 3000 samples, nothing changes when it comes to recording audio - no shifting in any direction. This behavior was the same with my old tascam. And it is the same in our Studio where we Track our Band with a RME Hammerfall internal card. I wonder if the offset value has any effect at all or if it is working for somebody? If i am right, putting a random big value there should result in a recording going "off sync" to the background track, right? Cheers, Axel
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Recording Latency Compensation Issue
2015/12/31 15:48:22
(permalink)
Hmmm... not sure what could account for that on more than one system. It's working as usual here, and I don't recall anyone else ever reporting that it doesn't work. What device is listed in the Record Latency Adjustment section of Sync and Caching, and is it the same as the Record Timing Master in Driver Settings? Assuming they are the same (or at least two different channels of the same device), try re-recording a track using the same analog loopback path that you used to ping with CEntrance and see whether the alignment changes with changes to the Manual Offset. If that checks out, and the alignment is perfect with the Offset at -143 samples, then I think something must be gong on with the timing of the audio metronome or the way you monitor it.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
Sevenduster
Max Output Level: -90 dBFS
- Total Posts : 20
- Joined: 2015/02/15 06:42:17
- Status: offline
Re: Recording Latency Compensation Issue
2016/01/02 15:25:20
(permalink)
Hey! I tried your tip and set up a new Project. When i try it in the new project it works as expected. I searched for diffenrences between the two and found that in the "old" project i had a couple of VSTs on the source track. Then i added some of them in the new one and then i realized that the latency compensations for the plugins is not exact. The offset value is working but the latency compensation for the plugins is masking the value because it is sometimes more "off". Since the latency compensation for the plugins is automatic - i fear i can't to anyting against it. The plugin i tried were Amplitube, and The Fab-C ...
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Recording Latency Compensation Issue
2016/01/03 02:37:56
(permalink)
So the PDC-inducing FX are on other, previously recorded tracks, and you're direct monitoring what you're recording so you don't hear the delay? Record compensation should correct for that unless the plugin's not reporting the correct value to SONAR, and I haven't seen anyone complaining about this with Amplitube. I don't have it, but I double-checked that record compensation is working with other plugins that induce PDC.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
Sevenduster
Max Output Level: -90 dBFS
- Total Posts : 20
- Joined: 2015/02/15 06:42:17
- Status: offline
Re: Recording Latency Compensation Issue
2016/01/03 06:01:30
(permalink)
No, not directly. Yesterday i did a new test-setup. 2 Audio-Tracks. on the first i recorded the metronome with the new patch-point feature. On the second i recorded the output from the first one (via connecting output and input on my sapphire box). Result: When zooming in there was no delay. Waveforms where in sync. Then i put Amplitube on the first track with a setting that minimal distrotion of the source metronome was done. Recorded on the second track again. Zoomed in and result: approximal 50 samples of delay to the source waveform. So i guess the delay compensation for amplitube is not working correctly. I checked if the delay compensation for amplitube is on in the plugin-manager, but it was. No, i don't use direct monitoring. Often i record a guitar with and amp-sim so i need the processed signal. The delay in that is no problem for me..
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re: Recording Latency Compensation Issue
2016/01/07 02:26:33
(permalink)
Sorry for the delay getting back to this. I just tried your metronome recording scenario using Transient Shaper on the first track with default settings that don't alter the click waveform, and compensation on the loopback track was still perfect. Give TS-64 a try, and if it works, the problem must be with Amplitube's PDC reporting.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|