From: Florian Bomers <Florian.Bomers@sun.com>
To: ian <deviant@custard.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: sblive midi out
Date: Mon, 04 Nov 2002 15:19:23 -0800 [thread overview]
Message-ID: <3DC7007B.C0490C59@sun.com> (raw)
In-Reply-To: Pine.LNX.4.44.0211042051560.9000-100000@rhubarb.custard.org
I have several SB Live's and even a Dell OEM one, and all of them have
functional external MIDI i/o. I haven't tried with latest ALSA drivers though.
You might want to search alsa-devel and alsa-user mailing lists, there were some
recent sb live issues.
Florian
ian wrote:
>
> Thanks for the answer on my dlmisc.c problem - updating sorted that out.
> I have an sblive oem that came with my dell, that has no digital output
> board. Alsa-lib reports that it is possible to writeto the midi port, but
> trying to do so reports that there is no such device. I believe the
> joystick connector on the back of the card can only be used for midi
> input, but i might be wrong there. At any rate it would seem that the
> sblive driver is doing something wrong?
> Ian
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
--
Florian Bomers
Java Sound
Java Software/Sun Microsystems, Inc.
http://java.sun.com/products/java-media/sound/
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
next prev parent reply other threads:[~2002-11-04 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 20:56 sblive midi out ian
2002-11-04 23:19 ` Florian Bomers [this message]
2002-11-05 18:19 ` ian
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=3DC7007B.C0490C59@sun.com \
--to=florian.bomers@sun.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=deviant@custard.org \
/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