Currently testing Ardour 9. When changing the track (i.e. clicking on the track) Ardour is changing connections of the virtual midi keyboard as shown below. In one project this is causing xruns, while in the other project it is not. In both projects the tracks have VST on it, but I can’t figure out why one is clicking and the other one not. Are xruns expected when such midi connections are changed?
Yes, in general changing connections is not click-free. But … “one set of connections” vs “a different set of connections” should not cause xruns.
Thanks, what do you mean with " “one set of connections” vs “a different set of connections” should not cause xruns."?
There are no connection patterns that by themselves would cause xruns. So you could wire things up like this or like that … neither case would have xruns caused by the wiring itself.
In general: the higher the DSP load, the more likely you will get xruns when changing connections.
For connection changes: processing stops, the change is applied, then a new process-graph is generated (the order in which JACK applications are called may have changed) and then processing resumes. – all this takes time, and if that time is longer than the process cycle there is a dropout.
–
PS. jack2 has some async mode option (1 cycle extra latency) that can offer click-free connection changes. IFF there is no signal on the audio port that is dis/connected.
PPS. you can disable automation connections on selection in Ardour > Preferences > MIDI
1 Like
If you mean that there are no xruns due to the connections once the connections are done yes that’s clear. Xruns only occurs when I change the connection. Will keep an eye on it to see what is triggering it.
we expect xruns to be possible during connections changing, in general.
1 Like
Thanks, already tried deactivating it. This of course solves it. DSP load shown in Ardour of the “clicking project” is 6%.