Delay in start of recorded region

Getting Stuff Done How do I .... ?
#1

Ardour 7.2
If I go to 25|0|0000 and hit record, the recorded region starts at 25|01|0492.
Any ideas?
Thanks

#2

Sadly, this is insufficient information to be able to answer this question. It sounds as if latency compensation is not doing what it is intended to do, which could be caused by a variety of different things. Connections, plugins that don’t report latency, lack of hardware latency measurement, track compensation mode and much more. In general, in a new default session this should (and does) just work.

I would suggest filing a bug report at https://tracker.ardour.org/ and attach a (small) session that demonstrates this behavior.

#3

I started a new empty session and found that I no longer had this problem. Then I noticed that ‘external positional sync’ was set to Int. I normally use Jack (for hydrogen). When I set ‘external positional sync’ to Jack the problem came back.

1 Like
#4

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.