![]() I currently use the 4i4 for recording, my mic is connected to it, and the on-board sound card via optical wires to my amplifier for output to some loudspeakers. ![]() My setup: I am running an up-to-date Arch linux (6.1.4-arch1-1) with an AMD R圜PU, having an onboard sound card (Mainboard Asus Prime X370-PRO) and a Focusrite Scarlett 4i4 audio interface. Independent of this choice, it still segfaults sometimes, doesn’t play sound, etc. Until… Well I have tried to set up Ardour for days now. I have tried to do so in Audacity first but when I saw Ardour in a video, I thought this could be a much better solution. ![]() If there is more than a few ms variation in the recorded track positions, then something is wrong with your sound card.I recently have got a new audio interface with a microphone and want to start to record some tracks. If the average position is a millisecond earlier than the original, then you need to tweak the “Track shift after record” by +1 ms (in my case that would be -187).If the average position is a millisecond later than the original, then you need to tweak the “Track shift after record” amount by another -1 ms (in my case that would be -189).If the average position of each click in the recorded tracks line up with the original track, you’re done.Note that it is normal for there to be a little variation from one track to the next, but with a reasonable sound card the variation should be small, perhaps varying by around +/- 1 ms. J) Repeat step (i) so that you have several tracks one above the other like this: I) Shift + R to record a new track, then stop after a few seconds. H) Select the first track and set it to “Solo” (click the track “Solo” button). This is our initial measurement for the amount of “round trip” latency.īecause we need to shift the newly recorded track to the left (earlier), we need to adjust the position by -188 ms (minus one hundred and eighty eight).į) “Edit > Preferences > Devices” → Set “Track shift after record” to the negative of the measurement. Note that the “Length of selection” in my example is 188 ms (your will probably be different). Note that the clicks in the newly recorded track are after the clicks in the original track.Į) Zoom in on one of the strong beats, and select from the start of that strong beat in the first track, to the start of the strong beat in the recoded track, like this (click image to expand): You should now have a recording that looks something like this: Set the “Beat sound” to “Ping”.Ĭ) Place you headphones close to the microphone (as in Koz’s previous image, and press “Shift + R” to start recording to a new track.ĭ) Allow the recording to run for 6 or 7 seconds, then stop the recording (spacebar). (Buffer length should normally be about 100, but don’t adjust this if microphone recording is working OK)ī) Generate a 30 second click track with “Generate menu > Rhythm track”. ![]() ![]() So when that’s all working, move on to latency correction:Ī) “Edit menu > Preferences > Devices” → Set “Track shift after record” to 0 (zero). Can you record a second track (shift + R) and hear the first track play while the first track is recording? If yes, proceed, else fix this first.Can I hear myself through my headphones without a delay or echo? If yes, proceed, else fix this first.Can I hear the recording through my headphones when I play it back? If yes, proceed, else fix this first.Does Audacity record via the microphone? If yes, proceed, else fix this first.Here’s my “easy way” to set up latency correction…įirstly, ensure that the prerequisites are all in place: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |