Difference between revisions of "Talk:PulseAudio"

Revision as of 22:33, 20 March 2021

Listen to microphone over the speakers using pulseaudio

By default, We cannot hear any sound of microphone over speaker on Debian or Ubuntu OS. So, we cannot sing karaoke. After “google” its, I’ve found a solution at “http://ubuntuforums.org/showthread.php?p=8672035”.

Using this command to route the mic input through output:

pactl load-module module-loopback latency_msec=1

To turn it off:

first find the module number

it gives it to you when you run the first command, or use this to find it:

pacmd list-modules

then to unload it use this with your module number:

pactl unload-module 27

Additional:

To fix the problem permanently, you need to load the modules when Pulseaudio starts. To do this, you need to add a line to the /etc/pulse/default.pa file with the following commands:

sudo gedit /etc/pulse/default.pa

Scroll down to the bottom of the file and add this line:

load-module module-loopback

Now the modules will load automatically and your line-in audio will always be available.

jackd and qjackctl

The program jackd is an audio sound server daemon for Linux, and its counterpart qjackctl is a simple user interface that let you handle JACK audio server. From this you can virtually connect the output of your mic to your speakers.

You can install them from you terminal with:

sudo apt-get install jackd qjackctl

errors : snd_pcm_open: Device or resource busy

snd_pcm_open: Device or resource busy -

~/.local/share/Steam/steamapps/common/PULSARLostColony/PULSAR_LostColony_Data/soundbackends/libalsa_linux_amd64.so error: ALSA

dooku:~$ lsof /dev/snd/pcm*
COMMAND    PID  USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 3553 xxxxx  mem    CHR  116,9           631 /dev/snd/pcmC0D0p
pulseaudi 3553 xxxxx   52u   CHR  116,9      0t0  631 /dev/snd/pcmC0D0p
PULSAR_Lo 4854 xxxxx  mem    CHR 116,10           632 /dev/snd/pcmC0D0c
PULSAR_Lo 4854 xxxxx   68u   CHR 116,10      0t0  632 /dev/snd/pcmC0D0c

dooku:~$ lsof /dev/snd/pcm*
COMMAND    PID  USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
pulseaudi 3553 xxxxx  mem    CHR  116,9           631 /dev/snd/pcmC0D0p
pulseaudi 3553 xxxxx   52u   CHR  116,9      0t0  631 /dev/snd/pcmC0D0p
PULSAR_Lo 4854 xxxxx  mem    CHR 116,10           632 /dev/snd/pcmC0D0c
PULSAR_Lo 4854 xxxxx   68u   CHR 116,10      0t0  632 /dev/snd/pcmC0D0c

dooku:~$ lsof /dev/snd/pcm*

libalsa_linux_amd64.so

linux dmix

dmix

dooku:~$ aplay -L|grep dmix
dmix:CARD=PCH,DEV=0
dmix:CARD=PCH,DEV=3
dmix:CARD=PCH,DEV=7
dmix:CARD=PCH,DEV=8
dmix:CARD=PCH,DEV=9
dmix:CARD=PCH,DEV=10
dmix:CARD=HDMI,DEV=3
dmix:CARD=HDMI,DEV=7
dmix:CARD=HDMI,DEV=8
dmix:CARD=HDMI,DEV=9
dmix:CARD=HDMI,DEV=10

alsa testing

The simplest way to find out something about your sound card(s) and how ALSA sees them is calling aplay -l for playback and arecord -l for recording. These commands list the cards, hardware devices and subdevices available for playback and recording, respectively. It also lists the card ID, which can be used instead of its index to specify the card.