From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000349]: can't play MIDI through ALSA / MPU-401 but non-ALSA "midiplayer" to MIDI device works
Date: Tue, 29 Jun 2004 07:58:33 +0200 [thread overview]
Message-ID: <a235e67e29374dbadc5c375d36884d31@bugtrack.alsa-project.org> (raw)
The following bug has been SUBMITTED.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000349
======================================================================
Reported By: amarsh04
Assigned To:
======================================================================
Project: ALSA - driver
Bug ID: 349
Category: ISA - sb16/sbawe
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Debian
Kernel Version: 2.6.5-1 (problem also showed with 2.4.24)
======================================================================
Date Submitted: 06-29-2004 07:58 CEST
Last Modified: 06-29-2004 07:58 CEST
======================================================================
Summary: can't play MIDI through ALSA / MPU-401 but non-ALSA
"midiplayer" to MIDI device works
Description:
With ISA SB16 PNP, aplaymidi -l reports:
Port Client name Port name
64:0 Sound Blaster 16 MIDI - Rawmidi Sound Blaster 16 MIDI
65:0 OPL3 FM synth OPL3 FM Port
Neither
aplaymidi -p 64:0 myfile.mid
nor
aplaymidi -p 65:0 myfile.mid
work, but the non-ALSA "midiplayer" works playing directly to the MIDI
device:
playmidi -v -D0 myfile.mid
======================================================================
Bug History
Date Modified Username Field Change
======================================================================
06-29-04 07:58 amarsh04 New Bug
06-29-04 07:58 amarsh04 Distribution => Debian
06-29-04 07:58 amarsh04 Kernel Version => 2.6.5-1 (problem also
showed with 2.4.24)
======================================================================
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next reply other threads:[~2004-06-29 5:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 5:58 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-07 18:57 [ALSA - driver 0000349]: can't play MIDI through ALSA / MPU-401 but non-ALSA "midiplayer" to MIDI device works bugtrack
2005-04-10 5:54 bugtrack
2005-04-10 7:53 bugtrack
2005-04-12 14:38 bugtrack
2005-08-29 4:23 bugtrack
2005-09-02 17:53 bugtrack
2005-09-03 1:42 bugtrack
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=a235e67e29374dbadc5c375d36884d31@bugtrack.alsa-project.org \
--to=noreply@alsa-project.org \
--cc=alsa-devel@alsa-project.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 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.