Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Dave Mielke <dave@mielke.cc>
To: linux-sound@vger.kernel.org
Subject: Re: Getting good sound input
Date: Sat, 29 Apr 2000 22:27:01 +0000	[thread overview]
Message-ID: <marc-linux-sound-95704760925645@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95703433918558@msgid-missing>

[quoted lines by Joe T. on April 29, 2000, at 11:32]

Hi:

>When i record from the input port, i get nothing.

Use "aumix -q" to see which of your input channels are set to "P" (play only)
and and which are set to "R" (play and record). If an input channel is set to
"P", then you'll hear it out of the speakers, but you won't be able to record
from it. If it's set to "R", then you'll be able to do both.

My guess is that your "line in" is set to "P". You can change it with a command
like "aumix -l R" (case is significant).

>When i record from the mic port, it sounds horrid.

The default in Linux is to use 8-bit sound, which intorduces a lot of low-level
distortion because the granularity is just too low. Using basic commands like
"cat" or "cp" will most definitely use the default, so they're not the best way
to go. Use a command which lets you specify the sample size, and use at least
16 bits.

-- 
Dave Mielke           | 856 Grenon Avenue | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: dave@mielke.cc | Canada  K2B 6G3   | if you're concerned about Hell.

  reply	other threads:[~2000-04-29 22:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-29 18:32 Getting good sound input Joe T.
2000-04-29 22:27 ` Dave Mielke [this message]
2000-04-29 22:35 ` Joe T.
2000-04-30  8:21 ` Britton

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=marc-linux-sound-95704760925645@msgid-missing \
    --to=dave@mielke.cc \
    --cc=linux-sound@vger.kernel.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