On 15/09/14 12:32, Adrian Mageanu wrote: > What exactly should I look for in /dev/snd* ?
You'd see files corresponding to each device present E.g. when I plug in a usb webcam (laptop has inbuilt also) The following files appear: pcmC1D0c - the capture device C1 = card#1, D0 -> Device#0, 'c'->Capture controlC1 - The control device ============================================== To test whether any audio comes from your hardware. List the devices $ arecord -l > **** List of CAPTURE Hardware Devices **** > card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > card 1: Camera [USB 2.0 Camera], device 0: USB Audio [USB Audio] > Subdevices: 1/1 > Subdevice #0: subdevice #0 Record from the appropriate device, in my case #1 $ arecord -vv -fcd -Dplughw:1 This should display some configuration information, then a basic real time level graph on the terminal. =============================================== If the above tests show that there is a device present, and it is generating some non-zero audio data, then move on up the stack. I.e. suspect pulseaudio or guvcview itself. You could try 1. Restart pulseaudio $ pulseaudio --kill pulseaudio will probably restart automatically (check with ps -C pulseaudio) Then you can look at sources and their states $ pactl list short sources > $ pactl list short sources > 0 alsa_output.pci-0000_00_1b.0.analog-stereo.monitor > module-alsa-card.c s16le 2ch 44100Hz SUSPENDED > 1 alsa_input.pci-0000_00_1b.0.analog-stereo module-alsa-card.c > s16le 2ch 44100Hz SUSPENDED > 2 > alsa_input.usb-Sonix_Technology_Co.__Ltd._USB_2.0_Camera-02-Camera.analog-mono > module-alsa-card.c s16le 1ch 16000Hz SUSPENDED The SUSPENDED state changes to RUNNING when the device is in use. _______________________________________________ Linux-users mailing list [email protected] http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
