web search finally revelaed that front panel midi in does not work -
joystick port works though (fortunately I happened to have a midi <->
joystick cable). I tested it and it works but:
when I turn off midi controller (keyboard) there is number of random
midi event (or at least it sounds like random sounds), the keyboard
doesn't work anymore, I have to reboot (at least I didn't know what else
to do). when I used the same keytboard with sb awe 64 (connected to
joystick port) I could turn off keyboard without any problems (and turn
it back and it continued to work). any ideas what's going on? at least
how to reset it back so that it works aghain (without reboot)
will front panel midi in be supported?
could it be mentioned/documented somewhere? it doesn't seem to be a
common knowledge (the fact that front panel midi in doesn't work).
erik
Erik Steffl wrote:
>
> this is a more specific version of my previous question about midi
> thru. It looks like for some reason the midi in (front panel connector)
> on my sb live doesn't work under linux (it works fine under windows so
> it's not a hw/cable problem). The rx field in /proc/asound/card0/midi0
> is always zero.
>
> btw midi out works, the number of tx bytes increases and I can hear
> the sound on external synth.
>
> my system:
>
> soundblaster live! platinum (using midi in and midi out on front
> panel)
>
> kernel 2.4.18
>
> alsa 0.9.0rc1-2 (that's debian version, AFAIK it's the second
> packaging of 0.9.0rc1)
>
> --------------------------------------------------------
> /proc/asound/card0/midi0:
>
> EMU10K1 MPU-401 (UART)
>
> Output 0
> Tx bytes : 16212
> Input 0
> Rx bytes : 0
> Buffer size : 4096
> Avail : 0
> Overruns : 0
>
> --------------------------------------------------------
> /proc/asound/seq/clients:
>
> Client info
> cur clients : 4
> peak clients : 5
> max clients : 192
>
> Client 0 : "System" [Kernel]
> Port 0 : "Timer" (Rwe-)
> Port 1 : "Announce" (R-e-)
> Connecting To: 63:0
> Client 63 : "OSS sequencer" [Kernel]
> Port 0 : "Receiver" (-we-)
> Connected From: 0:1
> Output pool :
> Pool size : 1024
> Cells in use : 0
> Peak cells in use : 0
> Alloc success : 0
> Alloc failures : 0
> Client 64 : "External MIDI 0" [Kernel]
> Port 0 : "MIDI 0-0" (RWeX)
> Connecting To: 65:0
> Client 65 : "Emu10k1 WaveTable" [Kernel]
> Port 0 : "Emu10k1 Port 0" (-We-)
> Connected From: 64:0
> Port 1 : "Emu10k1 Port 1" (-We-)
> Port 2 : "Emu10k1 Port 2" (-We-)
> Port 3 : "Emu10k1 Port 3" (-We-)
>
> --------------------------------------------------------
> 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
>
> any ideas on what's the problem or how to troubleshoot it?
>
> TIA
>
> erik
>
> _______________________________________________________________
>
> Sponsored by:
> ThinkGeek at http://www.ThinkGeek.com/
> _______________________________________________
> Alsa-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/alsa-user
_______________________________________________________________
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
