393
edits
Changes
Jump to navigation
Jump to search
Line 20:
Line 20: + + + + + + + + + + + + + + +
Configuring Audio Devices (view source)
Revision as of 23:09, 10 November 2017
, 23:09, 10 November 2017about bluetooth speakers
http://blog.scphillips.com/posts/2013/01/sound-configuration-on-raspberry-pi-with-alsa/
http://blog.scphillips.com/posts/2013/01/sound-configuration-on-raspberry-pi-with-alsa/
To debug audio problems, I access the Linux command line via ssh and use some command-line utilities to test and configure.
The Linux audio system is called ALSA. You can install '''alsa-utils''' to get some command line tools for testing/configuring audio. Unfortunately, ALSA and Linux audio configuration is complex and hard to figure out.
Install those utilities by giving the command:
sudo apt-get install alsa-utils
Here’s some documentation on ALSA http://www.linuxfromscratch.org/blfs/view/cvs/multimedia/alsa-utils.html1
One command I use is '''speaker-test'''. This will cause your audio device to make tones, if everything is properly configured.
===Bluetooth speakers===
A “Bluetooth speaker” is an audio device in its own. In order to get this device working with Zynthian you need to configure it with Jack Audio. See the “audio config” tab in the webconf tool.
Anyway, when you configure the bluetooth device and get it working with Zynthian, i suspect that latency will be too big for playing/sequencing in real-time. A wireless device like this normally need a big buffer to avoid “cuts”. In my very first tests I used a BT speaker “just for fun”. Latency was a little less than 1 second, more than enough to make it unplayable