Re: SOLVED? Re: [Alsa-user] sb live: midi in doesn't work

[Erik S. <st...@bi...>]

Takashi Iwai wrote:
> 
> At Thu, 13 Jun 2002 02:04:29 -0700,
> Erik Steffl wrote:
> >
> >   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:
> 
> oh, my, that's possible.  apparently only one midi device is defined
> in the driver on sb live, while audigy has two different ioports for
> the rear and front midi connectors.

  it's even worse: the game port midi in (on the back, the one that
works) works only with the keyboard that the cable came with (one end
midi, other end joystick connector). The other midi controller (drum
machine) doesn't work with this cable (both under linux and under
windows, it works fine with normal midi cable that goes into front panel
midi in (under windows)).

  is there anything special about the game port midi in? I thought it's
the same midi in as regular midi. is there any chance having the drum
machine work with this midi in port?

  or is there any chance front panel midi in being supported? is it a
matter of porting it from audugy driver or is it comepletely different?

> >   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)
> 
> how did you use the midi?
> if it's through sequencer and the port is connected, then try to
> disconnect once, and reconnect again.  this will invoke mpu401 uart
> reset.

  I did aconnect -x and reconnected again, that worked. annoying but
tolerable...

...
> unfortunately we have no idea.
> i'll take a look at oss emu10k1 driver whether it has something
> special about it (although i don't expect it).

  I guess this partially answers my question, any more info on this? Is
the problem missing docs?

  thanks,

	erik