25 Dec
2009
25 Dec
'09
5:01 a.m.
On Thu, 2009-12-24 at 20:36 -0800, Ken Restivo wrote:
This is driving me nuts.
When I use the "-X seq" argument to JACK with JACK MIDI, it makes a bunch of
bogus connections for EVERY synth, that get reported by ALSA via aconnect -lio,x and make
it unreadable. i.e.
Connecting To: 128:0[real:0]
Connecting To: 128:0[real:0]
Connecting To: 128:0[real:0]
Connecting To: 128:0[real:0]
.... spam spam spam spam..... on every port, of every synth. On my setup, this line gets
repeated 28 times.
We've got 128:0, we've got [real:0], we've got 128:0 and [real:0], we've
got [real:0] and 128:0, we got.....
But I don't LIKE 128:0[real:0]!
In fact, there isn't any such synth! It doesn't exist at all, according to
aconnect. I'm listing the available ALSA MIDI devices, and... other than 0: System,
the synths start at 130. There is no 128. It is connected to nowhere. is a ghost device?
What's up with this? Is there a way to make it stop?
128:0 will in fact be jackd, which needs the connections so that it can
expose their events to the jack midi world...
You could make it stop by not using -X seq, which probably isn't very
useful.