Uneven metronome???

[natas]

I did some metronome tempo changes because I figured the song would have tempo changes. I started recording a guitar under this changing metronome and then some vst instruments using the control keyboard. And I noticed two strange things. 
1.When I wanted to record from the secondiedo tempo, the countdown metronome before recording was at the tempo of the previous one and by the time it started recording the tempo had already changed to the second one. 
2. sometimes I had the impression that something was happening to the tempo of the metronome but I explained it by sitting too long in front of the comp and being tired.
So I performed an experiment of sorts. I fastened the output of the metronome to the aux and recorded to audio, and what was my surprise when it turned out that the click of the second tempo is not where the new tempo starts and is shifted. Is this due to latency? I did a similar experiment in another daw and there the waweform always started together with the tempo change marker. Do I have something set wrong?
PS. hope that what I wrote is understandable because I was using a translator

Translated with DeepL.com (free version)

[David Baay]

11 minutes ago, natas said:

So I performed an experiment of sorts. I fastened the output of the metronome to the aux and recorded to audio, and what was my surprise when it turned out that the click of the second tempo is not where the new tempo starts and is shifted.

What tempos, what buffer size, and how far off is the recording with the count-in? I did a quick test and unepectedly found a very small error in the timing of the click recorded with a 1-measure count-in enabled, but it was only about 16 samples (early) with a 128-sample ASIO buffer at 125bpm. Are you using ASIO mode?

[Sock Monkey]

I discovered a long time ago that if you do a loop back test using hardwired connections ASIO will for the most part be bang on. All other driver modes will be late. 

When I got my Motu M4 with built in loop back I thought great.  No more wires.  But when I tried the Loopback test the recording was early!  

This I assumed is because Cakewalk-Sonar has calibrated the known latency of the system and this is how it makes up for the difference. 
 

But later I bought a Zoom L8 and it didn’t do that. It was in sync?? 

Anyway not sure how you are recording the Aux track but it can definitely be due to latency and if you’re not using ASIO even more such. 

 

Edited December 12 by Sock Monkey

[natas]

Yes, indeed. For now, I use an integrated sound card, but I recorded guitars on a Blackstar ID Core 3 because it supposedly has a built-in USB interface, but there is no option to select drivers as ASIO, so it is not supported. So I guess it's time to equip myself with an audio interface. Although I am surprised that in another program, the click works. In fact, I will want to buy an interface in time, but I don't know if it makes sense to continue with Cakewalk, since I have a slight grind with this function. Sometimes it also seemed to me that I set, for example, the marker in line with Arranger, and after the next start, when I zoom in/enlarge the view, it turns out that everything is a bit out of sync. For example, I set the kick, vernel, bass, etc. and the next day I do the keys and strings, then it turns out that yes, the kick and bass play with the second guitar, but the strings have moved somewhere. Maybe it's a matter of accidentally selecting something and moving not only the track that I want to edit, but also others. Anyway, thanks for the answer and help.

[David Baay]

2 hours ago, Sock Monkey said:

I discovered a long time ago that if you do a loop back test using hardwired connections ASIO will for the most part be bang on. All other driver modes will be late. 

When I got my Motu M4 with built in loop back I thought great.  No more wires.  But when I tried the Loopback test the recording was early!  

The result of loopback recording depends on  record latency compensation; if your Manual Offset is dialed in to correct for the difference between the actual/measured latency and the driver-reported latency (almost never accurate) , the timing will be sample-accurate.

Recording internally to an Aux track via patch point has no latency and requires no record compensation. It should be sample-accurate regardless of count-in.