Content-Type: text/plain; charset=ISO-8859-1
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 wrote:
> On Fri, Jul 26, 2013 at 08:07:51AM -0400, Paul Davis wrote:
Content-Type: text/html; charset=ISO-8859-1
the last time i touched a2jmidi, it did precisely wha=
t you were looking for - 1 period of latency, zero jitter. ho=
wever, 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.
Jul 26, 2013 at 9:04 AM, Fons Adriaensen <email@example.com> wrote:
On Fri, Jul 26, 2013 at 08=
:07:51AM -0400, Paul Davis wrote:
> yes, absolutely. the only reason that -X raw and -X seq have not been<=
This made me have a look at the sources.
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:
=A0/* -FIX- this should have the frame time of the event, instead of '0=
So what is the advantage ?
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