From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001767]: midi port (64:32 'Audigy MPU-401 #2') will not read/record
Date: Sun, 22 Jan 2006 04:44:03 +0100 [thread overview]
Message-ID: <e252e44a1fbf978243ef443cc180ee29@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1767>
======================================================================
Reported By: bscipioni
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1767
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Redhat
Kernel Version: 2.6.12-smp
======================================================================
Date Submitted: 01-22-2006 03:23 CET
Last Modified: 01-22-2006 04:44 CET
======================================================================
Summary: midi port (64:32 'Audigy MPU-401 #2') will not
read/record
Description:
I have Audigy 2 Platinum. The Audgiy "drive" midi input is not working.
Previously I had been able to both play my midi keyboard and record from
it using Rosegarden, earlier versions of alsa and RedHat 9. Now I can
only play
the keyboard (midi out 64:32) - record doesn't work. Taking Rosegarden
out of the equation, I used both JACK and aconnect to connect 64:32
directly to 65:0 and I get nothing playing the keyboard. Soundfonts are
loaded and working
works just fine. So it seems just the 64:32 read port is not working
======================================================================
----------------------------------------------------------------------
rlrevell - 01-22-06 04:44
----------------------------------------------------------------------
Please use ALSA CVS to do a binary search by date and identify the change
that broke it.
Issue History
Date Modified Username Field Change
======================================================================
01-22-06 03:23 bscipioni New Issue
01-22-06 03:23 bscipioni Distribution => Redhat
01-22-06 03:23 bscipioni Kernel Version => 2.6.12-smp
01-22-06 04:44 rlrevell Note Added: 0007743
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next reply other threads:[~2006-01-22 3:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 3:44 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-18 12:40 [ALSA - driver 0001767]: midi port (64:32 'Audigy MPU-401 #2') will not read/record bugtrack
2006-01-22 2:23 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=e252e44a1fbf978243ef443cc180ee29@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