Hi,
I am having a massive problem with my audio recordings in logic express 7(.3 i think). I play guitar for example and it's perfectly in time and i can press record and all is well until i go to play it back and it's slightly out of time which obviously makes it sound awful. thanks for any help !
Audio not in sync
Audio not in sync
by Kim Prima » Mon Mar 03, 2008 6:07 pm
- Kim Prima
- Posts: 7
- Joined: Mon Mar 03, 2008 6:04 pm
by ski » Mon Mar 03, 2008 6:19 pm
NOTE: this procedure was originally posted during the Logic 7 era and updated for Logic 8. The procedure is still perfectly valid for Logic 9.
===========
SUMMARY: with this procedure you'll be playing back a track from Logic and recording it right back into Logic on another track. This "loopback recording" will likely be late* with respect to the original due to latencies inherent in your interface, driver software, etc. Note that Logic's I/O buffer and process buffer settings have no influence on this procedure.
This procedure lets you figure out to the sample how off your looped-back recording is with respect to the original. Once you determine that number, you'll then enter into Logic's recording delay setting in the audio prefs per the instructions below. From that point on, your live-recorded tracks will be perfectly in time with when you played them.
The procedure uses phase cancellation of the original and looped-back track to certify that you've found the right recording delay value (you'll see reference to "null point" below, and that's what this is about).
* Note: audio recorded by most audio interfaces ends up being late. But on some systems the recorded audio can actually end up early! And in some cases a recording delay setting of zero will suffice. The procedure outlined below addresses the more common scenario -- late audio.
HOW TO DETERMINE AND SET THE RECORDING DELAY
STEP 1 -- very important!
• Start with a totally blank song and NOT an existing project. Easy way to do this: use the Explore > Empty template.
• Turn software monitoring off
• Turn the metronome off
• Set the recording delay value to zero
• Set Plugin Delay Compensation (PDC) to off
2. Create two audio tracks:
• Track 1 (channel 1) -- add a CD track or any stereo track of your own, preferably something with sharp transients at the top, like drums or percussion. I'm going to refer to this audio region as "X". Align it to start at bar 2.
• Track 2 (channel 2) -- set this channel to record from INPUTS 1/2. This is the track you're going to record your looped-back audio on.
3. Use patch cables to physically connect outputs 1&2 of your audio interface to inputs 1/2 of the interface
4. Start playback at bar 1 and go into record a little before bar 2 (punch on the fly should be enabled to make this operation as smooth as possible. You can also use auto-punch if you want). The recording you're making on Track 2 -- the "loopback recording" -- is going to be called "Y". You only need to record about 10 - 20 seconds of material max.
5. After you've made the loopback recording, take Track 2 out of record and insert the Logic > Helper > Gain plug on this channel. Set the L & R channels to be out of phase.
What's going to happen next: you're going to play back both "X" (the original) and "Y" (the loopback recording). Because of the out-of-phase setting on the gain plug, if Logic recorded a perfectly in-time copy of X, playback at this point will result in silence. This is what happens when two identical waveforms are played together with the only difference being that one of them is 180º out of phase with the other.
However, chances are that X won't be time-aligned with Y due to the latency inherent in your audio interface and its driver software. You'll likely hear flamming (slapback echo), or a thin, flanger-like sound. If you hear this, it's a clear indication that your recording delay setting needs to be adjusted.
NOTE: the proper recording delay setting for some systems is indeed zero! So if at this stage you do achieve complete dead silence (or very close to it) you can conclude the test. If you don't achieve silence, continue to the next step...
6. Open "Y" in the sample editor. Zoom ALLLLLLLLLLL the way in to the anchor point as far as you can go. Set the sample editor's "view" to "samples".
7. Click/hold on the anchor point, being careful not to move it. You will now see two numbers in the sample editor window. Write down the bottom number.
On most system "Y" will have been recorded late. This means that the top of "Y" contains a little bit of dead air as compared to the original, "X". We're going to move the anchor point to the right -- one sample at a time -- to shift the starting point of "Y", past the dead air and to the sample position that will cause "Y" to be aligned with X, as follows...
8. Hit play and move Y's anchor point to the right one sample at a time until you start to hear the sound thin out. Start/stop Logic as needed. As you move the anchor further to the right the sound will thin out more and more. As you get closer to the null point a steady, flanger-like "pitch" will start to form in the sound. If the pitch gets increasingly higher you know you're moving in the right direction.
You will reach a point where the sound is extremely thin and almost silent, and then, moving one more sample to the right, it will cancel. When this happens, click and hold on the anchor and write down the bottom number.
9. Subtract the first number from the second number. Then put a "-" in front of it. THAT's your recording delay value; set it in your audio prefs.
To confirm that this is the correct number
10. Delete "Y" and make a new loopback recording on track 2. This is going to be called "Z".
11. If the number you calculated is correct, and the Gain plug is still active on track 2 (putting "Z" out of phase with the original "X"), when you play back both tracks now you will achieve silence. To confirm, bypass the plug and you should hear your original track 2x as loud.
If upon playing back X and Z the sound is still not perfectly canceling, adjust your recording delay +1 or -1 from the value you calculated and repeat steps 10 and 11 again.) However, note that sometimes it's not possible to achieve complete silence. You might hear a little bit of residual sound, and that will likely be due to the A/D convertor in your interface re-interpreting the signal in a slightly different way from the original. So while the goal is to achieve complete silence, you may only be able to get 99.95% of the way there. If you accomplish that, no worries, you're doing everything right and you'll be in good shape!
===========
SUMMARY: with this procedure you'll be playing back a track from Logic and recording it right back into Logic on another track. This "loopback recording" will likely be late* with respect to the original due to latencies inherent in your interface, driver software, etc. Note that Logic's I/O buffer and process buffer settings have no influence on this procedure.
This procedure lets you figure out to the sample how off your looped-back recording is with respect to the original. Once you determine that number, you'll then enter into Logic's recording delay setting in the audio prefs per the instructions below. From that point on, your live-recorded tracks will be perfectly in time with when you played them.
The procedure uses phase cancellation of the original and looped-back track to certify that you've found the right recording delay value (you'll see reference to "null point" below, and that's what this is about).
* Note: audio recorded by most audio interfaces ends up being late. But on some systems the recorded audio can actually end up early! And in some cases a recording delay setting of zero will suffice. The procedure outlined below addresses the more common scenario -- late audio.
HOW TO DETERMINE AND SET THE RECORDING DELAY
STEP 1 -- very important!
• Start with a totally blank song and NOT an existing project. Easy way to do this: use the Explore > Empty template.
• Turn software monitoring off
• Turn the metronome off
• Set the recording delay value to zero
• Set Plugin Delay Compensation (PDC) to off
2. Create two audio tracks:
• Track 1 (channel 1) -- add a CD track or any stereo track of your own, preferably something with sharp transients at the top, like drums or percussion. I'm going to refer to this audio region as "X". Align it to start at bar 2.
• Track 2 (channel 2) -- set this channel to record from INPUTS 1/2. This is the track you're going to record your looped-back audio on.
3. Use patch cables to physically connect outputs 1&2 of your audio interface to inputs 1/2 of the interface
4. Start playback at bar 1 and go into record a little before bar 2 (punch on the fly should be enabled to make this operation as smooth as possible. You can also use auto-punch if you want). The recording you're making on Track 2 -- the "loopback recording" -- is going to be called "Y". You only need to record about 10 - 20 seconds of material max.
5. After you've made the loopback recording, take Track 2 out of record and insert the Logic > Helper > Gain plug on this channel. Set the L & R channels to be out of phase.
What's going to happen next: you're going to play back both "X" (the original) and "Y" (the loopback recording). Because of the out-of-phase setting on the gain plug, if Logic recorded a perfectly in-time copy of X, playback at this point will result in silence. This is what happens when two identical waveforms are played together with the only difference being that one of them is 180º out of phase with the other.
However, chances are that X won't be time-aligned with Y due to the latency inherent in your audio interface and its driver software. You'll likely hear flamming (slapback echo), or a thin, flanger-like sound. If you hear this, it's a clear indication that your recording delay setting needs to be adjusted.
NOTE: the proper recording delay setting for some systems is indeed zero! So if at this stage you do achieve complete dead silence (or very close to it) you can conclude the test. If you don't achieve silence, continue to the next step...
6. Open "Y" in the sample editor. Zoom ALLLLLLLLLLL the way in to the anchor point as far as you can go. Set the sample editor's "view" to "samples".
7. Click/hold on the anchor point, being careful not to move it. You will now see two numbers in the sample editor window. Write down the bottom number.
On most system "Y" will have been recorded late. This means that the top of "Y" contains a little bit of dead air as compared to the original, "X". We're going to move the anchor point to the right -- one sample at a time -- to shift the starting point of "Y", past the dead air and to the sample position that will cause "Y" to be aligned with X, as follows...
8. Hit play and move Y's anchor point to the right one sample at a time until you start to hear the sound thin out. Start/stop Logic as needed. As you move the anchor further to the right the sound will thin out more and more. As you get closer to the null point a steady, flanger-like "pitch" will start to form in the sound. If the pitch gets increasingly higher you know you're moving in the right direction.
You will reach a point where the sound is extremely thin and almost silent, and then, moving one more sample to the right, it will cancel. When this happens, click and hold on the anchor and write down the bottom number.
9. Subtract the first number from the second number. Then put a "-" in front of it. THAT's your recording delay value; set it in your audio prefs.
To confirm that this is the correct number
10. Delete "Y" and make a new loopback recording on track 2. This is going to be called "Z".
11. If the number you calculated is correct, and the Gain plug is still active on track 2 (putting "Z" out of phase with the original "X"), when you play back both tracks now you will achieve silence. To confirm, bypass the plug and you should hear your original track 2x as loud.
If upon playing back X and Z the sound is still not perfectly canceling, adjust your recording delay +1 or -1 from the value you calculated and repeat steps 10 and 11 again.) However, note that sometimes it's not possible to achieve complete silence. You might hear a little bit of residual sound, and that will likely be due to the A/D convertor in your interface re-interpreting the signal in a slightly different way from the original. So while the goal is to achieve complete silence, you may only be able to get 99.95% of the way there. If you accomplish that, no worries, you're doing everything right and you'll be in good shape!
Last edited by ski on Fri Nov 09, 2012 2:48 pm, edited 22 times in total.
MacPro 8 Core 2.4 Xeon | 32G RAM | OSX 10.6.8 | Logic 9.1.7 | RME FF800 | 3 monitors | Toys for days
-
ski - Site Contributor
- Posts: 15667
- Joined: Thu Dec 15, 2005 5:12 pm
- Location: Los Angeles
by ski » Mon Mar 03, 2008 6:30 pm
"Turn software monitoring off, set recording delay to zero, set PDC off, and have zero plugins anywhere in your song."
Software monitoring, PDC, and recording delay are parameters in your audio preferences. Zero plugins means just that -- no plugins anywhere in the song.
You're best starting off with a blank template for this too, adding two audio tracks, and following the procedure above.
If you find that the procedure is too technical or seems too complicated, you may need someone more experienced on Logic to help you. This procedure is the only way to calculate recording delay and set it properly. And unless you set it correctly, your recording will always be out of time.
BTW, what audio interface do you have?
Software monitoring, PDC, and recording delay are parameters in your audio preferences. Zero plugins means just that -- no plugins anywhere in the song.
You're best starting off with a blank template for this too, adding two audio tracks, and following the procedure above.
If you find that the procedure is too technical or seems too complicated, you may need someone more experienced on Logic to help you. This procedure is the only way to calculate recording delay and set it properly. And unless you set it correctly, your recording will always be out of time.
BTW, what audio interface do you have?
MacPro 8 Core 2.4 Xeon | 32G RAM | OSX 10.6.8 | Logic 9.1.7 | RME FF800 | 3 monitors | Toys for days
-
ski - Site Contributor
- Posts: 15667
- Joined: Thu Dec 15, 2005 5:12 pm
- Location: Los Angeles
by ski » Mon Mar 03, 2008 6:41 pm
shiver,
FWIW, with few exceptions, everyone has this problem, whether they realize it or not.
FWIW, with few exceptions, everyone has this problem, whether they realize it or not.
MacPro 8 Core 2.4 Xeon | 32G RAM | OSX 10.6.8 | Logic 9.1.7 | RME FF800 | 3 monitors | Toys for days
-
ski - Site Contributor
- Posts: 15667
- Joined: Thu Dec 15, 2005 5:12 pm
- Location: Los Angeles
by ski » Mon Mar 03, 2008 6:49 pm
Logic's default setting for recording delay is zero. The manual suggests that it's not necessary to change this, but that's got to be one of the most blatantly incorrect pieces of information in the entire manual. Unlike Cubase, Logic does not do an automatic calibration of the recording delay for your audio interface. The only way to get it to be right is to set it manually.
DP is the same way. The figure must be calcluated by hand and entered in their recording prefs. At least that's the way it is with their very own interfaces, such as the 2408.
In most DAW situations, most of the time, recorded audio will be late due to audio driver (and audio interface) latencies. I believe that the Hammerfall drivers are the only ones that attempt to calculate a recording delay on their own, but AFAIA the numbers are never right. If I'm not mistaken, most people whom I've helped out on this subject who've experienced the opposite effect -- recorded parts play back early -- were using Hammerfall gear.
So I'll put this out to everyone --- if your recording delay is set to zero, you should do the above test and see how things line up in your system. I can almost guarantee that you won't achieve perfect cancellation if you were to hit PLAY at the end of step 7. If you do, then great! If you don't, you have a problem: your recorded tracks will be out of time on playback.
DP is the same way. The figure must be calcluated by hand and entered in their recording prefs. At least that's the way it is with their very own interfaces, such as the 2408.
In most DAW situations, most of the time, recorded audio will be late due to audio driver (and audio interface) latencies. I believe that the Hammerfall drivers are the only ones that attempt to calculate a recording delay on their own, but AFAIA the numbers are never right. If I'm not mistaken, most people whom I've helped out on this subject who've experienced the opposite effect -- recorded parts play back early -- were using Hammerfall gear.
So I'll put this out to everyone --- if your recording delay is set to zero, you should do the above test and see how things line up in your system. I can almost guarantee that you won't achieve perfect cancellation if you were to hit PLAY at the end of step 7. If you do, then great! If you don't, you have a problem: your recorded tracks will be out of time on playback.
MacPro 8 Core 2.4 Xeon | 32G RAM | OSX 10.6.8 | Logic 9.1.7 | RME FF800 | 3 monitors | Toys for days
-
ski - Site Contributor
- Posts: 15667
- Joined: Thu Dec 15, 2005 5:12 pm
- Location: Los Angeles
by ski » Mon Mar 03, 2008 6:56 pm
Kim Prima wrote:ok great thanks but i have a new problem . i cant plug my audio interfaces outs straight into the ins. it just does a crazy "about to blow up " sound. any ideas ?
That's probably because you have software monitoring turned on. It has to be off. That's why all the things I listed in the first step are so important!
MacPro 8 Core 2.4 Xeon | 32G RAM | OSX 10.6.8 | Logic 9.1.7 | RME FF800 | 3 monitors | Toys for days
-
ski - Site Contributor
- Posts: 15667
- Joined: Thu Dec 15, 2005 5:12 pm
- Location: Los Angeles
by ski » Mon Mar 03, 2008 7:05 pm
Kim Prima wrote:right sorry feeling real stupid. thanks
No need, really, this is a very technical procedure with lots to keep track of. I hope you get the desired result!!
MacPro 8 Core 2.4 Xeon | 32G RAM | OSX 10.6.8 | Logic 9.1.7 | RME FF800 | 3 monitors | Toys for days
-
ski - Site Contributor
- Posts: 15667
- Joined: Thu Dec 15, 2005 5:12 pm
- Location: Los Angeles
by ElMariachi78 » Tue Mar 04, 2008 11:28 am
Hi ski,
very interesting and important thing you figured out !
I can follow all your steps to calculate the recorddelaycompensation.
But i have one question which could be under step 1: what about the I/O-Buffersize, how should it be set. to the lowest (32) or to what i use in general for mixing like 512 or 1024 ?
Thank You
Milan
very interesting and important thing you figured out !
I can follow all your steps to calculate the recorddelaycompensation.
But i have one question which could be under step 1: what about the I/O-Buffersize, how should it be set. to the lowest (32) or to what i use in general for mixing like 512 or 1024 ?
Thank You
Milan
MacPro 2x2,66 GHz 6-Core, OS 10.7.5 , 8 GB RAM, Logic 9.1.7, MOTU midi express 128 , K&H O300D, Mixcubes, MH ULN-8, Mytek 8x192, UAD2, Duende Native, Axe-FX Ultra
-
ElMariachi78 - Posts: 274
- Joined: Wed May 30, 2007 1:05 pm
- Location: Darmstadt, Germany
by ski » Tue Mar 04, 2008 12:17 pm
ElMariachi78 wrote:Hi ski,
very interesting and important thing you figured out !
I can follow all your steps to calculate the recorddelaycompensation.
But i have one question which could be under step 1: what about the I/O-Buffersize, how should it be set. to the lowest (32) or to what i use in general for mixing like 512 or 1024 ?
Thank You
Milan
Hi Milan,
Strange as it may seem, neither buffer size settings (nor process buffer range settings) affect the recording delay calculation. In fact, after reading your post I did some tests to double-check this and I can confirm this is the case. At least on my system it is.
As far as setting the I/O buffer... as you probably know, the object of the game is to set the I/O buffer to the lowest possible number to reduce latency for live performance of virtual instruments while allowing them to actually function! For example, I was able to set my buffer to 32 when I first got my computer. But once I installed Garritan Personal Orchestra I was getting clicks and pops when I played those sounds, so I had to raise the buffer to 64. That cured the problem.
More recently I bought some VSL stuff and I had to raise the buffer yet again to 128.
But there are other tradeoffs that aren't always discussed... I'll relate how things work on my Logic 7 + MOTU system, though YMMV with Logic 8 and your particular audio interface...
My system doesn't work very well at a buffer setting of higher than 256... at settings of 512 and 1024, Logic complains. A lot LOL!!
But, at a buffer setting of 256, everything sounds better!. But that's too high a number to track with, so I'll track at 64 or 128 (if I'm using VSL). It would seem logical, then, for me to get the best sounding mix by upping the buffer to 256 but that's not the case... At 256, MIDI timing of any virtual or MIDI parts I have playing goes to s#!+.
Tradeoffs, tradeoffs...
-=sKi=-
MacPro 8 Core 2.4 Xeon | 32G RAM | OSX 10.6.8 | Logic 9.1.7 | RME FF800 | 3 monitors | Toys for days
-
ski - Site Contributor
- Posts: 15667
- Joined: Thu Dec 15, 2005 5:12 pm
- Location: Los Angeles
by ElMariachi78 » Tue Mar 04, 2008 1:13 pm
Hi ski again,
did the calculation...and it worked !...but... i had to try several times till i got it,my trouble was, i imported an normalized steroeinterleaved track and after i recorded that track on audio track 2 i missed that the level was a little bit lower than the original...hmmm.. then i thought to normalize that recorded track.. and so it worked.
Strange thing. The original has this double-zero sign and the recorded has not...and after normalization it also had that double-zero sign... wtf
And about that I/O-Buffer-thing, i know, for recording VI´s 32 is the best.but when i wanna use stuff like BFD 2 i have to increase up to 512 or even 1024... thats how it goes...But, well thanks for this calculation-thing !
did the calculation...and it worked !...but... i had to try several times till i got it,my trouble was, i imported an normalized steroeinterleaved track and after i recorded that track on audio track 2 i missed that the level was a little bit lower than the original...hmmm.. then i thought to normalize that recorded track.. and so it worked.
Strange thing. The original has this double-zero sign and the recorded has not...and after normalization it also had that double-zero sign... wtf
And about that I/O-Buffer-thing, i know, for recording VI´s 32 is the best.but when i wanna use stuff like BFD 2 i have to increase up to 512 or even 1024... thats how it goes...But, well thanks for this calculation-thing !
MacPro 2x2,66 GHz 6-Core, OS 10.7.5 , 8 GB RAM, Logic 9.1.7, MOTU midi express 128 , K&H O300D, Mixcubes, MH ULN-8, Mytek 8x192, UAD2, Duende Native, Axe-FX Ultra
-
ElMariachi78 - Posts: 274
- Joined: Wed May 30, 2007 1:05 pm
- Location: Darmstadt, Germany
by ski » Tue Mar 04, 2008 1:29 pm
ElMariachi78 wrote:Hi ski again,
did the calculation...and it worked !...but... i had to try several times till i got it,my trouble was, i imported an normalized steroeinterleaved track and after i recorded that track on audio track 2 i missed that the level was a little bit lower than the original...hmmm.. then i thought to normalize that recorded track.. and so it worked.
Strange thing. The original has this double-zero sign and the recorded has not...and after normalization it also had that double-zero sign... wtf
And about that I/O-Buffer-thing, i know, for recording VI´s 32 is the best.but when i wanna use stuff like BFD 2 i have to increase up to 512 or even 1024... thats how it goes...But, well thanks for this calculation-thing !
There are definitely a couple of WTF's in there LOL! But you did run across one thing that I didn't mention in my procedure --- that sometimes you won't get a perfect match of level when you do this kind of loopback test via analog out--->analog in; in such cases you have to jockey the level of track 2 a little bit. On systems where you can route a signal digitally out--->digitally in to Logic, level mismatches are usually not an issue.
Anyway, I'm very pleased that this has worked out for you and Kim.
Best,
-=sKi=-
MacPro 8 Core 2.4 Xeon | 32G RAM | OSX 10.6.8 | Logic 9.1.7 | RME FF800 | 3 monitors | Toys for days
-
ski - Site Contributor
- Posts: 15667
- Joined: Thu Dec 15, 2005 5:12 pm
- Location: Los Angeles
by ElMariachi78 » Tue Mar 04, 2008 2:35 pm
Ski wrote:There are definitely a couple of WTF's in there LOL! But you did run across one thing that I didn't mention in my procedure --- that sometimes you won't get a perfect match of level when you do this kind of loopback test via analog out--->analog in; in such cases you have to jockey the level of track 2 a little bit. On systems where you can route a signal digitally out--->digitally in to Logic, level mismatches are usually not an issue.
-=sKi=-
One more WTF... I routed the signal digitally like this:
logic out-->firewire-->Lightbridge-->Lightbrige ADAT out-->o1V96 ADAT in-->
Fader set to 0 db-->routing out ADAT -->Lightbrige ADAT in-->Firewire--->Logic in...= lower Level !? Don´t know why , must be something with the double-zero or normalization ... anyway
MacPro 2x2,66 GHz 6-Core, OS 10.7.5 , 8 GB RAM, Logic 9.1.7, MOTU midi express 128 , K&H O300D, Mixcubes, MH ULN-8, Mytek 8x192, UAD2, Duende Native, Axe-FX Ultra
-
ElMariachi78 - Posts: 274
- Joined: Wed May 30, 2007 1:05 pm
- Location: Darmstadt, Germany
Who is online
Users browsing this forum: Bing [Bot], cmurphy2 and 13 guests
