Linux Sound subsystem development
 help / color / mirror / Atom feed
From: llornkcor <llornkcor@llornkcor.com>
To: linux-sound@vger.kernel.org
Subject: Re: pci128 line-in help
Date: Wed, 27 Oct 1999 00:50:23 +0000	[thread overview]
Message-ID: <marc-linux-sound-94098612031968@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-94098365529736@msgid-missing>

I have a pci 128, and the mic input is the default, so you'll have to make sure
to select the line input using a mixer. If you've already done that, try
looking at /dev/dsp, or /dev/dsp1. If you are trying to listen to something and
record at the same time (full-duplex) the OSS driver that comes with the kernel
doesn't support it. So, if the line out is open, it won't record anything.
Sometimes, some sound apps don't close /dev/dsp correctly.Try ALSA or the
commercial OSS driver from 4front. 

On Tue, 26 Oct 1999, est@hyperreal.org wrote:
> I can't seem to get my pci128 line-in to work.  This is using the
> (es1370) OSS driver distributed with the 2.2.7 kernel.  I've tried all
> the obvious mixer settings as well as all the private ioctl()s the
> driver has, checked my hardware, etc.  Can anyone think of anything I
> might be missing?
> 
> Thanks,
> 
> Eric
-- 
"When the doors of perception are cleansed everything appears as it truly is - infinite."   - William Blake 

llornkcor rocknroll 
SpiritShip MultiMedia Recording Studio
http://www.llornkcor.com

  reply	other threads:[~1999-10-27  0:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-27  0:19 pci128 line-in help est
1999-10-27  0:50 ` llornkcor [this message]
1999-10-27  2:03 ` David Olofson
1999-10-28 16:14 ` Tony Nugent

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-94098612031968@msgid-missing \
    --to=llornkcor@llornkcor.com \
    --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