Hi. I have Cubase 15 and have a problem with audio recording a little behind the barline. I am using Volt 4 and I have been looking into most aspects of the recording, but hoping someone could give me a tip on what to do. On the pics one is not quantized and one is quantized. Very annoying.
Obviously weâd need to know exactly what youâre recording and how thatâs being triggered exactly on the beat??
1 Like
First is it actually played in time? 2nd it is the interface that reports to Cubase. If the driver is not properly designed or you are using the wrong one then it may report back wrong, therefore audio being in the wrong place. Have you tried sending a quantised drum beat out and back in to record it to check out the timing?
I have used the clicktrack to record via an external mic and the delay is constant throughout. On any audio recorded.
Did you put the microphone directly in front of the speakers? Because air has latency, the speed of sound is ~343m/s, roughly 3ms of delay per meter.
Those kind of tests should better be done with a loopback cable, from the line out of your interface to the line input, and record that.
The RTL utility (https://oblique-audio.com/rtl-utility.php#should_reported_rtl_match_measured) can more or less automate that and show you precise values.
It is actually possible that recorded audio is not positioned correctly. Cubase uses the driverâs latency information to correctly position the audio, but if that information is not fully correct, there can a discrepancy. If this happens, you can try to correct that in StudioSetupâAudioSystemâRecord Shift.
Donât know how often this happens nowadays in reality, maybe it is something else.
The Volt 4 has a USB-c on the back- I changed it for a regular cable and all was good.
Can you elaborate on what you mean by a âregular cableâ?
I canât for the life of me think of a way that a USB-C cable would add recording latency.
Pete
Microsoft
1 Like
Do you mean usb A at the PC end? It could be that it was on a different controller. I have seen on the RME forum where there were problems on different usb controllers.
If it works now then all is well. I hate the usb C size as itâs not a solid connection like usb A
No, I have C in both ends.
Is your recording latency offset set to blank or 0 in Audio Device Settings?
I have this problem too, and it is due to the latency in the interface. I have requested a manual adjustment capability from Steinberg to no avail. The automatic latency calc in the Steinberg ASIO driver doesnât get things right all the time, leading to the delay you see in your recording. My Focusright ASIO driver gets it spot on, but doesnât allow me to use the high quality audio out interface I have on my DAW PC, hence using the Steinberg ASIO.
I end up turning off snap to grid and just manually aligning audio with the bar timing. Works fine, just a pity Steinberg refuse to allow a manual offset to obfuscate needing to do any dragânâdropâŚ.
âRecord shiftâ should do it, shouldnât it?
It gets close, but for some reason since I updated to Win11, it doesnât seem to give the same result every time (Win10 didnât seem to have a problem). Iâm very picky about the audio sync to midi tracks and I pretty much always end up refining by dragging the audio.
It might just be my setup, but I think I canât be the only one as the original poster highlights.
EDIT - Iâve just tried changing Record Shift values, just to recheck for completeness sake and it makes no difference to the record latency at all now. Registering another bug with Steinberg. Updating to Windows 11 has not been kind to my previously stable DAW setup
No, this works entirely as intended, no bug there. The purpose of Record shift is to be able to manually compensate for ASIO drivers that report incorrect values to Cubase.
You can confirm it with a loopback test (render a metronome track to audio track with a line output of your interface configured, connect the line out to a line input, record that on another track.
Here is the result of such a test, on Win11 with my RME UCX.
This is not about MIDI, that is an entirely different area and hasnât been subject of this topic. If you have issues there, it would perhaps be better if you create a separate topic and describe exactly what you are doing, what you expect the results to be and what the results are (assuming you already have searched the forum for similar problems).
1 Like
Thanks Fese. Your pointers have helped identify a real problem with my system.
I just reinstalled Cubase afresh and it has cured a number of bugs - the record shift was not working previously; Iâve just checked it again and now I get recording movement vs system latency. It also solved a scroll bar problem, a sound dropout issue and an MP3 export issue. All of these appear to have come when I updated to Win11 just as upgrade to Win10. Customer support literally suggested a reinstall as I was replying to this forum.
So, to answer Oddvar Ruudâs original question - Fese is correct.
Go to Studio > Studio Setup > Audio System > Advanced Options, then ensure âAdjust for Record Latencyâ is ticked and try a value of 7000 - 7500 Samples for Record Shift and play around until itâs synced more accurately with your bars start.
For anyone having issues with it not working (or any oddities that happen), try uninstalling Cubase and reinstalling - it cured a very frustrating time for me!
When it comes to ASIO drivers, Windows is not at all in the path. Cubase talks to the ASIO DLL which talks to the hardware driver. Our native audio stack isnât involved. So Windows 10/ Windows 11 wonât really matter there when it comes to driver latency calculation.
Pete
Microsoft
Pete, my problem was nothing to do with ASIO drivers - upgrading Win10 to Win11 made my existing install of Cubase unstable on a number of counts that caused Steinberg customer services a lot of head-scratching. Re-installing Cubase solved my issue. The topic creatorâs issue should be solved by Feseâs solution, so best to see if it worked and concentrate on whether Oddvar Ruud has any further issues.
1 Like