From: bugtrack@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: Mon, 29 Aug 2005 06:23:17 +0200 [thread overview]
Message-ID: <1678ec8f8dcaf754a24bc1bd15adacb8@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=349>
======================================================================
Reported By: amarsh04
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 349
Category: ISA - sb16/sbawe
Reproducibility: always
Severity: major
Priority: normal
Status: acknowledged
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: 08-29-2005 06:23 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
======================================================================
----------------------------------------------------------------------
tiwai - 04-12-05 16:38
----------------------------------------------------------------------
What do you mean exactly "can't play MIDI"? Did you get any error
messages?
----------------------------------------------------------------------
amarsh04 - 08-29-05 06:23
----------------------------------------------------------------------
Still trying to identify the problem. alsamixer reports a CTL1745 chip.
aplaymidi -l
reports:
Port Client name Port name
62:0 Midi Through Midi Through Port-0
64:0 Sound Blaster 16 MIDI Sound Blaster 16 MIDI
65:0 OPL3 FM synth OPL3 FM Port
aplaymidi --port=64:0 somefile.mid
apparently runs but gives silence
after trying some other midi programs, I get playmidi to partially work:
playmidi -r somefile.mid
reports correct instruments, but doesn't give a good sound.
playmidi -r -p 64:0 somefile.mid
reports all instruments as "Syn.Brass 2" and all channels sound like
"Syn.Brass 2"
playmidi -r -p 65:0 somefile.mid
reports all instruments as "Soprano Sax" and all channels sound like
"Soprano Sax"
It's as if the sysex messages are being mis-interpreted although the note
events are getting through ok.
Could amidi be used to send and receive some debugging information
Running current Debian Unstable ALSA 1.0.9a
uname -a reports:
Linux symone 2.6.12-1-386 #1 Tue Aug 16 21:23:21 UTC 2005 i586 GNU/Linux
Issue History
Date Modified Username Field Change
======================================================================
06-29-04 07:58 amarsh04 New Issue
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)
04-07-05 20:57 jdthood Note Added: 0004365
04-10-05 07:54 amarsh04 Note Added: 0004434
04-10-05 09:53 jdthood Status new => acknowledged
04-12-05 16:38 tiwai Note Added: 0004450
08-29-05 06:23 amarsh04 Note Added: 0005964
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next reply other threads:[~2005-08-29 4:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 4:23 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-03 1:42 [ALSA - driver 0000349]: can't play MIDI through ALSA / MPU-401 but non-ALSA "midiplayer" to MIDI device works bugtrack
2005-09-02 17:53 bugtrack
2005-04-12 14:38 bugtrack
2005-04-10 7:53 bugtrack
2005-04-10 5:54 bugtrack
2005-04-07 18:57 bugtrack
2004-06-29 5:58 noreply
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=1678ec8f8dcaf754a24bc1bd15adacb8@bugtrack.alsa-project.org \
--to=bugtrack@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.