From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001319]: MIDI I/O (MPU-401) works for output only, not input
Date: Wed, 1 Mar 2006 00:59:31 +0100 [thread overview]
Message-ID: <7174df884f432ef3a5df4b43ccd2da97@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1319>
======================================================================
Reported By: roothorick
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1319
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: closed
Distribution:
Kernel Version:
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 08-08-2005 05:38 CEST
Last Modified: 03-01-2006 00:59 CET
======================================================================
Summary: MIDI I/O (MPU-401) works for output only, not input
Description:
I have a Sound Blaster PCI 512, and MIDI interfacing with external devices,
such as keyboards, only works for output (from the soundcard to other
devices). When I try to do input (from those devices to the soundcard) no
events get through at all.
======================================================================
----------------------------------------------------------------------
roothorick - 08-12-05 16:38
----------------------------------------------------------------------
Passing the option enable_ir=1 had no effect whatsoever.
----------------------------------------------------------------------
rlrevell - 12-30-05 23:22
----------------------------------------------------------------------
Any improvement in later ALSA releases?
Issue History
Date Modified Username Field Change
======================================================================
08-08-05 05:38 roothorick New Issue
08-11-05 14:31 tiwai Note Added: 0005759
08-11-05 17:41 roothorick Note Added: 0005761
08-12-05 15:53 tiwai Note Added: 0005776
08-12-05 16:17 roothorick Note Added: 0005779
08-12-05 16:30 Clemens LadischNote Added: 0005780
08-12-05 16:38 roothorick Note Added: 0005781
12-30-05 23:22 rlrevell Note Added: 0007286
03-01-06 00:59 rlrevell Status new => closed
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-02-28 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 23:59 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-30 22:22 [ALSA - driver 0001319]: MIDI I/O (MPU-401) works for output only, not input bugtrack
2005-08-12 14:38 bugtrack
2005-08-12 14:30 bugtrack
2005-08-12 14:17 bugtrack
2005-08-12 13:53 bugtrack
2005-08-11 15:41 bugtrack
2005-08-11 12:31 bugtrack
2005-08-08 3:38 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=7174df884f432ef3a5df4b43ccd2da97@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox