From: Juan Linietsky <coding@reduz.com.ar>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Alsa MIDI device description extension proposal.
Date: Sat, 23 Mar 2002 23:14:02 -0300 [thread overview]
Message-ID: <20020323231402.6834fe98.coding@reduz.com.ar> (raw)
In-Reply-To: <20020323223959.2c3dd215.coding@reduz.com.ar>
Oh, and you know what, I was so concentrated in my hate for sysex ;) that i just noticed that i forgot to write the most obvious point about why sysex is a no-go.
And this is basically, that what you propose would work like this:
sysex call to poll for bank description -> Midi Out
and later
Midi In <- patch listing
And this has a fatal flaw, which is basically, what i said in my first, mail... Midi is a 1-way protocol. Thus considering this, remember that
not all deviecs have In/Out , in fact many of them are either midi IN only, and midi OUT only. Think about the sblive/awe synth, alsa sequencer clients, etc, are MIDI OUT ONLY, so it's not possible in any way to retrieve information from them via sysex.
regards
Juan Linietsky
_______________________________________________
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-24 2:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-23 1:16 Alsa MIDI device description extension proposal Juan Linietsky
2002-03-24 0:35 ` stef
2002-03-24 1:14 ` Juan Linietsky
2002-03-24 1:39 ` Juan Linietsky
2002-03-24 2:14 ` Juan Linietsky [this message]
2002-03-24 12:22 ` stef
2002-03-24 16:44 ` Juan Linietsky
2002-03-24 12:08 ` stef
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=20020323231402.6834fe98.coding@reduz.com.ar \
--to=coding@reduz.com.ar \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.