-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
scar @ 06/25/2009 11:30 AM:
Clemens Ladisch @ 06/25/2009 02:21 AM:
scar wrote:
Clemens Ladisch @ 06/24/2009 12:53 AM:
The microphone input is mono. There are no left/right levels; the
driver pretending that they exist is a driver bug. I'll
scar wrote:
i have been experimenting, and what appears to be happening is this:
while recording using the line, if the microphone levels are adjusted,
the driver/card automatically jumps to recording from the mic.
Neither the driver nor the card do this; I'd guess this is a feature of
your
Hi,
I'm facing problems with my soundcard. I believe the hardware is being
recognized but not properly configured.
# lspci -v | grep -i audio
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 02)
I downloaded and installed the latest alsa-driver [1] sources
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Clemens Ladisch @ 06/26/2009 03:30 AM:
scar wrote:
i have been experimenting, and what appears to be happening is this:
while recording using the line, if the microphone levels are adjusted,
the driver/card automatically jumps to recording from
-- Forwarded message --
From: Ludwig Maes ludwig.m...@gmail.com
Date: 2009/6/26
Subject: Laptop speakers nonfunctional, jacks functional
To: alsa-user@lists.sourceforge.net
Realtek ALC888S (according to preinstalled Realtek HD audio manager on
windows) visible jacks working,
One idea: Is your jack a combined RCA/stereo jack? If so, windows might have
some code to switch between the two. But ALSA doesn't properly recognise, when
no jack is in.
Regards
Julien
Music was my first love and it will be my last (John Miles)
FIND MY
On Fri, 26 Jun 2009 10:48:29 -0700
scar s...@drigon.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Clemens Ladisch @ 06/26/2009 03:30 AM:
scar wrote:
i have been experimenting, and what appears to be happening is this:
while recording using the line, if the microphone
I want to cause a random alsa application to throw away all sound
output. I'm suspecting that something about how the program is
communicating with pulseaudio is causing it to act weird and I want to
test this.
To this end I put this in my ~/.asoundrc file:
pcm.!default {
type null
}
