{"id":187,"date":"2019-08-25T16:44:44","date_gmt":"2019-08-25T23:44:44","guid":{"rendered":"http:\/\/eequalspi.com\/?p=187"},"modified":"2019-08-25T16:44:44","modified_gmt":"2019-08-25T23:44:44","slug":"mopidy-and-multiple-audio-streams-from-the-command-line-on-raspberry-pi","status":"publish","type":"post","link":"http:\/\/eequalspi.com\/index.php\/2019\/08\/25\/mopidy-and-multiple-audio-streams-from-the-command-line-on-raspberry-pi\/","title":{"rendered":"Mopidy and Multiple Audio Streams From the Command Line on Raspberry Pi"},"content":{"rendered":"\n

Background<\/h2>\n\n\n\n

I feel like almost everyone who has had to deal with\nanything outside the most mundane audio setup on Linux machines has experienced\nthe pain I’m about to describe. On Mac and Windows machines, audio seems to\n‘just work’ (TM) (R) (C) — and on linux desktops like Ubuntu it seems to be\nfine too.<\/p>\n\n\n\n

\"\"
PCM5102A Module, product photo from Amazon.com<\/figcaption><\/figure><\/div>\n\n\n\n

For my UNIAC project however, I went a little off the rails (dun-dun-dun). UNIAC 2.0 uses a Raspberry PI Zero W, which doesn\u2019t come with any onboard analog audio output, forcing me to use a third party sound card. Since the project had a nice backplane motherboard, I wanted a module I could just plop down on the board as if it were a component. Ultimately, I settled on a PCM5102A module like this one<\/a>, which took audio as I2S samples and cost all of $8. For the final, working version of this, I used Raspbian Buster (July 2019).<\/p>\n\n\n\n

As an aside, I created an EAGLE Footprint for the module, so you can incorporate one into your own projects if so desired.<\/p>\n\n\n\n

The Solution<\/h2>\n\n\n\n

To get it all working, we need the OS to do four things:<\/p>\n\n\n\n

  1. Recognize the new I2S sound card.<\/li>
  2. Use it by default.<\/li>
  3. Provide some software volume control.<\/li>
  4. Mix multiple audio streams at once<\/li><\/ol>\n\n\n\n

    PCM5102A Drivers<\/h1>\n\n\n\n

    These no-name PCM5102A modules are sketchy at best, and come with no meaningful support and no manual. Fortunately, they use the same IC as the Hifiberry DAC+<\/a> project. After getting this thing going I feel somewhat bad for not buying their board, but the form factor is just not what I need.<\/p>\n\n\n\n

    In theory you can follow the Hifiberry DAC+ setup instructions<\/a> to get basic output going \u2013 but don\u2019t <\/strong>use them if you want software volume control. For me following those instructions resulted in a weird situation where the software volume control didn\u2019t actually stick after reboot, so I recommend staying away.<\/p>\n\n\n\n

    Volume Control<\/h1>\n\n\n\n

    What did work for me, was a modified version of these instructions<\/a>. To get basic volume control working, I used the first few steps of those instructions. I’ll duplicate them here in case the site goes down.<\/p>\n\n\n\n

    Software setup<\/h3>\n\n\n\n

    First we need to disable the onboard sound by editing alsa-blacklist.conf:<\/p>\n\n\n\n

    sudo nano \/etc\/modprobe.d\/alsa-blacklist.conf<\/code><\/pre>\n\n\n\n
    Add:<\/p>\n\n\n\n
    blacklist snd_bcm2835<\/code><\/pre>\n\n\n\n
    Save and exit (^X, Y, enter).<\/p>\n\n\n\n
    Now, to set the IO, edit config.txt:<\/p>\n\n\n\n
    sudo nano \/boot\/config.txt<\/code><\/pre>\n\n\n\n
    Add:<\/p>\n\n\n\n
    dtoverlay=hifiberry-dac<\/code><\/pre>\n\n\n\n
    Remove or comment (#) the line:<\/p>\n\n\n\n
    dtparam=audio=on<\/code><\/pre>\n\n\n\n
    Leave the line:<\/p>\n\n\n\n
    dtparam=i2s=on<\/code><\/pre>\n\n\n\n
    commented out.
    \nSave and exit (^X, Y, enter).<\/p>\n\n\n\n
    Next add some alsa (sound) configuration:<\/p>\n\n\n\n
    sudo nano \/etc\/asound.conf<\/code><\/pre>\n\n\n\n
    Paste the text below:<\/p>\n\n\n\n
    pcm.!default {\n  type hw\n  card 0\n}\nctl.!default {\n  type hw\n  card 0\n}<\/code><\/pre>\n\n\n\n
    Save and exit (^X, Y, enter).<\/p>\n\n\n\n
    It is no harm to do a reboot. So:<\/p>\n\n\n\n
    sudo reboot<\/code><\/pre>\n\n\n\n
    Test if everything is OK:<\/p>\n\n\n\n
    aplay -l<\/code><\/pre>\n\n\n\n
    This should return:<\/p>\n\n\n\n
    **** List of PLAYBACK Hardware Devices **** card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pcm5102a-hifi-0 [] Subdevices: 1\/1 Subdevice #0: subdevice #0<\/code><\/pre>\n\n\n\n
    If you have an amplifier you can connect via a phono lead you can now test it via: speaker-test -D -c -twav So:<\/p>\n\n\n\n
    speaker-test -D default -c 2 -twav<\/code><\/pre>\n\n\n\n
    This is a continuous test saying \u2018front left\u2019 and \u2018front right\u2019 alternately from the appropriate speakers. Enter ^C to stop.<\/p>\n\n\n\n
    Adding Software Volume Control<\/h3>\n\n\n\n
    This is an optional step that adds a software volume control into the  sound processing sequence. <\/p>\n\n\n\n
    sudo nano \/etc\/asound.conf<\/code><\/pre>\n\n\n\n
    add the following:<\/p>\n\n\n\n
    pcm.sftvol {\n   type softvol \n   slave.pcm \"plughw:0\" \n   control { \n     name \"PCM\" \n     card 0 \n   }<\/code><\/pre>\n\n\n\n
    Enter or change the pcm.!default section to:<\/p>\n\n\n\n
    pcm.!default { \n   type plug \n   slave.pcm \"sftvol\" \n }<\/code><\/pre>\n\n\n\n
    Save and exit (^X, Y, enter).
    \n Now we can test it, as before:<\/p>\n\n\n\n
    speaker-test -D default -c 2 -twav<\/code><\/pre>\n\n\n\n
    This should give alternating “front right” and “front left” from the respective speakers.<\/p>\n\n\n\n
    Great, but what about multiple streams?<\/h2>\n\n\n\n
    Here’s where we go off the rails. We need to add a software mixer to this cozy little ALSA setup. Fortunately, DMIX is a thing<\/a>. There are a few dmix examples out there. What we need to do, however, is connect dmix to softvol to a PCM sound device. This I could not find documented clearly anywhere on the internet, so here we are.<\/p>\n\n\n\n
    pcm.!default {\n  type plug\n  slave.pcm \"softvol\"\n}\n\npcm.softvol {\n  type softvol\n  slave {\n    pcm \"dmix\" #redirect the output to dmix\n  }\n  control {\n    name \"PCM\" #override PCM slider to set softvol lvl globally\n    card 0\n  }\n}<\/code><\/pre>\n\n\n\n
    Great, Now What?<\/h2>\n\n\n\n
    To get MOPIDY to work (my ultimate goal here), I had to do two things:<\/p>\n\n\n\n
    1. Install mopidy-alsamixer.<\/li>
    2. Edit ~\/.config\/mopidy\/mopidy.conf<\/li><\/ol>\n\n\n\n
      In mopidy.conf, I had to change the audio section to this:<\/p>\n\n\n\n
      \n#mixer = software\nmixer = alsamixer\noutput = alsasink device=plug:softvol\n#mixer_volume = \n#output = autoaudiosink\n#buffer_time = <\/code><\/pre>\n\n\n\n
      And then I added an alsamixer config as follows:<\/p>\n\n\n\n
      [alsamixer]\ncard = 0\ncontrol = PCM\nmin_volume = 0\nmax_volume = 100\nvolume_scale = cubic<\/code><\/pre>\n\n\n\n
      Finally after weeks of pain, I’ve arrived at a configuration that works!<\/p>\n","protected":false},"excerpt":{"rendered":"
      Background I feel like almost everyone who has had to deal with anything outside the most mundane audio setup on Linux machines has experienced the pain I’m about to describe. On Mac and Windows machines, audio seems to ‘just work’ (TM) (R) (C) — and on linux desktops like Ubuntu it seems to be fine … Continue reading “Mopidy and Multiple Audio Streams From the Command Line on Raspberry Pi”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[18,22,19,20,16,17,21],"class_list":["post-187","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-alsa","tag-linux","tag-mopidy","tag-pcm5102a","tag-raspberrypi","tag-rpi","tag-uniac"],"_links":{"self":[{"href":"http:\/\/eequalspi.com\/index.php\/wp-json\/wp\/v2\/posts\/187","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/eequalspi.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/eequalspi.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/eequalspi.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/eequalspi.com\/index.php\/wp-json\/wp\/v2\/comments?post=187"}],"version-history":[{"count":7,"href":"http:\/\/eequalspi.com\/index.php\/wp-json\/wp\/v2\/posts\/187\/revisions"}],"predecessor-version":[{"id":195,"href":"http:\/\/eequalspi.com\/index.php\/wp-json\/wp\/v2\/posts\/187\/revisions\/195"}],"wp:attachment":[{"href":"http:\/\/eequalspi.com\/index.php\/wp-json\/wp\/v2\/media?parent=187"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/eequalspi.com\/index.php\/wp-json\/wp\/v2\/categories?post=187"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/eequalspi.com\/index.php\/wp-json\/wp\/v2\/tags?post=187"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}