From: Peter Enderborg <pme@ufh.se>
To: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: Rawmidi bug or missed feature?
Date: Sat, 02 Mar 2002 18:45:36 +0100 [thread overview]
Message-ID: <3C810FC0.27150313@ufh.se> (raw)
In-Reply-To: 200203021711.MAA06182@renoir.op.net
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. This is very, very important.
>
> >I have a midisport 8x8. It have a serial port. I have a computer
> >linux. Alsa don't have driver for the unit. So I have writen a daemon
> >that open the snd-card-virmidi with snd_rawmidi_open().
>
> This makes no sense at all to me. snd_rawmidi_open() is a way to
> get access to an ALSA low level, raw MIDI driver. For example, my
> trident card has a MIDI port on it, and the trident driver contains
> code to deliver and receive data from the port. If I want to
> read/write that data stream, I would use snd_rawmidi_open().
>
Yes, and my device is a midisport.
>
> But snd_rawmidi_open() has nothing to do with the sequencer, or with
> virmidi. virmidi exists to make sequencer ports available via the raw
> MIDI API so that programs which don't know about the sequencer can
> still read and write data to it.
>
I do. I is a connection. I gets a client ID. So it have very mush to do
with the
sequencser.
>
> If there is no ALSA driver for the unit (or for serial MIDI - I am not
> sure if we have such a thing, do we?), then why would you be calling
> snd_rawmidi_open()?
>
There is a serial driver. But it dont handle the same protocol as
midisport.
So how should I connect my device so I can use the midisport to talk to
my synths?
Rawmid on a snd-card-virmidi gives one way. Show me a better way instead
of say that
im wrong.
>
> > I have also
> >writen a processor that handels event on a sequencer level to
> >interface my Roland MCR-8 with varius applications, synths.
>
> Why are you using the sequencer for this?
It is the api for midi programming. I don't have to think about active
sensing, streaming or
anything on the low level. And I get tools for routing the data as I
like. I thougth that you should
know the concept. Almost everything is in realtime. But some mappings i
done in the time domain
as well. For example the dialer.
>
>
> --p
--
foo!
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next prev parent reply other threads:[~2002-03-02 17:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 22:56 Rawmidi bug or missed feature? Peter Enderborg
2002-03-01 13:45 ` Paul Davis
2002-03-01 14:58 ` Ricardo Colon
2002-03-01 19:22 ` Peter Enderborg
2002-03-01 20:30 ` Paul Davis
2002-03-01 21:06 ` Peter Enderborg
2002-03-01 21:31 ` Paul Davis
2002-03-01 22:18 ` Peter Enderborg
2002-03-02 11:14 ` Jaroslav Kysela
2002-03-02 13:31 ` Peter Enderborg
2002-03-02 17:11 ` Paul Davis
2002-03-02 17:45 ` Peter Enderborg [this message]
2002-03-02 18:01 ` Paul Davis
2002-03-02 18:37 ` Peter Enderborg
2002-03-02 18:58 ` Paul Davis
2002-03-02 19:15 ` Peter Enderborg
2002-03-02 19:31 ` Paul Davis
2002-03-02 22:22 ` ALSA sequencer in user land (was: Rawmidi bug or missed feature?) Frank van de Pol
2002-03-02 17:55 ` Paul Davis
2002-03-03 0:34 ` Frank van de Pol
2002-03-02 20:18 ` Paul Davis
2002-03-03 4:13 ` CAPs Bob Ham
2002-03-02 17:55 ` Rawmidi bug or missed feature? Roger E Critchlow Jr
2002-03-02 18:36 ` Peter Enderborg
2002-03-02 20:43 ` Roger E Critchlow Jr
2002-03-02 22:20 ` Peter Enderborg
2002-03-01 21:32 ` Paul Davis
2002-03-02 10:28 ` Jaroslav Kysela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C810FC0.27150313@ufh.se \
--to=pme@ufh.se \
--cc=alsa-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox