Re: Hardware Latency Compensation
2016/06/03 10:56:24
(permalink)
☄ Helpfulby Adji 2016/06/04 14:25:53
As scook says, the external insert plugin is the, or at least probably the simplest, way to go.
You don't need to use the plugin, you can do the job simply by using two tracks, one playin the recorded audio out to interface and the other recirding the return. If you can get low enough round trip latency you can monitor via track echo using either method. Otherwise monitor the loopback directly through the interface.
Without using the plugin, you can line up the original and re-recorded tracks simply by zooming right in and dragging the audio in the processed track until a prominent transient in it (big transients are the easiest thing to spot) lines up with its equivalent in the original unprocessed track. The best way I find is to put a kick drum or hi-hat symbol at the beginning or end of the original track, record it to the new track along with the rest of the audio, then into use it as a guide to nudging the new recording, after which delete the drum/hat sample from both tracks.
Sometimes you'll need to nudge the new recording backwards or forwards a big even if the external insert plugin has been used, some hardware processors, especially if they are digitsl in any way, have latency of their own which can vary slightly as they do their thing.
Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board,
ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre.
Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.