Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 12 Aug 2005 16:17:26 +0200	[thread overview]
Message-ID: <95c2ca541ff9033f2c54244716ff7991@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<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:                     new
Distribution:               
Kernel Version:             
======================================================================
Date Submitted:             08-08-2005 05:38 CEST
Last Modified:              08-12-2005 16:17 CEST
======================================================================
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.
======================================================================

----------------------------------------------------------------------
 tiwai - 08-12-05 15:53 
----------------------------------------------------------------------
The single irq is used for all pcm and midis.  So, don't run any audio
program during you measure (even better on console rather than on a
graphical desktop system to avoid beeps per PCM).

And, are you sure that the midi device produces a right MIDI byte stream? 
Can it test with a loopback?

----------------------------------------------------------------------
 roothorick - 08-12-05 16:17 
----------------------------------------------------------------------
The device works properly with input on a soundcard in another computer
(that one uses the snd-cmipci driver), so I'm positive it's functional. I
can even use aseqnet to run the input to this system. However, it's a
royal pain maintaining an entire second system just for MIDI input.

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                          
======================================================================




-------------------------------------------------------
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

             reply	other threads:[~2005-08-12 14:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-12 14:17 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-28 23:59 [ALSA - driver 0001319]: MIDI I/O (MPU-401) works for output only, not input bugtrack
2005-12-30 22:22 bugtrack
2005-08-12 14:38 bugtrack
2005-08-12 14:30 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=95c2ca541ff9033f2c54244716ff7991@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