From: Ross Kendall Axe <ross.axe@blueyonder.co.uk>
To: alsa-devel@alsa-project.org
Subject: Re: [ALSA - driver 0000628]: Can't record audio
Date: Thu, 20 Jan 2005 21:00:18 +0000 [thread overview]
Message-ID: <41F01BE2.5020808@blueyonder.co.uk> (raw)
In-Reply-To: <4ca0e9985d5a7a7378d1370dcaa3754e@bugtrack.alsa-project.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
bugtrack@alsa-project.org wrote:
| The following issue has been RESOLVED.
| ======================================================================
| <https://bugtrack.alsa-project.org/alsa-bug/view.php?id=628>
| ======================================================================
| Reported By: pawlik
| Assigned To: tiwai
| ======================================================================
| Project: ALSA - driver
| Issue ID: 628
| Category: PCI - via82xx
| Reproducibility: always
| Severity: major
| Priority: normal
| Status: resolved
| Distribution: Debian
| Kernel Version: 2.6.8.1
| Resolution: not an issue
| Fixed in Version:
| ======================================================================
| Date Submitted: 11-03-2004 18:46 CET
| Last Modified: 01-17-2005 15:07 CET
| ======================================================================
| Summary: Can't record audio
| Description:
| I'm not able to record any audio. Reading from /dev/dsp results in an
| "Input/Output Error".
| The hardware I'm using is Soltek 75DRV5 with built-in soundcard.
| ======================================================================
|
| ----------------------------------------------------------------------
| rossaxe - 01-16-05 17:09
| ----------------------------------------------------------------------
| What is this particular knob supposed to do? So far as I can tell, it just
| offers a choice betweens 'works' and 'breaks'
|
| ----------------------------------------------------------------------
| tiwai - 01-17-05 15:07
| ----------------------------------------------------------------------
| This defines the connection of which input pin is selected for the certain
| input path. So, whether it works or not strongly depends on the hardware.
Wouldn't it make sense to disable it on hardware for which it does not work?
Ross
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB8Bvg9bR4xmappRARAtWbAJ4yMhnjJsmPYx2wJhFzdIMjGEAIpQCgj6u1
VU6489GB6yag+RcNT/h/Rzk=
=oc4t
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-20 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 14:07 [ALSA - driver 0000628]: Can't record audio bugtrack
2005-01-20 21:00 ` Ross Kendall Axe [this message]
2005-01-21 10:20 ` Takashi Iwai
2005-01-21 15:05 ` Ross Kendall Axe
2005-01-21 15:15 ` Ross Kendall Axe
2005-01-21 19:34 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2005-02-17 17:34 bugtrack
2005-01-16 16:09 bugtrack
2005-01-16 9:05 bugtrack
2004-11-09 14:28 bugtrack
2004-11-03 17:46 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=41F01BE2.5020808@blueyonder.co.uk \
--to=ross.axe@blueyonder.co.uk \
--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