Hi there,

I'm using a 64bit pd-extended .deb package with jack 0.109.2 on a DualCore laptop, under UbuntuStudion Hardy 8.04.

I noticed that every "note on" or "note off" midi message leads to an "ALSA: connection graph change" in my 'messages' window of Jack. (It might also occur with other msgs but I didn't test it yet)

This problem doesn't occur on another pc, with the same usb card, and the same distro, but a 32bit one with a "generic" 32bit pd-extended version that I installed from sources.

As I send such msgs every 10ms in a simple 'midifier' patch of mine, this also leads to problems, even though I see no xruns banging. I guess that this flow of "connection graph change" encountered by jackd slows down the whole process, and sometimes leads to bad midi communication with my device (midi expander plugged to the card).

Any idea of what's happening ?
Would it be a 64bit issue, or rather a known jackd bug solved in a more recent version of jackd ?

Thanx

Nau

Hi (nobody ?),

I answer my own message, adding more info (not solved yet).

Then same behaviour occurs on a freshly installed 32bit distro.
Other clients than PD don't lead to the "odd connection graph changes" (i.e. virtual Keyboard sends notes to my card without showing "odd connection graph change").
Card : intel HDA, n=3

Any idea ?

Nau

Hi,
Exactly the same problem... Happens with all midi out objects ([midiout] [ctlout] [noteout])
It's not a 64bit issue, I'm running Ubuntu Studio 9.10 32bit, and I confirm other clients (Ardour, etc) doesn't make any problem. I tried both internal HDA and FA-101 (wih FFADO drivers).

pd-vanilla 0.41.4 from Karmic repos... (who knows when extended compilation for Karmic will be released?)

Ok, I get a "hack" on PD-List:
start PD with args:

$ pd -alsamidi -mididev 1,1

No more graph connection change...
Will create two pd midi clients (ch 1-16 & 17-32), and midi autoconnect won't work anymore (which is better I thing)

Enjoy

Oh thanx, I'll try it as soon as possible !