adding an 'asymmetrical' ALSA device worked:
change the contents of /etc/asound.conf and ~/.asoundrc to the following:
and sudo alsa force-reload for good measure
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.
Using a bluetooth dongle or Wi-Fi dongle resolve the problem.
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 ...
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 ...
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:
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)
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.
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 ...
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,
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]
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 ...
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
Then I had to plug in a monitor and keyboard and make sure it connected on the desktop, ...
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 ...
Okay, I've done some tests.
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)
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]
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 (...
You may have a problem that's unrelated to the fact that you're using a DAC, but with the radio webpage itself. This may be an easily fixable issue, however, I will offer a different approach:
After inspecting the webpage source, I noticed that the radio stream it plays is at th following URL: http://audio.scdn.arkena.com/11016/fip-midfi128.mp3. You can ...
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 ...
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,
This was written after bluetoothctl was executed.
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 ...
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.
This worked for me - totally in remote SSH session:
Mini Bluetooth Speaker
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install pi-bluetooth ( "already the newest version" )
sudo apt-get install blueman pulseaudio pavucontrol pulseaudio-module-bluetooth
hcitool dev (look for bluetooth address of the built-in adapter)
The default audio out on the Pi models uses PWM for audio, so is not really for hi quality audio.but is enough to make it audible - for example see the tests done here
If you want better quality you can use a variety of USB Sound Cards, or addon boards like the HiFiBerry.
There are two PWM channels used by the audio jack (left and right I guess).
These audio channels can be directed to zero, one, or more gpios as follows.
channel 0: gpios 12 (alt0), 18 (alt5), 40 (alt0), and 52 (alt1).
channel 1: gpios 13 (alt0), 19 (alt5), 41 (alt0), 45 (alt0), and 53
To direct PWM to a gpio you set the gpio to the particular mode ...
I've got audio piping into a bluetooth speaker with a pi 3 via pulse and MPD.
Here's how I got it working:
Factory install raspbian jessie (had trouble with lite and bluetooth permissions) onto the raspberry pi 3.
Run raspi-config in terminal and expand the filesystem, then reboot.
Install pulseaudio bluetooth support via the following command.
I'm in a similar position. But as of Nov 27,2015 I don't think this is supported. I totally agree with you about the documentation issue. When I execute bluetoothctl and poke around this is what I found. Here's why it doesn't work:
Bluetooth capability mismatch-
Raspberry Pi bluetooth doesn't report a UUID for A2DP, I'm expecting that it should. Also /etc/...