On Thu, May 05, 2011 at 06:31:42PM +0200, Lieven Moors wrote: > On Thu, May 05, 2011 at 06:24:54PM +0200, Lieven Moors wrote: > > On Thu, May 05, 2011 at 12:20:09PM -0400, Paul Davis wrote: > > > On Thu, May 5, 2011 at 12:14 PM, Lieven Moors <[email protected]> > > > wrote: > > > > Hi, I just discovered that aj-snapshot fails to connect > > > > a2jmidid ports that appear in jack midi. > > > > > > > > I store connections by seperating the client and port name > > > > from what jack_get_ports returns, and I restore connections by > > > > concatenating those as port names again (with a seperating colon). > > > > This seems to work with most clients, but not with a2jmidid. > > > > > > > > Does anyone know what the problem might be? > > > > > > what are the failing portnames? > > > > e.g.: > > > > Failed to connect port 'a2j:Midi Through [14] (capture)' to 'yoshimi:midi > > in' ! > > Failed to connect port 'a2j:Midi Through [14] (capture)' to 'a2j:TiMidity > > [128] (playback): TiMidity port 0' ! > > This seems to work though: > > Connecting port 'jack-keyboard:midi_out' with 'a2j:TiMidity [128] (playback): > TiMidity port 0' > > I'll have to do some more testing... > Just thought there might have been something obvious.
It looks like connecting from a2jmidid output ports to other clients does not work. But connecting to a2jmidid's input ports does. Strange... _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
