1 |
On Fri, Jun 3, 2011 at 1:32 PM, <meino.cramer@×××.de> wrote: |
2 |
> cat /proc/asound/cards |
3 |
> 0 [CameraB404271 ]: USB-Audio - USB Camera-B4.04.27.1 |
4 |
> OmniVision Technologies, Inc. USB Camera-B4.04.27.1 at usb-0000:00:12.2-3, high |
5 |
> 1 [SB ]: HDA-Intel - HDA ATI SB |
6 |
> HDA ATI SB at 0xfcaf8000 irq 16 |
7 |
> 2 [NVidia ]: HDA-Intel - HDA NVidia |
8 |
> HDA NVidia at 0xfe97c000 irq 25 |
9 |
|
10 |
(I don't know about Jack or Pulseaudio, in case you use those, maybe |
11 |
it complicates things) but with ALSA you can specify the cards order |
12 |
in /etc/modprobe.d/alsa.conf to help this kind of situation become |
13 |
easier. I have the same (onboard + hdmi + webcam) and it seemed like |
14 |
the order was random every time I rebooted, and I had to reconfigure |
15 |
all my things that use sound. Fixing the order to be the same every |
16 |
time helped to solve that problem. |
17 |
|
18 |
For mplayer you can force the output to use the proper device in your |
19 |
mplayer.conf |
20 |
|
21 |
Use alsamixer to enable/disable the inputs depending on when you are |
22 |
using them. Maybe your microphone is recording and played back when |
23 |
you watch TV, causing the bad sounds... it's only a guess. :) |
24 |
|
25 |
For testing it might be easier to use aplay and arecord (from |
26 |
media-sound/alsa-utils) since they give you a more explicit choice of |
27 |
ALSA devices. For example "aplay -l" will list your playback devices, |
28 |
"arecord -l" will list the input devices. Then you can experiment with |
29 |
them and alsamixer until you find which one works. |
30 |
|
31 |
The alsa-info script will give you all the info about your sound |
32 |
hardware. Probably more info than you care about knowing. :) |
33 |
|
34 |
Good luck, |
35 |
Paul |