On Sat, 2013-02-23 at 20:19 +0000, Fons Adriaensen wrote:
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(a)lavabit.com> 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.
So I can repeat myself ;).
a2jmidi + alsarawmidi for jack2 are a nice combination to get rid of hw
MIDI jitter.
Regards,
Ralf
OT PS: I didn't use audio with my new Arch install and while I wrote
this mail I noticed ...
[root@archlinux rocketmouse]# jackd --help
[snip]
Could not open component .so '/usr/lib/jack/jack_firewire.so':
libffado.so.2: cannot open shared object file: No such file or directory
Could not open component .so '/usr/lib/jack/jack_firewire.so':
libffado.so.2: cannot open shared object file: No such file or directory
jack_get_descriptor : dll jack_firewire.so is not a driver
Segmentation fault (core dumped)
[root@archlinux rocketmouse]# pacman -Qi jack2
Name : jack2
Version : 1.9.9.5-1
URL :
http://jackaudio.org/
Licenses : GPL
Groups : None
Provides : jack jackmp jackdmp jackdbus
Depends On : libsamplerate celt
Optional Deps : libffado: FireWire support
dbus-core: jackdbus
python2: jack_control
Required By : None
Conflicts With : jack
Replaces : None
Installed Size : 3132.00 KiB
Packager : Rashif Rahman (Ray) <schiv(a)archlinux.org>
Architecture : x86_64
Build Date : Mon 10 Dec 2012 10:10:29 PM CET
Install Date : Tue 19 Feb 2013 06:17:18 AM CET
Install Reason : Explicitly installed
Install Script : No
Description : The next-generation JACK with SMP support
One issue fixed and the next appeared soon :D.