1. Load the loopback module
pacmd load-module module-loopback latency_msec=5
creates a playback and a recording device.
2. Configure the devices in pavucontrol
In pavucontrol, in the Recording tab, set the "Loopback" device's from input device to the device which receives the line in signal.
In the Playback tab, set the "Loopback" device's on output ...
A) Is there a way to determine the systemd unit that caused the creation of a specific process (in my example output, process 2738, the PA daemon)?
Sure. You can run systemctl status <pid> and systemd will find you the unit that contains that PID. For example, on my system I find a dnsmasq process:
# ps -fe | grep dnsmasq
nobody 18834 1193 0 ...
Jack requires you-- the knowledgeable user-- to configure the server to determine lowest possible processing latency for your machine. (Processing latency is the time it takes the server to move data to/from the client applications and then send/receive the next "chunk" of audio samples outside the system.) Jack will either deliver those chunks of audio ...
Add the following to /etc/pulse/default.pa:
set-card-profile <cardindex> <profilename>
How do we figure out what to use as cardindex and as profilename? Here's one way. Configure the card so everything is working. The cardindex will usually be 0, but you can find it by running pacmd list-cards and looking at the line index: .... To find the ...
The problem lies in a PulseAudio module called module-role-cork which exists to pause music and video during phone calls. All applications are given a media-role property which can be either music video or phone. The Cork module will give any application tagged phone exclusive access to the PulseAudio server and pause anything not tagged as such.
It's all about multiplexing.
I don't need to multiplex sounds from or to several sound cards
Ah, but you do! If you want to be able to play audio from two sources at once, ever, for any reason, you need multiplexing.
OSX and Windows handle Multiplexing in the Kernel (but still in software), which is why this never/rarely comes up on those platforms.
I have these headphones as well, along with a handy laptop running Fedora 24. After chatting with one of the Bluez developers on IRC, I have things working. Below is what I've found. (Note that I know very little about Bluetooth so I may be using incorrect terminology for some of this.)
The headphones support (or at least say they support) bluetooth LE ...
You can add a sink with
pacmd load-module module-null-sink sink_name=MySink
pacmd update-sink-proplist MySink device.description=MySink
You can add a loopback device with the command
pacmd load-module module-loopback sink=MySink
pactl list sinks | grep '^[[:space:]]Volume:' | \
head -n $(( $SINK + 1 )) | tail -n 1 | sed -e 's,.* \([0-9][0-9]*\)%.*,\1,'
That's what I have. It's not neat, but it was enough for my use. I couldn't find the way to do it. The pactl just doesn't seem to have any means of getting listing for one sink only, but they are printed in ascending order. So ...
I had the same problem (for at least a year now), and the following seemed to work:
Taken from: https://bbs.archlinux.org/viewtopic.php?id=164868
Use pavucontrol to change the port to your desired one. Then find the internal name of the port with this command:
$ pacmd list | grep "active port"
active port: <hdmi-output-0>
active port: <...
It seems any process linking to the libpulse* family of shared objects--either before or after running X and the i3 window manager--may implicitly autospawn PulseAudio server, under your user process, as a byproduct of attempts to interface with the audio subsystem. PulseAudio creator Lennart Poettering seems to confirm this, in a 2015-05-29 email to the ...
Linux doesn't have a "historical problem in configuring audio devices". The problem actually are the manufacturers of devices, mostly laptops, who just ship the laptop with pre-installed Windows drivers that can be configured acurately to deal with the laptop hardware, because the manufacturer of course knows exactly how the hardware is set up. On the other ...
VMG's answer is subtly wrong; it will technically work, but it will disable all other plugins than a2dp, meaning bluetooth keyboards/mice/gamepads/etc will stop working, when the only plugin causing issues seems to be one called avrcp.
and change ExecStart=/usr/lib/bluetooth/bluetoothd
You can get the number of sink Input with pactl command.
$ pactl list sink-inputs
Sink Input #7119
Owner Module: 12
application.icon_name = "google-chrome"
media.name = "Playback"
application.name = "Chromium"
Using this number(#7119), you specify the sink ...
pactl unload-module gives a hint:
You have to specify a module index or name
as does the manpage:
Unload the module instance identified by the specified numeric
index or unload all modules by the specified name.
The ID is shown in this line (pactl list):
Owner Module: 24
In PulseAudio, each sound card has a profile set associated with it. A profile set contains multiple profiles, and those are the profiles that you see when listing the cards (or when looking in the various PulseAudio GUIs).
There is a default profile, which primarily contains things useful for analog sound output. There is also an extra-hdmi profile that ...
In your example, pulseaudio is using 32MB not 3GB. The RES column is physical memory. The VIRT column shows all the virtual memory used by the process. According to man top, that includes all code, data, and shared libraries plus pages that have been swapped out and pages that have been mapped but not used.
I finally found the solution: https://steamcommunity.com/app/93200/discussions/0/864959809826195633/
It seems that some apps use something called OpenALsoft to control audio, and it has a configuration option that inhibits sink changes. To disable the option, you can create a config file.
Have you tried disabling suspend-on-idle in /etc/pulse/default.pa? I change this:
### Automatically suspend sinks/sources that become idle for too long
### Automatically suspend sinks/sources that become idle for too long
and then killall pulseaudio to restart it.
First of all we need to configure/change the audio configuration for our bluetooth device (in my case, Bose Soundlink), I wouldn't assume that this steps would work for every bluetooth device, so give it a try, and hopefully it'll work.
We type in this command.
sudo nano /etc/bluetooth/audio.conf
This will open or if not exist previously then create the ...
After some experimentation I found that modifying /etc/pulse/system.pa to permit anonymous:
load-module module-native-protocol-unix auth-anonymous=1
The audio now plays fine. Hope this helps others needing system mode pulse
Turning all hardware mixers up worked.
Edit: Actually just found another, slightly hacky, work around to this issue after it came back a few boots later by using an ladpsa amplifier and compressor in Arch. Something similar to this could probably work in other distros too.
Install ladspa plugins:
pacman -S ladspa-plugins
Create an .asoundrc file in the ...
I ended up here because of the very same problem, after upgrading from Stretch, the audio disappeared. Similar symptoms and outputs (Nvidia card and Intel HDA sound). While following instructions, though, I've found that I couldn't get this step to work:
root@desk:~# aplay -D plughw:0,0 /usr/share/sounds/alsa/Front_Center.wav
aplay: main:828: audio open ...
How is PulseAudio getting started?
While this is still a valid question, the answer for it has changed over time. The previous answers are either insufficient or incorrect as now PulseAudio is being launched automatically by the user's systemd, which in turn was launched by the system's systemd when the user logged in.
$ systemctl --user status pulseaudio
You can use Xvfb, which is X server with a virtual framebuffer, i.e. an X server that displays only in memory and doesn't connect to any hardware. You don't need to run any client you don't want on that server, and in particular no desktop environment or window manager.
Xvfb :1 -screen 0 1x1x8 &
DISPLAY=:1 pulseaudio ...
Note that Tommi Kyntola's answer relies on the sink to be in use so that you can actually get the sink number.
Also note that it relies on named sink indexes to be the same as the counted index. Let's say, for example, we have 3 sinks 1, 2 and 3 and that 3 is our selected sink, we then disconnect number 2, leaving us with 1 and 3. Now you can't count to sink ...