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!

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

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!

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!

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.

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 by far one of the most important features of reaper. Thank you !!

Years using Reaper and adjusting all almost by "ear", thank you Kenny! Keep teaching, I'll keep learning!

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.

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!

🤯 Kenny is amazing! The things I've learned from him alone has saved years of time.

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!

yet again you've helped me fix a reoccurring issue (very much a pain in my behind) tysm man god bless u

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.

Thank you, thank you, thank you! This was driving me crazy! I thought that my "internal" timing was way off!

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.

only you have the solution.. wasted my time watching other junk videos.. thank you sir 🙏🙏🙏🙏

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!

Just can't thank you enough Mr. Gioia... Great Stuff!

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!

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 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 🙌🙌

You are the best for Reaper video's my friend !

Thank you!!! This video really solve a big problem of mine for years!!!

My interface is spot on, but its nice to know how i can adjust it. Never heard of this feature, thnx!

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!

Thank you Kenny for all this useful information, We as a community can't thank you enough!!

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 make this look like it's completely logical yet I would never have come up with this myself. Thanks man!

Reaper and Kenny Gioia is magic

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!

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

Thanks. New to the channel and it seems to be a banger. See you next time.

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

Great video and I was able to fix my latency problem almost instantly thanks to your help

Yo, seriously brother. Great video! Thank you Kenny. You're really the GOAT!

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!

Thanks Kenny, I’m overdue in adjusting mine and this is just what I needed!

Thanks Kenny... It's so good to know..

Incredible trick, as always... Ty Kenny, we all love you.

Nuff respect dude👍🏽! Thanks

Wohhooo. that is great. Thx as always Kenny!

Kenny you a gift. Thankyou for everything you do. ❤️

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!!!

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!!

Thank you.... for this info.... I will.... be sure.................. to try it.......... out!

OMFG - I just did this and it is freakin' brilliant! I salute you Mr. G!!!!

I'll be attempting this tomorrow..thanks

This was very helpful. Thank you. I use Studio one but the principle is the same.

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!

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!!!

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.

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!!

Thank you Kenny for this very important video helps a lot to not have latency in our recordings!!!

Thanks 1000 Kenny! You are always the best.

Great information. Thank you Kenny!

Very important and useful tutorial/instruction video! Thank you, Kenny!

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!

Great video! just tried with my apogee symphony mk1 and the reported latency is perfect!

Thank you Kenny 🎈

I love you Kenny. Seriously.

Yessir this saved my day. I’m recording my first live performer today using reaper.

i was just 5 sample off but still now i can totally nail it! thank you so much!!!

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

Love these videos! ❤

Thanks Kenny, love your channel, helps out A LOT. Big hugs, cheers!

Awesome! Just did it and works perfect!

Awesome Tip... Thanks man!!

This is a GAME CHANGER... thank u so much kenny... 🤘🤘🤘🤘🤘 more powers..

Kenny you're the best!

Great simple video, thanks very much

Very useful as always! keep it up!

Thank you!!! Very best channel.

Good to know. Thanks!

Kenny you are the best man...

Thank you Kenny.

Thank you for sharing your mad knowledge! You're a legend mate

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?

Awesome as usual Kenny !!!! You are the best !!!!! 🙂

Kenny, you're the best! I learned something new!

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?

Excellent, thank you so much Kenny !

As always, Great video Kenny. Thanks.

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.

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 !

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?

This is incredibly helpful, thank you very much!

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!

yo te amo, tenga su like buen hombre, usted es un dios, yo amo a la musica y al hombre/mujer que hizo este video

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.

Awesome and useful tip Kenny👍🏻

Wow, this saved my ass, thanks!

Great professional video!

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!