hi (just realized that i replyed directly to Will and not to the list; apologies for a dang old email use case mistake:)) On 9/19/19 3:21 PM, Rui Nuno Capela wrote: On 9/19/19 2:01 PM, Will Godfrey wrote: let's put it this way: jack2 implementation to "seq" (jack-midi) driver is an old decade+ and quite frankly outdated and flawed re. to timing and what not jack1 implementation, standing for the (-X) "alsamidi" for that matter, is independent if not the same as to running a2jmidid in the background, and as infrastructure (like IaaS, eh?:) also, on jack1, that goes straight and _independent_ of whether you run (-d) "alsa" driver at all; of course, only granted to work on linux, but otoh jack2 makes it locked-in to the "alsa" audio diver anyhow, so you get the picture. nb. on jack1, selecting (-X) "seq", as the preferred jack-midi driver _is_exactly_the_same_as_ running "a2jmidid -e &", so that wouldn't be a viable option no longer ;) and yes, to let my stanfd be clear enough, jack2 _shall_ make the "alsamidi" (internal client?) driver ported in from jack1 alright. for all the people that use jack2, please do and rely on good old a2jmidid--it just works at lot and way better than any other option (but jack1's;) cheers -- rncbc aka. Rui Nuno Capela rncbc(a)rncbc.org