4
adding an 'asymmetrical' ALSA device worked:
change the contents of /etc/asound.conf and ~/.asoundrc to the following:
pcm.!default {
type asym
playback.pcm "hw:0,0"
capture.pcm "hw:1,1"
}
and sudo alsa force-reload for good measure
4
Make sure HDMI is selected as default output in Sound & Video -> PulseAudio Volume Control settings. You have to click on the green checkmark with "set as fallback" tooltip in the screenshot below:
If that doesn't help, or you don't want to keep Pulse at all, remove pulseaudio, reboot, and your system should be back to plain ALSA. You can ...
3
Pulseaudio is incredibly tedious. I think this has something to do with dbus.
I've been sitting here for hours just to get it working somehow. Tried systemd units system-wide, systemd units in --user mode, … nothing worked.
The only way I got this to work was:
move away the provided autostart:
mv /etc/xdg/autostart/pulseaudio.desktop
/etc/xdg/...
3
I've got it working with a USB bluetooth dongle right now. Here's a general outline of what I did:
Remove bluez 5 and pulseaudio with apt-get remove.
Compile and install ALSA from source.
Compile and install bluez 4.101 from source.
Copy libasound_module_pcm_bluetooth.so to the folder: /usr/lib/arm-linux-gnueabihf/alsa-lib/ (used find -name to locate it)
...
3
This is a known bug on the rpi3. internal Wifi and internal Bluetooth simultaneous usage will provoke crackling sound and sound disapearance. No fixes yet.
https://github.com/raspberrypi/linux/issues/1402
Using a bluetooth dongle or Wi-Fi dongle resolve the problem.
3
Configure looks for the presence of the development libraries of PulseAudio, Jack and ALSA, in that order.
That is why in answers like this it is mentioned that "...It also appears that ALSA will not be used if PulseAudio is installed...".
In my particular case, I didn't have anything else installed besides ALSA. But then I remembered that I did some tests ...
3
This site isn't made for "which works best for my requirements" as this is highly subjective and likely to change, but a couple of alternatives are:
Volumio - mpd-based, web interface, supports queuing and has a browser interface
RuneAudio - also mpd-based, web interface, based on same code as Volumio but with different features (I use this one)
Both these ...
3
I found the solution for my problem and it's to remove --disallow-module-loading flag. It prevents loading of module-bluez5-device as this module is always loading on-demand and can't be pre-loaded on startup via defaults.pa/system.pa.
3
Make the RPi connected to the audio system essentially a bluetooth speaker. Stream the audio from the RPi that's playing back the video. Most video player apps have sound delay/advance configurable. - once the audio delay/advance is set for a particular video it should hold audio sync throughout playback pretty well.
From tutorial at Raspberrypi.org forum ...
2
You are supposed to mention your sound card number to store the settings using sudo alsactl store,
You could see the card number of your device using the command,
arecord -l
The output would be apparaently in this form,
List of CAPTURE Hardware Devices
card 1: U0x41e0x30d3 [USB Device 0x41e:0x30d3], device 0: USB Audio [USB Audio]
...
2
layla writes on http://robot.laylamah.com/?p=35
Note, if you receive an error such as the following:
Error opening audio device plughw:1,0 for capture: Connection refused
Mixer load failed: Invalid argument FATAL_ERROR: "continuous.c", line
246: Failed to open audio device
You likely have pulseaudio installed, which is causing sphinxbase to attempt to use ...
2
After much digging around and beating my head against the wall I finally got it working.
I had to change /etc/pulse/default.pa where it mentioned Bluetooth to
load-module module-bluetooth-policy
load-module module-bluetooth-discover
load-module module-switch-on-connect
Then I had to plug in a monitor and keyboard and make sure it connected on the desktop, ...
2
Yes, should be possible
(While I don't understand whether those "displays" are supposed to show some kind of graphics output), it is possible for the Pi to source multiple different audio outputs. One simple approach is to use multiple USB sound cards. alsa is perfectly capable to handle multiple cards (see here). Different software tools or multiple ...
2
Okay, I've done some tests.
Setup:
Pi 3 without a heatsink, 1A power supply (artificial starvation, on purpose)
Fresh install of Raspbian Jessie Lite (downloaded a few minutes ago
as of writing)
Samsung Galaxy S6 Duos
VLC player for Andorid
320kbps HD copy of Tremor by Martin Garrix
320kbps HD full copy of Tomorrowland 2014 @ Belgium (57min:11sec)
Modified ...
2
Use amixer -c2 controls to list all the low-level controls.
Then you can use amixer -c2 cset .. to select specific controls by their unique ID number.
2
I feel your pain, I have the same setup and trying to troubleshoot at the moment looking for a solution.
edit: I've tried a bunch of things.
I just did
pi@raspberrypi:~ $ sudo killall bluealsa
pi@raspberrypi:~ $ sudo bluealsa --disable-hfp
then i was able to play a wav that i downloaded
aplay piano.wav
audio started playing, and i was even able to ...
2
I was able to use PulseAudio to route my audio to the RPi.
The superuser question linked by @user1937198 gave me a place to start, however I wasn't able to publish over ssh as suggested by the article because when I typed in ssh -R ... I was given the ssh usage help:
usage: ssh [-46AaCfGgKkMNnqsTtVvXxYy] [-b bind_address] [-c cipher_spec]
[-D [...
2
There is a g_audio driver which allows Linux systems with USB OTG support to show up as audio devices on the USB host.
You won't be able to do it on a Pi 3 though, you'll need a Pi 4 or a Zero which support OTG.
2
You can try to use a mediarenderer together with a controlpoint. I cannot say if it is the right program for your setup because lack of additional information. But it is worth to have a look at it. It is needed that the media sources (different smartphones?) announce themselves as media server by uPNP/DLNA on your local network. I know apps that do it (...
2
Answered my own question with help from this link
from Mark Hills
Once you have bluealsa working and can connect devices and play, then these additional steps open up dmix capability and allow audio mixing.
Install loop module once only.
modprobe snd-aloop
Edit /etc/asound.conf for each bluetooth connection - i.e. if you change device, update this file.
...
2
In my case the problem was that raspberrypi-ui-mods had been held back and it needed to be force updated. You can confirm this by checking if there is a message about it being held back when you run sudo apt upgrade.
Upgrade raspberrypi-ui-mods by running sudo apt-get upgrade raspberrypi-ui-mods.
If you remove pulseaudio, apart from this not being ...
2
It is a known issue on the PI4. Take a look at the forum thread:
https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=311457#p1864038
1
I got pulseaudio 7 running on my raspberry jessie. I used this post, in DEBIAN, if it can be useful (but remember: IN DEBIAN). Debian 8 Jessie.
I've found a way to use pc like an headset with Android phone (for making callings).
!!! I've use pulseaudio from jessie-backports: I don't know how much this takes risks ;-) !!!
In /etc/apt/sources.list ...
1
I got the same error and solved as following:
$ sudo apt-get install pulseaudio-module-bluetooth
$ pulseaudio --start
$ bluetoothctl
$ connect @MACtoConnect
1
In my case, the choppiness was due to the fact the bluetooth device scan kept running in the background and was never stopped. The choppiness disappeared once the scan was stopped using,
scan off
This was written after bluetoothctl was executed.
1
So I've just come across this thread and found it useful. Flittermice's answer was nearly there for me but I may a slight amendment which seems to have worked well.
In the /etc/xdg/autostart/pulseaudio.desktop file the config says to Exec=start-pulseaudio-x11 and if you trace this file it's actually a shell script located in /usr/bin/. This script itself ...
1
that's the old Philippine rice cook principle:
one cook, one plate, one fireplace.
With other words:
Its not possible, its a principle of pairing: one sender one reciever
1
As indicated in https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting
Use
load-module module-udev-detect tsched=0
in /etc/pulse/default.pa. This fixes the choppy audio
1
The 3.5mm output jack on the Pi is unique. See this link: http://www.raspberrypi-spy.co.uk/2014/07/raspberry-pi-model-b-3-5mm-audiovideo-jack/
1
Did you try running "amixer cset numid=3 1" to set the output to the audio jack.
If that didn't work try the setting the audio output to another interface such as HDMI, if this works then you know that the problem is with the audio jack. Just make sure to use "amixer cset numid=3 2" to set the ouput to HDMI.
Have a look at this page here for more details.
Only top voted, non community-wiki answers of a minimum length are eligible