Jaroslav Kysela wrote:
On Fri, 1 Mar 2002, Peter Enderborg wrote:
Paul Davis wrote:
Yes! And the device that is using running status is alsa rawmidi device.
What makes you think that? AFAIK, the raw MIDI device code does no
parsing of MIDI data at all ...
Parsing? It sends
I have a snd_rawmidi_t. And I want to know what client Id it will have
in the other end.
For example my first rawmidi is card 2 device 0. And that is client id
80:0 but how do I look
that up in the rigth way?
___
Alsa-devel mailing list
[EMAIL
I have just done some work on the alsa-howto wiki for the cmipci card.
I intend to use this as the template for all the other cards. I appreciate any
constructive criticism.
http://alsa.opensrc.org/index.php?page=cmipci
--
Patrick Shirkey - Boost Hardware Ltd
For the discerning hardware
I don't know how to be more specific. I have a program that listen to
a raw midi stream generated by alsa. But I try.
You have a program that uses the sequencer to read MIDI data. That's
totally different from a program that uses the raw MIDI interface to
read MIDI data. This is very, very
Paul Davis wrote:
I don't know how to be more specific. I have a program that listen to
a raw midi stream generated by alsa. But I try.
You have a program that uses the sequencer to read MIDI data. That's
totally different from a program that uses the raw MIDI interface to
read MIDI data.
Peter Enderborg writes:
Jaroslav Kysela wrote:
On Fri, 1 Mar 2002, Peter Enderborg wrote:
Paul Davis wrote:
Yes! And the device that is using running status is alsa rawmidi device.
What makes you think that? AFAIK, the raw MIDI device code does no
parsing of
Roger E Critchlow Jr wrote:
Peter Enderborg writes:
Jaroslav Kysela wrote:
On Fri, 1 Mar 2002, Peter Enderborg wrote:
Paul Davis wrote:
Yes! And the device that is using running status is alsa rawmidi device.
What makes you think that? AFAIK, the raw
How do you solve the problem with sharing hardware then?
I don't. I intend to wait for (and contribute too, if I can) what I
consider the correct solution:
a) sequencer genuinely split into:
1) a router/multiplexer
2) a scheduler
b) sequencer moves into user space
As
How can we get the same performance i userspace? For me it is the
processor/OS schedule that gives the limit for that, and in kernel we
get
the hardware as the limit.
there are two things done by the sequencer:
a) routing/multiplexing
this is mostly a matter of code design
Roger E Critchlow Jr wrote:
Peter Enderborg writes:
Roger E Critchlow Jr wrote:
[ ... ]
Does this help?
Well. I guess it do. I will give it a try. It should work. What about non midi
snd_seq_event_t.
The internal alsa stuff, like subscribe?
Hmm, hadn't
Frank -
thanks for writing. I don't want to suggest for one moment that there
is any blame to be attached to the current sequencer design. None of
us knew what we know now, and as you point out the hardware state of
affairs has changed considerably.
Pentium 60 MHz (though faster iron was
On Sat, 2002-03-02 at 20:18, Paul Davis wrote:
ok, don't forget to put CAPs on the 2.5 wishlist :-)
they are already implemented and maintained. its just that (almost)
nobody turns them on.
How do you do this now? This http://www.tml.hut.fi/~tilmonen/givertcap/
page tells me to do change
I have been trying to get S16_LE format sound out of my ice1712 with
poor success, and noted the example in
http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html
for setting up slaves. I added a format line to ~/.asoundrc thus:
pcm.rate44100Hz {
type plug
slave {
13 matches
Mail list logo
