On Sat, Feb 23, 2013 at 01:09:28PM -0500, Paul Davis wrote:
> On Sat, Feb 23, 2013 at 11:16 AM, Johannes Kroll <jkroll@email-addr-hidden> wrote:
>
> >
> > I don't know if there's such a tool. But AFAIK jack would only block
> > the raw MIDI device when you use "-X raw" to use the raw MIDI driver in
> > jack. Do you need that driver? If you don't, you can use the "seq"
> >
>
> to reiterate: if timing matters to you, do NOT use -X raw or -X seq.
>
> use a2jmidid -e instead.
Are there any technical reasons why whatever method a2jmidi
is using is not adopted for the backend ? Maybe it's just a
matter of manpower, but OTOH this situation with the backend
failing to do 'the right thing' has existed for quite some
time now.
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@email-addr-hidden http://lists.linuxaudio.org/listinfo/linux-audio-userReceived on Sun Feb 24 00:15:04 2013
This archive was generated by hypermail 2.1.8 : Sun Feb 24 2013 - 00:15:04 EET