How to: FIX RECORD LATENCY SHIFTS IN CUBASE (Part #1)

[@NikosAchilleus]

Thank you my friend! Man, this was helpful! Countless times I've wondered how everything is recorded earlier....well, latency shifts!

[@NewSonicLight]

@D Rocks Records -- Thank you very much. Having a clinical anxiety disorder makes me panic for the smallest thing and blow thing out of proportion, so every time I get an "Oh, OK, that CAN be fixed moment..." is soul relief. :)

[@kevfly21]

Great info.. small precision: 34 x 1000 = 34000. 3400 = 34 x 100

[@DRocksRecords]

You're right, I was doing the right thing and saying the wrong word :D Thanks for commenting.

[@tomykryl62]

Can't say how grateful I am for this video, thank you so much my friend!!!

[@Redbunker]

just a tip , often audio engineers pre calculate this thing by a default number, the reason why you see the recording before the real hit is because they calculate the delay by a standard cable length, so they anticipate the recordings by a standard value .. because you will always use cable longer than 1/2 mt if you record something.. I just did this test with my audiocard and routed everything with my pachbay wich result in 7/8 mt of cables length and my result is slighty after ... probably if I route everything with 30 cm cables I will have a "before " value ... anyway now is perfect in time with your help thanks

[@DRocksRecords]

Thanks. This is insightful details. I never thought of cable length!

[@yehonatanfranco]

Thanks men! Really helpful! I wonder why its happen in the first place...

[@DRocksRecords]

Yehonatan Franco - יהונתן פרנקו Youre very welcomed :) Yeah I also wonder why sometimes its not fixed automatically by Cubase. Probably linked to our audio interfaces drivers. I still have an old firewire Firestudio tube that is discontinued

[@ophirgal9585]

Super helpful, just what I needed to fix my issue, thank you!!

[@kobalt77]

Thank you ................... I never knew what the Range tool was for..... excellent !

[@DRocksRecords]

Hey that's good to read! Thanks for your comment.

[@Scipheord]

Thank you You saved me from a lot of headache!

[@hoomtal]

Thanks a Zillion Man! Perfect Tutorial!

[@dooorpaaar]

Great help buddy..just encountered this problem in cubase 10 elements..I’ll see to solve it with your help tonight..thanks

[@DRocksRecords]

Thanks for your comment! It sucks that it happens sometime but I hope you get this right easily and can move on to making music fast

[@ezasjad]

It depends what sample rate are you using ....

[@audiofrank6747]

Thank you sir! Fix my problem!

[@L.PAudioWorkshop]

The latency issue is not from Cubase but from the ASIO driver. If you try a different sound card you gonna have different latencies. Also if you change the sample rate, you have to adjust again the record shift. BTW I think the value you enter in record shift is in samples not milliseconds.

[@DRocksRecords]

+Lazaros Palaskas Thanks so much for your precisions! Yes you're right the problem is not Cubase itself - when it's about the latency and that the audio card and buffer size will affect all of this. At first, before doing the video, I tried just about anything like changing BUFFER size, activate and deactivate ADJUST FOR RECORD LATENCY box, activate and deactivate CONSTRAIN DELAY COMPENSATION etc in all different combos... Well, I still had the same RECORD SHIFT problem which is normally handled by Cubase without doing anything (Yes, I tried restarting computer, DAW, and interface). That's why I had to find out how to shift the recordings back in time manually. And the wierd thing is that the day after the video my Cubase could record correctly without any manual shifting. This also led me to verify if my informstion was 100% accurate in this video and found a new faster and easier method to calculate the record shift value right from the Studio setup infos.. Could you please check part #2 on my Audio Latency Knowledge playlist and see if the answer is helpful to close the issue with record shifting? As I said the Cubase manual is almost silent about this so I have to figure out alone and with forums.. and KZbin :D Thanks again man Alex

[@L.PAudioWorkshop]

Hello Alex. I did check part 2 of you video and i did a test with my PC. First of all i was wrong that the record shift is in samples, sorry for that. Second is that in my setup with my audio interface (Digi Rack 002) with 256 buffer size i have 7.800 input and 7.800 output latency, and for me the perfect record shift number is at 176. So your math in my case is not correct. The weird thing is even if i change the buffer size to 1024 and the input latency is 25.xxx and the output 25.xxx the record shift needs to stay as before. So in my case with the number 176 i am fine with ANY in and output latency. I have to change the record shift ONLY when i change sample rate lets say all the tests are in 44.1khz and i change to 96khz then the record shift has to be at 422. Sorry for the long post but my conclusion is that: every soundcard/ASIO driver needs his own setup and there is no math for that. Test and set it to the right value.

[@DRocksRecords]

That's great info again thanks! But wow it is surprising that it behaves in different ways. I hope Steinberg will add more exact details in the manual in the future. If you find anything else please let me know again. Good news is that both of us have fixed the issue :D

[@DRocksRecords]

Lazaros Palaskas btw: did you test it with a similar recording output and input method that I tried? Or What was your method?

[@L.PAudioWorkshop]

Knowledge has to be shared that's why we have to communicate and solve problems. :) I was thinking that every computer has different parts inside and everything can be leading to different results that's why i'm saying that every user has to make his own adjustments. Hope that any user finds the right setup/adjustments for hisself.

[@zoanoids2083]

Thanks for sharing this, super helpful! 🤘

[@garethmillers5453]

Very helpful. Thank you.

[@DRocksRecords]

Gareth Millers you're welcome :)

[@infestedalien]

Thats a handy method in cubase. I made a macro to correct a latency i get when doing some external processing for outboard i cannot use external fx setup for.

[@rowbocaster]

Thanks so very much, you have given me back my sanity!

[@DRocksRecords]

Haha! Yeah...I understand that, you're welcome rowbocaster :D

[@tfbremer]

I feel the same way! I thought I was rushing for years! I’m not crazy!

[@ramizgokbudak2315]

Thanks for this helpful video !

[@DRocksRecords]

Youre welcome Ramiz :) thanks for taking time to leave a comment

[@DenBartoloMusic]

Thank you, it works for me, you save my day

[@DanielDixon92]

Absolute life saver! I thought I was out of time all along pahahahaha

[@rowlandstraylight]

Really useful. Thanks.

[@DRocksRecords]

StraylightGuitars thats great :) Thanks for taking time to let me know.

[@georgephilis]

Many thanks for this great and very helpful tip (and for part 2 also) :-)

[@DRocksRecords]

You're welcome George! And thank you also for your comment :D

[@brunorivas7013]

Hi thanks for this video ! ive set mine to 32! dont ask me why but its works in every sample rate

[@DRocksRecords]

Bruno Rivas thats great! Youre welcome. Im still impressed that a video like this was not already adressed by Steinberg themselves with more knowledge from the developpers. Its such an important thing :D

[@miltonex]

Wow thank you very much you Rock!!!!

[@GuitareAvecSly]

Thanks man !

[@stevenochan9780]

Thank you so much Alex. Great helpful vid. ThNx buddy. I wonder if a similar technique would work for Vocals/audio that get recorded many tones(pitch) lower than the actual input. My vocals go down into a completely different key for some reason(the vocals surely arent that bad). 🤔😏🙄😁 Keep fab

[@DRocksRecords]

Hey thanks for your comment Steven :D Well for that pitch recording issue, it sounds to me like a Sample Rate / Playback rate problem. There is probably a difference between your Recording sample rate (for example 44khz) and your software might playback at a different rate like maybe (48khz or 96khz). If it is the case then surely the sound will pitch up or down because it plays either faster or slower than when you recorded it. Try to check this and I hope it helps you :D cheers

[@secretpilgrimage6879]

Thank you Sir !!!

[@DRocksRecords]

My pleasure!

[@produzee]

wow, what a relieve mine was 2100sample thanks

[@ObservatoireProduction]

You saved me

[@soumyaranjanofficial1221]

Thanks bro. Its solved. But the lenth was .7 and my latency solved with +415 of saple rate input

[@barewolf3]

Excellent

[@Baark]

You're great! Thanks a lot!

[@DRocksRecords]

You are welcomed. Thanks for your time to comment!

[@owinoyoungboyramji]

halo sir i have done all that but when i add a multiband compressor the vocals or audio still lugs

[@DRocksRecords]

Hi, I think this is another kind of problem if you are recording with plugins on the input it probably changes the way cubase handles the latency compensation. I'm sorry this is not something I have tested and I can't help you more. Please tell us if you find a video or article on the subject. thanks.

[@nathanreddent2427]

In studio one this is called offset. Is there a way to set this with midi also?

[@spnova6960]

YOU SAVED ME ~

[@GSSahuwalaSahuwala]

Very nice sr,thank

[@mjvicky1997]

Sir after install cubase 9.0.30 when I'm opening it, there are no timeline, mixer and if i add track from project menu the screen Doesn't chang. There have just uper and lower tools.. Please tall me how to fix it..

[@AleLoy]

thanks very much man

[@DRocksRecords]

Youre welcome Ale. Thanks for taking time to comment :)

[@n.l.541]

What to do if every synth comes with its own latency? Can you make this shift correction on a track basis?

[@DRocksRecords]

Im not an expert but I think you should never worry about this unless you really find a problem with your synchronisation. By default every track delay should be handled by Cubase or any other modern DAW. The recordshifting is more like a rescue setting when things are not aligned by default. But I never had to align tracks one by one and should never be the case otherwise it would be a nightmare to synchronise everything. So dont worry about that unless you find your tracks dont align with your project tempo.

[@Artinmotionmusic]

@@DRocksRecords all my external gear when recorded gets a small delay, is never perfectly on the grid. record shift doesnt work. and i have the minimum latency allowed, 32. steinberg cant help with that! On ableton it syncs perfectly.

[@alex-desroches]

@@Artinmotionmusic This is wierd. Probably a driver problem (easy to think that but it can be many factors). What audio interface do you have?

[@Artinmotionmusic]

Alexandre Desroches i have an UAD and a brand new mac. If your project has a swing do you manage to record with the swing as well ?

[@DRocksRecords]

@@Artinmotionmusic man thats wierd youre full equipped this should be fine. Im sorry please see with Cubase support or UAD to see why they dont sync together. Good luck that sucks

[@iamkrysten1136]

Hey man I tried your process, just didn't work the more I tweaked the more it shifted either more to the right or to the left

[@DRocksRecords]

Hey its probably because you dont have a problem in the first place. Also this is just how it works I did not come up with that trick. This resolves a wierd an unpredictable issue that can happen but it should never happen in an ideal world. It theorically is all handled by Cubase by default. Sometimes its not aligned and thats when you would try manual shifting.

[@iamkrysten1136]

@@DRocksRecords still having serious issues I can't use it to record just mastering, cuz it take lower CPU usage than flstudio

[@farid6491]

if you change your buffer size you will have another result. do not forget in/ out latencies

[@freemindas]

Does this work for midi ?

[@Skiroy]

Does this have to be redone if you change song tempo for midi projects?

[@DRocksRecords]

good question, probably. But to be honest this should not be the case. I hope for you that the problem will not be problematic to that point!

[@rupeshshrestha9870]

Awesome

[@JoeyAyalaMandiriwa]

Thank you Alex :-)

[@Skiroy]

Is this latency cause by the interface or CPU or both?

[@DRocksRecords]

I never found an answer to that sorry

[@ElleEllie9]

THANKYOUUUUU

[@streetlogic]

you mean times 100

[@DRocksRecords]

Yes thank you for pointing this out. Probably my french translation to english had latency on that one :D

[@xdeville1]

@@DRocksRecords french haha i thought it was russian dialect

[@streetlogic]

sorry but 34 * 1000 is not 3400 lol sorry

[@DRocksRecords]

Hahaha you're the first one to notice! Yeah my bad I have mentionned the error in the description. Thanks for being alert :D

[@LonnBaker]

This is not Latency - Cubase is Shifting the recording... Why? It seems as though Cubase is guessing some value of latency and shifting the recording.

[@projectmayhemband443]

*Times 100*

[@froglogdogtog]

Why the hell is this even a problem? I'm having the same problem on both protools and ableton on two different rigs and it haunts me how long i've been having this problem with out even knowing. It's the most basic function of a recording system to record overdubs in sync WTF.

[@BANDATEPUYOFICIAL]

Very helpful. Thank you.

[@victorescobar1697]

thank you man!