the last time i touched a2jmidi, it did precisely what you were looking for - 1 period of latency, zero jitter.
however, i do not maintain a2jmidid (it is not my project) and i have no idea what has happened to it since I last did any work on it.On Fri, Jul 26, 2013 at 9:04 AM, Fons Adriaensen <fons@xxxxxxxxxxxxxx> wrote:
On Fri, Jul 26, 2013 at 08:07:51AM -0400, Paul Davis wrote:This made me have a look at the sources.
> yes, absolutely. the only reason that -X raw and -X seq have not been
> removed is that the code to replace them isn't ready. always use a2jmidid
> (with -e to pick up external h/w ports).
Up to ten minutes ago I was believing that a2jmidid used timestamps etc.
to reduce jitter, and that this made it preferable over Jack's -X.
But apparently it doesn't, all events in the same Jack period are
just bunched together. There's even a comment in the source code:
/* -FIX- this should have the frame time of the event, instead of '0': */
So what is the advantage ?
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
