30 Sep
2013
30 Sep
'13
8:32 p.m.
On 28 September 2013 22:01, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
If the problem is the same as with the original LP,
then
the ALSA driver can't do anything about it, unless it would
contain LP-specific code.
But isn't the problem a general running-status problem if multiple programs
are receiving from the same device? Is it a problem with the way the ALSA
sequencer works (this seems to ring a bell somehow) as you said in the
older thread that using Jack-MIDI would solve it?
30 Sep
30 Sep
9:05 p.m.
New subject: MIDI Running Status and ALSA, was: [LAU] Launchpad S and Linux
On Mon, Sep 30, 2013 at 07:32:36PM +0100, Kaspar Bumke wrote:
On 28 September 2013 22:01, Fons Adriaensen
<fons(a)linuxaudio.org> wrote:
ALSA will not look at the data sent by the LP or any other MIDI
device unless that device is opened by some client. This *could*
be different - which would mean that ALSA would be monitoring all
devices all the time, even if nobody is interested - probably a
waste of CPU time.
Jack-MIDI would solve it because the device would remain open
even while no app is using it (the client is Jack, not any app),
and running status would be preserved.
The real source of the problem here is the LP firmware. Even if
you accept that using running status make sense (it doesn't in
this case), it should at least send a status byte after a reset.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
If the problem is the same as with the original
LP, then
the ALSA driver can't do anything about it, unless it would
contain LP-specific code.
But isn't the problem a general running-status problem if multiple programs
are receiving from the same device? Is it a problem with the way the ALSA
sequencer works (this seems to ring a bell somehow) as you said in the
older thread that using Jack-MIDI would solve it?
1:08 p.m.
On Tue, Oct 01, 2013 at 11:01:52AM +0200, Clemens Ladisch wrote:
Fons Adriaensen wrote:
But apparently it does. If not, what is this whole
thread about ?
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
If the problem is the same as with the original
LP, then
the ALSA driver can't do anything about it, unless it would
contain LP-specific code.
The Launchpad S is class compliant and thus cannot use
running status. 
2:24 p.m.
Fons Adriaensen wrote:
On Tue, Oct 01, 2013 at 11:01:52AM +0200, Clemens
Ladisch wrote:
The OP asked about the Launchpad S. Nobody knew anything about that, so
people reminisced about the quirks of the old Launchpad instead.
Regards,
Clemens
Fons Adriaensen wrote:
But apparently it does. If not, what is this whole
thread about ? If the problem is the same as with the original
LP, then
the ALSA driver can't do anything about it, unless it would
contain LP-specific code.
The Launchpad S is class compliant and thus cannot use
running status.
3859
days inactive
3860
days old
linux-audio-dev@lists.linuxaudio.org
4 comments
3 participants
participants (3)
-
Clemens Ladisch -
Fons Adriaensen -
Kaspar Bumke