Reaper users, do you know how lucky you are to have Kenny Gioia? In the Avid world, the manufacturer you give 2, 10, or $50,000, wants you to know none of this. Just buy their stuff over and over and shut up about it. The contempt relationship of Avid support simply cannot be believed. Here, instead, Kenny brings to your attention on a regular basis answers before you need them, and presents them in a way no manual can even touch. Pro Tools complexity is certainly on a par with Reaper’s. The big difference is, with Avid, it’s all a big secret if you run into trouble, whether simple or arcane. I salute you Kenny!
@@TheCompleteGuitarist BuT ReAPeR iS NoT a rEaL dAw for real though, most producers dont realise that reaper can do the exact same thing for a fraction of the price
Your channel is just stupid valuable. I hope Cockos is paying you big money for this lol. This channel is half the reason I use Reaper. There is a perfect video for any question I might have. No other daw has as comprehensive of a video series on it. Never stop Kenny
Whenever I see a notification for a Kenny Gioia vid I immediately give the vid a thumbs up even if I don't watch it at that moment. Thank you Kenny for creating the best content ever!
Everyone knows for a fact that Keny is the best when it comes to Reaper. His awesome skills combined with his extensive knowledge on Reaper is simply extraordinary. He explains everything clearly in such a way that even the most stupid person can easily understand. Thanks again one more time for another super brilliant video..
I always thought I played a bit after the beats for some reason, I was never able to play better through the metronome(at least I thought). After doing this, I found I'm actually very good at keeping up with the tempo. This gave me a lot more of confidence and helped with my musician self-esteem by A LOT. I was off by 500-something samples. Thank you, Kenny! You're the man!
Same bro! After master studies in music, where I play music that's super tight, I was close to an existensial crisis when I heard how loose my time was when recording. But dang, it wasn't me, it was well over 500 samples from hell.
hey bro! Could you help me please? I have a focusrite 2i2 and when I record a track, it’s always earlier before the click track, ahead the grid. I already set the recording latency compensation, but the problem still there. Cheers
@@Quini66 Yeah, the loopback test in this video did the job, I come back to this video everytime I move, get a new PC or interface. It just never fails.
Thank you for this because I have tried to explain this to people but they just don't get it. You make my life simple just by showing them your video. Thanks a million Kenny. I posted your video for the world to see.
I'm still evaluating but I plan to buy Reaper. That is thanks to Kenny alone. Other DAW support can't compare when it comes to Kenny's enlightened and well executed videos!
This video has revolutionised my recording. The auto detect feature on my DAW gave the latency as 0.2ms whereas after doing this test I realised it was 3.8ms. No wonder all my tracks sounded off! If only I had figured this out earlier! I can't thank you enough for helping me to make this great leap forward. Now the tracks sound in sync.
This is fantastic, Kenny! A practical method to determine the actual latency instead of my trial and error attempts at nudging the track back or forwards a few milliseconds at a time (and still not getting it quite right). This really is excellent - thanks heaps!
Just one thing - make sure you turn OFF all monitoring FX , if using headphone output as this adds about 2500 samples latency in some cases ( things like Metric AB , sonarworks etc ) - but this is gold i found my system was out by 68 samples at 48 k 32bit 128 block . thanks alot Kenny
That's just brilliant. I'd read about these tests before, but they sounded so freaky, I would have a major anxiety attack it I tried them, so I never did. That's because I'd been given abstract instruction, with assumptions about my ability or pre-existing knowledge, but I had never been shown how to do them. Now I know.
So glad to have seen this. I must have done this kind of set up a few years back with a different and much older audio interface. It was way off. The Scarlett on its own gets me to around 0.4 milliseconds, an easy adjustment. But when we think about latency in real life, it's not a hard wired loopback that we're dealing with. It's signal to monitors or headphones, through our ears and brains, eventually to our fingers, to the articulations of our instrument, which can then be captured in real-time through the audio interface. Latency is complicated. But it's good to get that last half millisecond taken care of where we can because it all adds up.
Awesome tip Kenny. Just run this on my setup and the interface drivers were actually reporting very close - actually over-reporting the latency. I've had to enter -14 samples to get a match!
Adjusting interface latency like this makes the world of change for everybody but especially for idiots like me who use a lot of external hardware and resample through it. This video is a must see for everyone using Reaper. Thank you so much, Kenny! Awesome channel with so much great info on how to use Reaper.
I just ran this test on my setup, found it to be 16 samples off, corrected now! That was a small amount, but big enough to make a difference, THANKS Kenny! What a great test.
I tried this test and my interface was actually reporting the correct latency! However, the test track is recording exactly out of phase from the source. I rendered a MIDI kick note to a mono wave file and did the test from that. I have the channel set to Phase Normal. Has anyone seen this? Edit: I knew I'd find as soon as I posted - ugh! Long story short: the wave was changing phase at the interface. I found that changing the input from Line to Instrument/Guitar put the wave back in phase. I hope that helps someone.
Yes once again this is a video from Kenny that could not be clearer about what to do but at the same time gives all the background on why that you need. He's in danger of becoming a bit of a (international) treasure I fear!
It's not clear to me how the Request Block Size thing works compared to the buffer size setting in the ASIO driver. Followed this tutorial on my self-built PC (Core i7-5820K @ 4.3 GHz, 32GB RAM) running Windows 10 with a Focusrite 2i2 3rd Gen I/O. I set the buffer size in the ASIO Configuration... area to 32 samples. With the "Use audio driver latency" box unticked and running the test, it reported an offset of 206 samples. Ticking the box reduced that to 10 samples and entering that in the input manual offset field reduced it to 0 as demonstrated. But then I switched the buffer size to 64 and could immediately tell the waveform was AHEAD of the original; it measured 4 samples. Then I rewatched the steps and realized he was changing the Request Block Size field. So I went and changed it to 32 there and it lined up. HOWEVER, when I changed it to 512 samples it advanced the recorded wave 7 samples; same with 64. Go back 32 and it's now 4 samples fast. WTAF?!? I checked the Focusrite site and found a firmware update and afterwards the unchecked "Use audio driver latency" box returned 334 samples behind, but turning it on resulted in wav being 22 samples EARLY. Huh? I had to set a manual input offset of -15 to get things lined up, but now it holds across buffer sizes. Doing this has made me more confused than before. O_o
hey bro! Could you help me please? I have a focusrite 2i2 and when I record a track, it’s always earlier before the click track, ahead the grid. I already set the recording latency compensation, but the problem still there. Cheers
@@jcisternas I have the same issue. Seems like the latency is fluctuating and not consistent. No one seems to cover this issue and I think most people set it like kenny is explaining but dont care to check after the fact if its still configured correctly.
Wow, what a great tutorial. I am a ProTools user, but using Reaper as a second option, and using it on a mobility recording laptop. Knowing how to properly calibrate Reaper's latency in this very easy to understand way is awesome - Thank you!
my scarlet solo was only ~15 samples off after it adjusted to reported latency, but still worth it to have no doubt that the timeline is exactly as I heard it. thank you Kenny!
I did my loopback test ...and found out that my latency came from a manual output offset...which was delayed by 61 samples earlier than the sample I used... I put in my output manual offset by -61 samples...and now everything is correct as it should be. Thanks Kenny Gioia!
Thanks for this video. I try to route to outboard gear and record that to a new track but there is latency I want to avoid. Your approach is exactly what I was thinking of doing but didn't know how to do the the settings in Reaper. Thanks!
Wow .. this is gold and such a Pro Hack for peek performance. Kenny you are the man !!!!!! Hands down you provide the BEST content for Reaper by a long shot !!!! Thank you
Hi! I have an issue with my interface (a Behringer U-Phoria UMC22) that every time I do this process I get a slightly different result. Even on e.g. two consequent records of Track 1 sent to Track 2, I'll get different value for the offset. Moreover, when I change the requested block size, the recording is then completely off. Any ideas?
Thanks for this explanation, very helpful! The difference between the driver-reported latency and your measured latency might also be caused by the output latency of your interface. In that case "overadjusting" the input latency would lead to misaligned, "premature" recordings. Anyway, thanks for sharing!
hey bro! Could you help me please? I have a focusrite 2i2 and when I record a track, it’s always before the click track, ahead the metronome. I already set the recording latency compensation, but the problem still there. Cheers
@@jcisternas Sounds like the latency compensation is not configured correctly (value too high). Have you tried disabling it in the Recording preferences?
Got any tips for when your latency differs everytime you run a test? Pretty sure there's several others who has the same issue of never having the same result twice. What's even more baffling is that the recorded audio has already been rendered halfway through the source audio, so it's like the reported latency has been taken into account even when it's unchecked.
This is confusing to me because the loopback's path is different than the path from a mic. 1) Mic to interface to Computer to reaper vs 2) Reaper/pc out to interface to computer to Reaper. Wouldn't the time it takes to go from mic to the interface be different than the time it takes in the loopback to go from Reaper/computer to interface?
Changing the buffer after setting the manual offset doesn’t give me the same result when recording at different buffer settings. I calculated mine at 128, but it only records accurately at 128. The test recording comes in earlier than the original track with lower buffer settings. With higher settings it’s still recording later than the original track. Any ideas?
I tried this on my system. Unfortunately the latency is different every time when I record with the audio driver reported latency turned off. I took consecutive 4 records and the gap was 574, 571, 562, 583, etc. Any suggestion for this? Thanks Kenny for your awesome videos as always!
Hi Kenny, thanks for all the lessons to the community. You sure deserve more... Now, this one means that if we make this right we can record with monitoring on or do i miss something. Sorry if this is a stupid Q but i am new to this! Thanks again!
This video was a game changer for me , I ended up leaving the box unchecked and left my samples at around 1024 . And am able to record my guitar with amplitube in perfect time!!! HUGE HELP!!!
I think it's worth noting that the monitoring FX chain should be turned off during this test as any plugin inserted there would add to the output delay. Secondly, it seems that this delay is sampling rate dependent. In my case, I end up with 176 samples at both 44.1 and 48KHz, but 161 at 96KHz and 142 at 192 KHz.
If you mean monitoring fx on the master channel if you're sending audio directly to the hardware from the track it won't go through the master channel, but you probably mean any track fx you might have. It's best not to have any, just like in the video, just to be on the safe side.
Yeah, this helps a lot! Love Reaper and Kenny! Best decision to switch to Reaper. Not only because of Reaper, but also because of Kenny's outstanding videos! Thank you!!!
@@alcoustic5297 yeah but you may have more than one track going. If you are soloing a single track to be recorded using this method, then yes. All I'm asking is if the sample offset is relevant to other tracks playing with plugins on them at the same time or not.
Hello. When working with iD14 mk2 there is a problem with the delay. After the loopback test, I manually adjust the delay of 33 samples. After which I reboot the computer and do the loopback test again and get 40 samples (the number varies within +- 20 samples). Latency can also change during one session. I work at 48 kHz and a buffer of 128 samples in Reaper 7, Windows 11 OS.
4:28 Need some extra help here. Could someone tell me how can I record without using Ctrl+R, Kenny apparently managed to record as soon as he hit the Kick key. Instead of having to press Ctrl+R and then the Kick. Also, another novice question, 4:10 what's exactly what needs to be leveled, volume on both recordings? I didn't get that part either. Thanks to anyone who bothered to read me and reply!
this is exactly what I needed. while recording overdub in the 2nd, 3rd, etc tracks, can we hear the previously recorded tracks in the monitor speakers and / or headphones? I'd like to hear the formerly recorded tracks, so that I can play another instrument over that.
Is this test valid? You're sending a signal out of the device and back in. So you're dealing with DA conversion and AD conversion. Seems like the sample offset should set to like half most of the time because you're normally only dealing with AD conversion, no? Unless you're using this to output to hardware and back in with ReaInsert or something...
While I'm very grateful for this help I'm well over my head on many of the technical functions mentioned here. I wish you'd made one video for PC's and one for Macs as I struggle to follow as it switches back and forth. One example is at 1:19 for a Mac with block size checked and 48000 sample rate but unchecked and 1:53 for a PC with block size unchecked and sample rate checked 44100. So this sent me off trying to figure out what my settings there should be. For people like me, that are just barely hanging on as they try to follow, this combination of Mac and PC made it more complicated. Thanks for the advice though.
Hi Kenny. I was excited to finally try this. I used the same interface you seemed to use in your test. However, I get inconsistent results. Every time I repeat the test, the result is different. I SO wanted this to work. Ah well. Thanks anyway! Hope you're doing well.
Wow this is super cool. Everything is answered ! I feel ashamed for recording wrong this whole time by a few samples I guess.... By the way I have to play the video at 2x speed to stay awake, but it's because I'm in know territory. Thanks !
Hi, I'm trying to follow this tutorial, I got the setup, but I'm stuck on how to make the recording. How do I play the kickdrum at the same time I hit Record?
I have the opposite problem. I have look ahead issues. I did the loop back test to see by just how much and the recorded kick is 735 samples ahead of the original kick. I thought ok instead of adding samples I'll subtract them with -735. It had no effect. I've been looking for solutions to this problem and have had no luck. Any suggestions Kenny?
My device is over compensating so that what I record gets offset earlier than it should. Do I just put a minus figure in that box, or should I switch 'use audio driver reported latency' off and then add my plus figure (which is 9314 samples!!!). I tried that but then it's still not right. It comes out early again.
I don't know if I'm having a latency problem or something else. Now when I strum my guitar there is no sound but if I strum it hard the sound comes on a bit late and then it seems to sustain and then the sound just drops off. I need some help please.
Could any of the latency be coming from the output side of things? Would the amount of latency be different coming from, say an instrument line-in? I have no idea if there's "output latency" on computer + audio interface setups.
Interesting point. You will be performing to what you hear coming out of the output so the output latency ( time between Reaper sending a sample and it being heard on the output ) may not actually matter at all. Great video from Kenny (as always).
im new to all this but even though this video makes complete sense to me i am having trouble recording to the second chanel. No matter which input i chose (my options are input-mono(left , right) or input-stereo(left/right) i am not getting any levels to record. Can someone help me please?
I need help: My audio interface's (IK Multimedia Axe I/O) reported latency constantly chnges. I've tested using the RTL utility, reainsert, as well as just recording a kick sample from the input to output of the interface and checking the difference in samples on the timeline in reaper. And with these individual tests there can be a difference of up to 80 samples the next time I run it. This is all usually at 48kHz sample rate and 64 buffer size. So that 80 sample difference translates to a difference of over 1.5 ms latency. Is this normal? If not, does anyone know what could be the issue?
Awesome, however my results diverge when I change the Request Block Size - ie the marker no longer lines up with the recording.. any ideas what's going on? (FYI my required offset was only 5 samples)
The issue I'm having is when playing to Reaper's built in metronome, the recording itself starts either early, or the metronome is early which results in roughly half the first beat cut off. Any fixes for that with a Scarlett 2i2?
Why is it that when I recorded a sample (kick sample @44100) that my recording is not late, but it was ahead by 323 samples? I measure it from the sample's 0 threshold, backwards to my recorded output's 0 threshold. am I doing something wrong? PRettty sure I followed this vid to the letter (reported latency is turned on, audio interface is plugged in to the headphone jack instead of output.....something's weird.
i tried the loopback test but whenever I change the buffer size it again doesn't line up. In other words I would need a custom setting for every buffer size. Additionally the latency seems to vary 3 buffers with every recording. 1) Does anyone have the same problem? 2) Any ideas to fix that? It seems to me that it might maybe be a driver issue, where the interface is always reporting a different latency to Reaper. 3) Could that be possible? Gear used: Windows 10 ; Focusrite Scarlett 2i2 2nd Gen Anyway thanks for the great video!
Reaper users, do you know how lucky you are to have Kenny Gioia? In the Avid world, the manufacturer you give 2, 10, or $50,000, wants you to know none of this. Just buy their stuff over and over and shut up about it. The contempt relationship of Avid support simply cannot be believed. Here, instead, Kenny brings to your attention on a regular basis answers before you need them, and presents them in a way no manual can even touch. Pro Tools complexity is certainly on a par with Reaper’s. The big difference is, with Avid, it’s all a big secret if you run into trouble, whether simple or arcane. I salute you Kenny!
I agree with you. May experience exactly.
Under-rated comment. Reaper will end up owning the world with this approach (I hope).
@@TheCompleteGuitarist BuT ReAPeR iS NoT a rEaL dAw
for real though, most producers dont realise that reaper can do the exact same thing for a fraction of the price
Of course we do. That's why we use Reaper...
Agree
Your channel is just stupid valuable. I hope Cockos is paying you big money for this lol. This channel is half the reason I use Reaper. There is a perfect video for any question I might have. No other daw has as comprehensive of a video series on it. Never stop Kenny
I wouldn't say stupid but yes, great channel Sir, thank you!
@@jeaneugenedxstupid = crazy good (American slang)
Ladies and Gentlemen Mr. Kenny Gioia saving our lives in this hard music producing world. We can't thank you enough Kenny...You are simply awesome!!!
Whenever I see a notification for a Kenny Gioia vid I immediately give the vid a thumbs up even if I don't watch it at that moment. Thank you Kenny for creating the best content ever!
Obsidian s
Me too :)
Me too ♥️
Everyone knows for a fact that Keny is the best when it comes to Reaper. His awesome skills combined with his extensive knowledge on Reaper is simply extraordinary. He explains everything clearly in such a way that even the most stupid person can easily understand. Thanks again one more time for another super brilliant video..
I'm a stupid person and I approve this comment.
@@Son-vy5rl me too. And I am stupider than you
I always thought I played a bit after the beats for some reason, I was never able to play better through the metronome(at least I thought). After doing this, I found I'm actually very good at keeping up with the tempo. This gave me a lot more of confidence and helped with my musician self-esteem by A LOT. I was off by 500-something samples.
Thank you, Kenny! You're the man!
Same bro! After master studies in music, where I play music that's super tight, I was close to an existensial crisis when I heard how loose my time was when recording. But dang, it wasn't me, it was well over 500 samples from hell.
hey bro! Could you help me please? I have a focusrite 2i2 and when I record a track, it’s always earlier before the click track, ahead the grid. I already set the recording latency compensation, but the problem still there. Cheers
Hey, same issue here... Did you find any fix for it? I am getting crazy
@@Quini66 Yeah, the loopback test in this video did the job, I come back to this video everytime I move, get a new PC or interface. It just never fails.
@@RandallHammer thanks bud! I did it this morning and seems to be working now. 800 samples were the problem 😅
Thank you for this because I have tried to explain this to people but they just don't get it. You make my life simple just by showing them your video. Thanks a million Kenny. I posted your video for the world to see.
Thank you again, Kenny. You keep making me glad I purchased reaper and use it as my main DAW.
I'm still evaluating but I plan to buy Reaper. That is thanks to Kenny alone. Other DAW support can't compare when it comes to Kenny's enlightened and well executed videos!
This video has revolutionised my recording. The auto detect feature on my DAW gave the latency as 0.2ms whereas after doing this test I realised it was 3.8ms. No wonder all my tracks sounded off! If only I had figured this out earlier! I can't thank you enough for helping me to make this great leap forward. Now the tracks sound in sync.
That's a very much low latency anyway. It seems you're able to say there's a difference. I'm in awe!
Years using Reaper and adjusting all almost by "ear", thank you Kenny! Keep teaching, I'll keep learning!
This is by far one of the most important features of reaper. Thank you !!
This is a rare content nobody could explain it, Except Kenny Jioia in a Reaper Mania. Thank You. You are Just a Saver.
This is fantastic, Kenny! A practical method to determine the actual latency instead of my trial and error attempts at nudging the track back or forwards a few milliseconds at a time (and still not getting it quite right). This really is excellent - thanks heaps!
Just one thing - make sure you turn OFF all monitoring FX , if using headphone output as this adds about 2500 samples latency in some cases ( things like Metric AB , sonarworks etc ) - but this is gold i found my system was out by 68 samples at 48 k 32bit 128 block . thanks alot Kenny
Kenny I have no words to describe how much you helped me in my music production journey with Reaper. Honestly, you are BRILLIANT!
That's just brilliant. I'd read about these tests before, but they sounded so freaky, I would have a major anxiety attack it I tried them, so I never did. That's because I'd been given abstract instruction, with assumptions about my ability or pre-existing knowledge, but I had never been shown how to do them. Now I know.
🤯 Kenny is amazing! The things I've learned from him alone has saved years of time.
So glad to have seen this. I must have done this kind of set up a few years back with a different and much older audio interface. It was way off. The Scarlett on its own gets me to around 0.4 milliseconds, an easy adjustment. But when we think about latency in real life, it's not a hard wired loopback that we're dealing with. It's signal to monitors or headphones, through our ears and brains, eventually to our fingers, to the articulations of our instrument, which can then be captured in real-time through the audio interface. Latency is complicated. But it's good to get that last half millisecond taken care of where we can because it all adds up.
yet again you've helped me fix a reoccurring issue (very much a pain in my behind) tysm man god bless u
Thank you, thank you, thank you! This was driving me crazy! I thought that my "internal" timing was way off!
only you have the solution.. wasted my time watching other junk videos.. thank you sir
🙏🙏🙏🙏
Thank you!!! This video really solve a big problem of mine for years!!!
Awesome tip Kenny.
Just run this on my setup and the interface drivers were actually reporting very close - actually over-reporting the latency. I've had to enter -14 samples to get a match!
Adjusting interface latency like this makes the world of change for everybody but especially for idiots like me who use a lot of external hardware and resample through it. This video is a must see for everyone using Reaper. Thank you so much, Kenny! Awesome channel with so much great info on how to use Reaper.
I just ran this test on my setup, found it to be 16 samples off, corrected now! That was a small amount, but big enough to make a difference, THANKS Kenny! What a great test.
I spent years with this problem, and i never found a solution so i had to get used to offset my tracks manually, thanks a lot for this information 🙌🙌
Just can't thank you enough Mr. Gioia... Great Stuff!
I tried this test and my interface was actually reporting the correct latency! However, the test track is recording exactly out of phase from the source. I rendered a MIDI kick note to a mono wave file and did the test from that. I have the channel set to Phase Normal. Has anyone seen this? Edit: I knew I'd find as soon as I posted - ugh! Long story short: the wave was changing phase at the interface. I found that changing the input from Line to Instrument/Guitar put the wave back in phase. I hope that helps someone.
Yes once again this is a video from Kenny that could not be clearer about what to do but at the same time gives all the background on why that you need. He's in danger of becoming a bit of a (international) treasure I fear!
It's not clear to me how the Request Block Size thing works compared to the buffer size setting in the ASIO driver. Followed this tutorial on my self-built PC (Core i7-5820K @ 4.3 GHz, 32GB RAM) running Windows 10 with a Focusrite 2i2 3rd Gen I/O. I set the buffer size in the ASIO Configuration... area to 32 samples.
With the "Use audio driver latency" box unticked and running the test, it reported an offset of 206 samples. Ticking the box reduced that to 10 samples and entering that in the input manual offset field reduced it to 0 as demonstrated.
But then I switched the buffer size to 64 and could immediately tell the waveform was AHEAD of the original; it measured 4 samples. Then I rewatched the steps and realized he was changing the Request Block Size field. So I went and changed it to 32 there and it lined up. HOWEVER, when I changed it to 512 samples it advanced the recorded wave 7 samples; same with 64. Go back 32 and it's now 4 samples fast. WTAF?!?
I checked the Focusrite site and found a firmware update and afterwards the unchecked "Use audio driver latency" box returned 334 samples behind, but turning it on resulted in wav being 22 samples EARLY. Huh? I had to set a manual input offset of -15 to get things lined up, but now it holds across buffer sizes.
Doing this has made me more confused than before. O_o
hey bro! Could you help me please? I have a focusrite 2i2 and when I record a track, it’s always earlier before the click track, ahead the grid. I already set the recording latency compensation, but the problem still there. Cheers
@@jcisternas I have the same issue. Seems like the latency is fluctuating and not consistent. No one seems to cover this issue and I think most people set it like kenny is explaining but dont care to check after the fact if its still configured correctly.
My interface is spot on, but its nice to know how i can adjust it. Never heard of this feature, thnx!
Wow, what a great tutorial. I am a ProTools user, but using Reaper as a second option, and using it on a mobility recording laptop. Knowing how to properly calibrate Reaper's latency in this very easy to understand way is awesome - Thank you!
my scarlet solo was only ~15 samples off after it adjusted to reported latency, but still worth it to have no doubt that the timeline is exactly as I heard it. thank you Kenny!
You are the best for Reaper video's my friend !
I did my loopback test ...and found out that my latency came from a manual output offset...which was delayed by 61 samples earlier than the sample I used...
I put in my output manual offset by -61 samples...and now everything is correct as it should be.
Thanks Kenny Gioia!
I did the test without using driver reported latency as you suggested, and it came to 496 samples....I recorded at 128 block size
The other test was done using driver reported latency
Thanks for this video. I try to route to outboard gear and record that to a new track but there is latency I want to avoid. Your approach is exactly what I was thinking of doing but didn't know how to do the the settings in Reaper. Thanks!
Thanks. New to the channel and it seems to be a banger. See you next time.
Thank you Kenny for all this useful information, We as a community can't thank you enough!!
Kenny Gioia you are a genius!!
Thank you very much for sharing all this knowledge, we learn a lot thanks to your generosity.
Greetings from Argentina!
Wow .. this is gold and such a Pro Hack for peek performance. Kenny you are the man !!!!!! Hands down you provide the BEST content for Reaper by a long shot !!!! Thank you
I just did my tests with your Kenny way. I have an allen & heat mixer that showed over 1000 samples. I fixed the delay. thank you very much
You make this look like it's completely logical yet I would never have come up with this myself. Thanks man!
Great video and I was able to fix my latency problem almost instantly thanks to your help
Wohhooo. that is great. Thx as always Kenny!
This was very helpful. Thank you. I use Studio one but the principle is the same.
Man this helped me so damn much, I was getting frustrated with this latency. This video solved my issues, much thank you Kenny. I AM SUBSCRIBING!!
Hi!
I have an issue with my interface (a Behringer U-Phoria UMC22) that every time I do this process I get a slightly different result. Even on e.g. two consequent records of Track 1 sent to Track 2, I'll get different value for the offset. Moreover, when I change the requested block size, the recording is then completely off. Any ideas?
I think this is happening to everyone but no one is actually checking after "fixing it" the first time.
Reaper and Kenny Gioia is magic
Thanks for this explanation, very helpful! The difference between the driver-reported latency and your measured latency might also be caused by the output latency of your interface. In that case "overadjusting" the input latency would lead to misaligned, "premature" recordings. Anyway, thanks for sharing!
hey bro! Could you help me please? I have a focusrite 2i2 and when I record a track, it’s always before the click track, ahead the metronome. I already set the recording latency compensation, but the problem still there. Cheers
@@jcisternas Sounds like the latency compensation is not configured correctly (value too high). Have you tried disabling it in the Recording preferences?
@@oletrenner yes bro, I disabled it on recording preferences, but still the same
@@oletrenner yes bro, I disabled it on recording preferences but still the same :(
Yo, seriously brother. Great video! Thank you Kenny. You're really the GOAT!
Thanks Kenny, I’m overdue in adjusting mine and this is just what I needed!
Got any tips for when your latency differs everytime you run a test? Pretty sure there's several others who has the same issue of never having the same result twice. What's even more baffling is that the recorded audio has already been rendered halfway through the source audio, so it's like the reported latency has been taken into account even when it's unchecked.
This is confusing to me because the loopback's path is different than the path from a mic.
1) Mic to interface to Computer to reaper vs 2) Reaper/pc out to interface to computer to Reaper. Wouldn't the time it takes to go from mic to the interface be different than the time it takes in the loopback to go from Reaper/computer to interface?
Changing the buffer after setting the manual offset doesn’t give me the same result when recording at different buffer settings. I calculated mine at 128, but it only records accurately at 128. The test recording comes in earlier than the original track with lower buffer settings. With higher settings it’s still recording later than the original track. Any ideas?
Nuff respect dude👍🏽! Thanks
I tried this on my system. Unfortunately the latency is different every time when I record with the audio driver reported latency turned off. I took consecutive 4 records and the gap was 574, 571, 562, 583, etc. Any suggestion for this?
Thanks Kenny for your awesome videos as always!
Mine too, still not fixed
I´m experiencing the same issue, any clue on this?
Kenny you a gift. Thankyou for everything you do. ❤️
Hi Kenny, thanks for all the lessons to the community. You sure deserve more...
Now, this one means that if we make this right we can record with monitoring on or do i miss something.
Sorry if this is a stupid Q but i am new to this!
Thanks again!
This video was a game changer for me , I ended up leaving the box unchecked and left my samples at around 1024 . And am able to record my guitar with amplitube in perfect time!!! HUGE HELP!!!
Hey bro, didnt you noticed that your recorded guitar tracks seems to be earlier ahead of the click track? I have that problem and it’s so annoying
Incredible trick, as always... Ty Kenny, we all love you.
I think it's worth noting that the monitoring FX chain should be turned off during this test as any plugin inserted there would add to the output delay. Secondly, it seems that this delay is sampling rate dependent. In my case, I end up with 176 samples at both 44.1 and 48KHz, but 161 at 96KHz and 142 at 192 KHz.
If you mean monitoring fx on the master channel if you're sending audio directly to the hardware from the track it won't go through the master channel, but you probably mean any track fx you might have. It's best not to have any, just like in the video, just to be on the safe side.
Thanks Kenny...
It's so good to know..
Thank you Kenny! My new interface is somehow having a negative latency with the reported latency on, -16 samples. This just fixed that. Thank you!!
Yeah, this helps a lot! Love Reaper and Kenny! Best decision to switch to Reaper. Not only because of Reaper, but also because of Kenny's outstanding videos! Thank you!!!
Will a given calculated manual offset remain constant even under heavy cpu load?
@@alcoustic5297 yeah but you may have more than one track going. If you are soloing a single track to be recorded using this method, then yes. All I'm asking is if the sample offset is relevant to other tracks playing with plugins on them at the same time or not.
@@msuscorpio no it's not relevant
How does this adjustment affect previously recorded material? My concern is for adding tracks - I know it won't change previously recorded tracks
I'll be attempting this tomorrow..thanks
Hello. When working with iD14 mk2 there is a problem with the delay. After the loopback test, I manually adjust the delay of 33 samples. After which I reboot the computer and do the loopback test again and get 40 samples (the number varies within +- 20 samples). Latency can also change during one session. I work at 48 kHz and a buffer of 128 samples in Reaper 7, Windows 11 OS.
Very important and useful tutorial/instruction video! Thank you, Kenny!
Thank you Kenny for this very important video helps a lot to not have latency in our recordings!!!
OMFG - I just did this and it is freakin' brilliant! I salute you Mr. G!!!!
4:28 Need some extra help here. Could someone tell me how can I record without using Ctrl+R, Kenny apparently managed to record as soon as he hit the Kick key. Instead of having to press Ctrl+R and then the Kick.
Also, another novice question, 4:10 what's exactly what needs to be leveled, volume on both recordings? I didn't get that part either.
Thanks to anyone who bothered to read me and reply!
Thank you.... for this info.... I will.... be sure.................. to try it.......... out!
this is exactly what I needed.
while recording overdub in the 2nd, 3rd, etc tracks, can we hear the previously recorded tracks in the monitor speakers and / or headphones?
I'd like to hear the formerly recorded tracks, so that I can play another instrument over that.
Is this test valid? You're sending a signal out of the device and back in. So you're dealing with DA conversion and AD conversion. Seems like the sample offset should set to like half most of the time because you're normally only dealing with AD conversion, no? Unless you're using this to output to hardware and back in with ReaInsert or something...
Thanks 1000 Kenny! You are always the best.
While I'm very grateful for this help I'm well over my head on many of the technical functions mentioned here. I wish you'd made one video for PC's and one for Macs as I struggle to follow as it switches back and forth. One example is at 1:19 for a Mac with block size checked and 48000 sample rate but unchecked and 1:53 for a PC with block size unchecked and sample rate checked 44100. So this sent me off trying to figure out what my settings there should be. For people like me, that are just barely hanging on as they try to follow, this combination of Mac and PC made it more complicated. Thanks for the advice though.
Great information. Thank you Kenny!
Thank you Kenny 🎈
Great video! just tried with my apogee symphony mk1 and the reported latency is perfect!
Hi Kenny. I was excited to finally try this. I used the same interface you seemed to use in your test. However, I get inconsistent results. Every time I repeat the test, the result is different. I SO wanted this to work. Ah well. Thanks anyway! Hope you're doing well.
I´m experiencing the same issue, any clue on this?
Wow this is super cool. Everything is answered ! I feel ashamed for recording wrong this whole time by a few samples I guess....
By the way I have to play the video at 2x speed to stay awake, but it's because I'm in know territory.
Thanks !
Hi, I'm trying to follow this tutorial, I got the setup, but I'm stuck on how to make the recording. How do I play the kickdrum at the same time I hit Record?
I have the opposite problem. I have look ahead issues. I did the loop back test to see by just how much and the recorded kick is 735 samples ahead of the original kick.
I thought ok instead of adding samples I'll subtract them with -735. It had no effect. I've been looking for solutions to this problem and have had no luck. Any suggestions Kenny?
My device is over compensating so that what I record gets offset earlier than it should. Do I just put a minus figure in that box, or should I switch 'use audio driver reported latency' off and then add my plus figure (which is 9314 samples!!!). I tried that but then it's still not right. It comes out early again.
I don't know if I'm having a latency problem or something else. Now when I strum my guitar there is no sound but if I strum it hard the sound comes on a bit late and then it seems to sustain and then the sound just drops off. I need some help please.
Could any of the latency be coming from the output side of things? Would the amount of latency be different coming from, say an instrument line-in? I have no idea if there's "output latency" on computer + audio interface setups.
Interesting point. You will be performing to what you hear coming out of the output so the output latency ( time between Reaper sending a sample and it being heard on the output ) may not actually matter at all. Great video from Kenny (as always).
Can this be done with the Focusrite Clarett+ 4pre? Mine doesn't seem to have the loopback feature on it. Is there another way to test latency?
Love these videos! ❤
Yessir this saved my day. I’m recording my first live performer today using reaper.
Great video as always Kenny! Quick question, why didn't you use the actual latency found during the loopback test? Just curious.
im new to all this but even though this video makes complete sense to me i am having trouble recording to the second chanel. No matter which input i chose (my options are input-mono(left , right) or input-stereo(left/right) i am not getting any levels to record. Can someone help me please?
I need help: My audio interface's (IK Multimedia Axe I/O) reported latency constantly chnges.
I've tested using the RTL utility, reainsert, as well as just recording a kick sample from the input to output of the interface and checking the difference in samples on the timeline in reaper. And with these individual tests there can be a difference of up to 80 samples the next time I run it.
This is all usually at 48kHz sample rate and 64 buffer size. So that 80 sample difference translates to a difference of over 1.5 ms latency.
Is this normal? If not, does anyone know what could be the issue?
Awesome, however my results diverge when I change the Request Block Size - ie the marker no longer lines up with the recording.. any ideas what's going on? (FYI my required offset was only 5 samples)
The issue I'm having is when playing to Reaper's built in metronome, the recording itself starts either early, or the metronome is early which results in roughly half the first beat cut off. Any fixes for that with a Scarlett 2i2?
Thanks Kenny, love your channel, helps out A LOT.
Big hugs, cheers!
Why is it that when I recorded a sample (kick sample @44100) that my recording is not late, but it was ahead by 323 samples? I measure it from the sample's 0 threshold, backwards to my recorded output's 0 threshold. am I doing something wrong? PRettty sure I followed this vid to the letter (reported latency is turned on, audio interface is plugged in to the headphone jack instead of output.....something's weird.
I see I have already commented on this vid.
i tried the loopback test but whenever I change the buffer size it again doesn't line up. In other words I would need a custom setting for every buffer size.
Additionally the latency seems to vary 3 buffers with every recording.
1) Does anyone have the same problem?
2) Any ideas to fix that?
It seems to me that it might maybe be a driver issue, where the interface is always reporting a different latency to Reaper.
3) Could that be possible?
Gear used:
Windows 10 ; Focusrite Scarlett 2i2 2nd Gen
Anyway thanks for the great video!
I think most people are having this issue but not checking it after "fixing" it the first time. Have you found a solution or decided to live with it?
OMG Thank you! Off I go to fix this setting. All this time I thought my performances were off. Which is still very possible But at least I'll know!
💯
i was just 5 sample off but still now i can totally nail it! thank you so much!!!