Personal tools
You are here: Home documentation Raspberry Pi

  • According to some it will get you a more stable audio performance if you make sure that the power supply is providing enough Voltage and Ampère (guarateeing that the Voltage doesn't go below 5V, and making sure that you can draw up to 2Amp from the power supply if you have other devices connected to the Pi).

  • It is a good idea to run the Raspberri Pi headless if you only want it to make audio. Leave mouse, keyboard and screen disconnected. Connect via the ethernet to your network, give the Raspberry Pi a fixed IP and control it with another computer through a SSH connection. This way you will also avoid problems with Keyboards when you have to slow down the USB port to 1.1, because most keyboards seem to not like that (exeption: Bluetooth Keyboards).

  • General Info about the Raspberry Pi and low latency audio in the LinuxAudio wiki

Available Distros

Audio and the Raspberri Pi

Idea: writing here a short blurp what the issues/problems are with the on board audio possibilities of the Raspberry (the mini stereo jack and the HDMI audio). There is no audio-in on the Raspberry Pi, so for input you will need a device on one of the USB ports.

Working Soundcards

This list is kind of replicating what you can already find in the wiki

  • Logitech USB To 3.5mm Jack Audio Adapter ASIN: B0058P0I2C w/ dwc_otg.speed=1

  • Beringher UCA222 w/ dwc_otg.speed=1

  • Griffin iMic. Cheap, 3.5mm jacks, mic/line in, USB powered w/ dwc_otg.speed=1

  • ESI UDJ 6, 6 24bit outputs @ 48kHz : 4 line output on RCA, 2 headphone out on jack 6,3mm, USB powered, works out of box on Raspbian (i.e. without USB speed down), tested with kernel 3.6.11+ and active ethernet connection and with Pd Vanilla 0.44-2, can't manage to make it work with only 2 outputs @ 96kHz.

  • ESI UGM6 ouput works with alsa driver without USB slowdown, input doesn't work with output and ethernet(got crackles). Input and output seems to work after disabling ethernet (see the linuxaudio wiki for more info (link on top of this page)). Interface not seen correctly with USB slowdown.

  • ESI GIGAPort AG (old version), only the last 6 outputs works. Out 1&2 does work either on headphone or on RCA plug. Don't know why...

  • ESI GIGAPort HD+. Works fine with alsa driver and without USB slowdown. Note this is HD+ (HD plus) version, the HD is reported to not work.

  • HY544 USB 3D Sound Adapter. You just need to type 'amixer -c 1 set Mic 80% cap' in a term window to enable to Mic. In Pd, under preferences, choose 'Alsa' as output and under 'audio configuration', select 'input Generic AudioUSB Device (hardware) Channels 1' and 'output Generic USB Audio Device (plug-in) Channels 2'.

*M-Audio MobilePre USB works with ALSA driver and without USB slowdown on Raspbian, but may only work at 22,050 Hz.

Not Working Soundcards

  • ESI GIGAPort HD. Tried with and without USB slowdown. Device not seen at all.

  • Hercules Muse Pocket LT. Without dwc_otg.speed=1: 6 channels can be outputed but sound quality is poor (cracks...). With dwc_otg.speed=1: works with 2 channels (though an unwanted sine can be heard), more than 2 channels does not work ("ALSA output error (snd_pcm_hw_params): Invalid argument" or "read other error -77").

  • Terratec Aureon 7.1 USB. 3.5mm jacks. Only works with up to 2 channels. Setting the USB speed down to 1.1 does not work (yields: schedule_periodic: Insufficient periodic bandwidth for periodic transfer).

  • RME Fireface UCX (and also Fireface UC, Babyface and any other UAC 2 device). The USB Class Compliant mode provided by the Firmware should make the device compatible under Linux, but a bug in the ALSA /sound/usb/mixer.c actually prevents it to run. You'll have to compile the kernel yourself with a tiny fix or wait until 3.8 is available for the raspberry (wheezy is 3.2).

note: "dwc_otg.speed=1" is a string to add to the file, /boot/cmdline.txt, which slows down all USB devices to 1.1 speed - including ethernet. For some reason, when running with slow USB, USB (wired or with wireless dongle) keyboards don't work (connecting one will instantly crash the pi). The workaround is to either use a bluetooth keyboard or log in remotely via ssh -XY See, e.g., On the other hand, at least one device, the E-MU 0404, apparently can work with USB set to its faster default speed (2.0):

Powered by IEM Powered by Plone Section 508 WCAG Valid XHTML Valid CSS Usable in any browser