Hi, At Sun, 09 Jun 2002 23:51:39 -0700, Erik Steffl wrote: > > I have an external midi controller (just a keyboard with midi out, no > sound) and I would like to use it to control sb live! internal synth. > Back in the old times aconnect 64:0 65:0 used to do the trick but now it > doesn't seem to be working. > > the following works: > > pmidi -p 65:0 jazz.mid > > so I guess midi is working ok, the soundfonts are loaded etc. > > here's what aconnect says (after aconnect 64:0 65:0): > > erik@cert:~/tmp/midi$ aconnect -i -l -o > client 0: 'System' [type=kernel] > 0 'Timer ' > 1 'Announce ' > Connecting To: 63:0 > client 64: 'External MIDI 0' [type=kernel] > 0 'MIDI 0-0 ' > Connecting To: 65:0 > client 65: 'Emu10k1 WaveTable' [type=kernel] > 0 'Emu10k1 Port 0 ' > Connected From: 64:0, 128:0 > 1 'Emu10k1 Port 1 ' > 2 'Emu10k1 Port 2 ' > 3 'Emu10k1 Port 3 ' > client 128: 'Client-128' [type=user] > 0 'port-0 ' > Connecting To: 65:0 > > so it shows that 64:0 is connected to 65:0 but I hear no sound when I > play keyboard. the keyboard is plugged in into 'midi in' connector on > front panel (it works in windows so HW is OK). > > btw the 128:0 is the pmidi, once the pmidi stop 128:0 disappears but > midi thru is still not working. > > what's the secret? TIA!
can you check whether the status on /proc/asound/card0/midi0 changes? it shows the rawmidi status. if any input really occurs, then the bytes shown in this file must increase. also, check /proc/asound/seq/clients how much the event is received and whether this number varies. Takashi _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
