I am trying to get audio to LedFx, a controller for sound reactive LEDs. One of the ways it can read audio through its docker container is through a named pipe. The command ffmpeg -y -i http://wms-15.streamsrus.com:11630 -f u16le -acodec pcm_s16le -ac 2 -ar 44100 ~/audio/stream is able to play audio into the container, but for some reason, every ffmpeg, parecord, or arecord command that I use to capture system audio doesn't work.

I am on Raspbian Lite, and I've changed my soundcard from the audio jack output to a USB dac output by setting this in /usr/share/alsa/alsa.conf:

defaults.ctl.card 1
defaults.pcm.card 1

I am recieving audio from bluetooth with the rpi-audio-reciever project, and everything is working properly and playing on my DAC. How can I route this audio to my LEDs too?

  • Any reason not to use PulseAudio? It comes with a lot of plugins, including network and bluetooth. Mar 11, 2021 at 11:19
  • @DmitryGrigoryev No reason not to. Pulseaudio is installed on the system. I've just solved all the audio receiving problems without it, and LedFx is running inside a docker container. If you can figure out how to route audio into that named pipe with Pulseaudio, that would be great. I've already tried module-pipe-source with no luck.
    – Byte11
    Mar 11, 2021 at 20:53
  • With Pulse you woldn't need the pipe, you could receive your audio directly using pulseaudio-module-bluetooth. Mar 16, 2021 at 10:14
  • Right, but I'm already receiving audio through bluetooth and hearing it play over my speakers. pulseaudio-module-bluetooth accomplishes the same thing rpi-audio-reciever uses bluealsa for. The key is also sending the audio to LedFx
    – Byte11
    Mar 17, 2021 at 18:36


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.