Yo, back on Friday, May 14, 2010 Andrew C was all like:
You don't need to connect the two in any way. Klick just servers to set the tempo so that all jack-transport aware apps stay in sync with the same tempo.
Arpage gets it's timing from jack, so unless there is an jack client program connected that is setting the beat / tempo, Arpage won't do anything. This also helps so that if you have other applications like a jack transport aware sequencer of sort, the timing of Arpage and the sequencer will match up.
The downside to a CLI app like klick is that it's not practical to do something like tap tempo or change the tempo somehow with out restarting it. (There is a GUI front end for klick called gtklick that allows tap tempo or manually changing the tempo, but it doesn't activate the jack-transport-master functionality, which totally defeats the purpose.)
Linux-audio-user mailing list