On Monday 24 December 2012 05:52:41 Pedro Lopez-Cabanillas wrote:
> I think that you are not getting more help here because a terminology
> confusion. This is only a guess, but I think that by "jack connections" you
> mean the lines that can be created in the "ALSA" tab of qjackctl. In that
> case, you are using the wrong name because those lines have nothing to do
> with jack. They are ALSA sequencer connections that can be made using
> other programs as well, like "aconnect". There is an ALSA API to create
> connections; look for "subscription" here:
> http://www.alsa-project.org/alsa-doc/alsa-lib/seq.html
>
> If you want to use jack midi instead, please clarify (and don't expect
> answers or interest from me.)
Well, that explains why there's a separate ALSA tab in QJackCtl. And, yes, I'm
using the ALSA tab to make my connections. So, at this point, it seems I don't
really need jack.
Just a side question: if I had an application that uses audio and midi (like
Sonar), who keeps them in sync? Is this ALSA or Jack?
> Assuming that you want to use the ALSA Sequencer, and not jack midi, I can
> provide some working examples.
>
> As per your request, a simple metronome program in C
> http://lalists.stanford.edu/lau/2009/08/att-0005/ametro.c