Page 2 of 2
Re: recording time offset
Posted: Sat Jan 09, 2016 10:53 am
by steve
Re-reading your original post...
fretski wrote:I play a backing track in Audacity and record at the same time with overdub & play-through checked in prefs.
"Software playthrough" must be off (not selected) for overdub recording.
Re: recording time offset
Posted: Sat Jan 09, 2016 5:33 pm
by Gale Andrews
fretski wrote:
The settings are assumed stock and are "Audio To Buffer: 100ms, Latency Correction: -130ms". Looks like I'd have to change one of these by 100ms.
[...]
The original condition as posted and involving a +/- 100ms lead in the guitar track being recorded is unresolved and remains unchanged.
Latency correction physically shifts the track after recording in the direction and by the amount set in the preference. Negative value shifts left, positive value shifts right.
If the problem is that the current -130 ms setting makes the recorded track 100 ms too far to left, have you tried setting Latency correction to -30 ms?
Gale
Re: recording time offset
Posted: Sun Jan 10, 2016 2:02 am
by fretski
steve wrote:Re-reading your original post...
fretski wrote:I play a backing track in Audacity and record at the same time with overdub & play-through checked in prefs.
"Software playthrough" must be off (not selected) for overdub recording.
Didn't know that, just found it in the manual under 'your first recording'
And I had completely misread 'overdub' to mean that a new track is recorded including the monitored one as well as the one being played as opposed to only the played track being recorded as seems to be he case. What is meant I think is that the ultimate operation or final mix will be an overdub.
Re: recording time offset
Posted: Sun Jan 10, 2016 2:07 am
by fretski
Gale Andrews wrote:fretski wrote:
The settings are assumed stock and are "Audio To Buffer: 100ms, Latency Correction: -130ms". Looks like I'd have to change one of these by 100ms.
[...]
The original condition as posted and involving a +/- 100ms lead in the guitar track being recorded is unresolved and remains unchanged.
Latency correction physically shifts the track after recording in the direction and by the amount set in the preference. Negative value shifts left, positive value shifts right.
If the problem is that the current -130 ms setting makes the recorded track 100 ms too far to left, have you tried setting Latency correction to -30 ms?
Gale
I most certainly will do that now that I understand what the latency setting actually does. -30 should be right on, but I'm still curious how it comes about i.e. I had a hard time with handling a note being recorded what seems to be before being played
I'll be back later with this because if it works it'll simplify my life a lot
Re: recording time offset
Posted: Sun Jan 10, 2016 11:14 am
by steve
For multi-track editors (such as Audacity), the idea of "overdubbing" is to create a new recorded track while listening to other tracks. Thus you can create multiple voice / instrument recordings, recording one track at a time with each voice / instrument on separate tracks. This then allows you to edit / process each voice/instrument independently. You can also use overdubbing for recording new tracks with a backing track. When the project is Exported to create a normal audio file, all tracks (provided that they are not muted) are mixed down to create a single mono or stereo file.
Re: recording time offset [SOLVED]
Posted: Sun Jan 10, 2016 7:07 pm
by fretski
Gale Andrews wrote:fretski wrote:
The settings are assumed stock and are "Audio To Buffer: 100ms, Latency Correction: -130ms". Looks like I'd have to change one of these by 100ms.
[...]
The original condition as posted and involving a +/- 100ms lead in the guitar track being recorded is unresolved and remains unchanged.
Latency correction physically shifts the track after recording in the direction and by the amount set in the preference. Negative value shifts left, positive value shifts right.
If the problem is that the current -130 ms setting makes the recorded track 100 ms too far to left, have you tried setting Latency correction to -30 ms?
Gale
i tried with -30 but then had to ease off to -50, it's all in sync now, thanks