# Mopidy on Raspberry Pi Zero MPDroid Audio Output

**URL:** <https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420>\
**Category:** Misc\
**Created:** [December 12, 2016, 11:01am UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420 "2016-12-12T11:01:38Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Peter\_Jones](https://avatars.discourse-cdn.com/v4/letter/p/97f17d/32.png) [@Peter\_Jones](https://discourse.mopidy.com/u/Peter_Jones)\
**Post date:** [December 12, 2016, 11:01am UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/1 "2016-12-12T11:01:38Z")

</div>

Hello,

I have successfully set-up Mopidy on my Raspberry Pi Zero. My Pi Zero is plugged into a TV via HDMI and I can play and control this via MPDroid and hear the sound on the TV.

Can anyone tell me if I can play the audio through the MPDroid App? When I go to settings and Outputs the only option is NULL.

I know when you set-up MPD on its own there is an Audio Output section in the configuration, but I don’t know where this is within Mopidy.

Thank you in advance.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [December 12, 2016, 3:57pm UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/2 "2016-12-12T15:57:12Z")

</div>

There is no streaming built into Mopidy itself but you can use icecast. See [https://docs.mopidy.com/en/latest/audio/#streaming-through-icecast](https://docs.mopidy.com/en/latest/audio/#streaming-through-icecast)

---

<div class="post-metadata">

**Author:** ![Peter\_Jones](https://avatars.discourse-cdn.com/v4/letter/p/97f17d/32.png) [@Peter\_Jones](https://discourse.mopidy.com/u/Peter_Jones)\
**Post date:** [December 12, 2016, 4:37pm UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/3 "2016-12-12T16:37:42Z")

</div>

Thank you kingosticks. I will try that tonight. I’m assuming Icecast has a Raspberry Pi ARM built? I will update in this post in the morning.

---

<div class="post-metadata">

**Author:** ![xsteadfastx](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/xsteadfastx/32/480_2.png) [@xsteadfastx](https://discourse.mopidy.com/u/xsteadfastx)\
**Post date:** [December 13, 2016, 11:10am UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/4 "2016-12-13T11:10:42Z")

</div>

another thing that works good for me is the use of snapcast. i use the snapcast client on my raspi and on my android phone. works really great.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [December 13, 2016, 12:11pm UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/5 "2016-12-13T12:11:04Z")

</div>

Yes I believe i does.

I’ve never actually tried snapcast myself but it requires the use of an output fifo which some people seem to run into trouble with, although perhaps that’s no longer the case. And of course you need the Android client too, you can’t just use MPDroid.

---

<div class="post-metadata">

**Author:** ![xsteadfastx](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/xsteadfastx/32/480_2.png) [@xsteadfastx](https://discourse.mopidy.com/u/xsteadfastx)\
**Post date:** [December 13, 2016, 12:20pm UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/6 "2016-12-13T12:20:20Z")

</div>

i used icecast before and i hated the lag mostly. with snapcast no problems so far and its pretty responsive on switching tracks or pausing. not what i could get working well with icecast. but thats just my experience.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [December 13, 2016, 12:25pm UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/7 "2016-12-13T12:25:43Z")

</div>

That is interesting. Do you also run the snapserver on a raspberry pi or something more beefy?

---

<div class="post-metadata">

**Author:** ![xsteadfastx](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/xsteadfastx/32/480_2.png) [@xsteadfastx](https://discourse.mopidy.com/u/xsteadfastx)\
**Post date:** [December 13, 2016, 12:37pm UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/8 "2016-12-13T12:37:36Z")

</div>

mopidy runs on my homeserver and the snapclient on the raspi. but im pretty sure running both would also work fine. mopidy and the snapcast server run in a docker container.

---

<div class="post-metadata">

**Author:** ![Peter\_Jones](https://avatars.discourse-cdn.com/v4/letter/p/97f17d/32.png) [@Peter\_Jones](https://discourse.mopidy.com/u/Peter_Jones)\
**Post date:** [December 13, 2016, 12:41pm UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/9 "2016-12-13T12:41:26Z")

</div>

Hi xsteadfastx,

Would you consider documenting how you set this up?

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [December 13, 2016, 1:01pm UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/10 "2016-12-13T13:01:04Z")

</div>

Their documentation looks pretty solid [https://github.com/badaix/snapcast/blob/master/doc/player\_setup.md#mopidy](https://github.com/badaix/snapcast/blob/master/doc/player_setup.md#mopidy)

---

<div class="post-metadata">

**Author:** ![xsteadfastx](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/xsteadfastx/32/480_2.png) [@xsteadfastx](https://discourse.mopidy.com/u/xsteadfastx)\
**Post date:** [December 14, 2016, 8:45am UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/11 "2016-12-14T08:45:42Z")

</div>

im writing a blog post right now about it. but the docs mentioned from @kingosticks is what i used mostly. its really straight forward and works really well.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [December 14, 2016, 9:28am UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/12 "2016-12-14T09:28:40Z")

</div>

I actually gave it a quick go last night. The default snapserver options work without any modification (assuming you go with their suggested mopidy output setting). I didn’t test with it for very long but experienced one instance where the client audio stopped and I had to restart the song. Presumably the Fifo got in a mess, I saw a bunch of gstreamer sink warnings.

---

<div class="post-metadata">

**Author:** ![xsteadfastx](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/xsteadfastx/32/480_2.png) [@xsteadfastx](https://discourse.mopidy.com/u/xsteadfastx)\
**Post date:** [December 14, 2016, 9:48am UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/13 "2016-12-14T09:48:34Z")

</div>

maybe its a permission problem with the fifo file. in my setup i run snapserver as the same user as mopidy and it runs for a week now without problems.

---

<div class="post-metadata">

**Author:** ![kingosticks](https://avatars.discourse-cdn.com/v4/letter/k/858c86/32.png) [@kingosticks](https://discourse.mopidy.com/u/kingosticks)\
**Post date:** [December 14, 2016, 10:03am UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/14 "2016-12-14T10:03:47Z")

</div>

I only experienced an issue once. I would expect a permission problem to be permanent. I’ll give it some more rigorous testing on the weekend. I want to try out the multi-client synchronised playback anyway.

---

<div class="post-metadata">

**Author:** ![Peter\_Jones](https://avatars.discourse-cdn.com/v4/letter/p/97f17d/32.png) [@Peter\_Jones](https://discourse.mopidy.com/u/Peter_Jones)\
**Post date:** [December 14, 2016, 10:24am UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/15 "2016-12-14T10:24:48Z")

</div>

@xsteadfastx Where is your blog?

---

<div class="post-metadata">

**Author:** ![jjok](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/jjok/32/448_2.png) [@jjok](https://discourse.mopidy.com/u/jjok)\
**Post date:** [December 14, 2016, 11:39am UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/16 "2016-12-14T11:39:02Z")

</div>

I set up Snapcast with Mopidy and had no issues at all.

The only thing I found was that a Pi Zero isn’t really powerful enough to run Mopidy, Snapserver and Snapclient together.

I think Snapcast is the best solution for multi-room audio.

---

<div class="post-metadata">

**Author:** ![xsteadfastx](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/xsteadfastx/32/480_2.png) [@xsteadfastx](https://discourse.mopidy.com/u/xsteadfastx)\
**Post date:** [December 15, 2016, 8:40am UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/17 "2016-12-15T08:40:02Z")

</div>

@Peter_Jones[http://xsteadfastx.org/2016/12/14/audio-uberall-mopidy-und-snapcast/#audio-uberall-mopidy-und-snapcast](http://xsteadfastx.org/2016/12/14/audio-uberall-mopidy-und-snapcast/#audio-uberall-mopidy-und-snapcast) but its in german. but mainly i just did what the official docs said.

@jjok i think so too… but i guess the pi zero will be a perfectly snapclient. maybe a model B Pi would work with mopidy and snapserver.

---

<div class="post-metadata">

**Author:** ![jjok](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/jjok/32/448_2.png) [@jjok](https://discourse.mopidy.com/u/jjok)\
**Post date:** [December 15, 2016, 12:00pm UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/18 "2016-12-15T12:00:40Z")

</div>

@xsteadfastx I think the Zero would be fine running just Snapclient, although I haven’t tried it.

I did have Mopdiy, Snapserver and Snapclient all running on a Pi2, and that was fine.

---

<div class="post-metadata">

**Author:** ![jjok](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/jjok/32/448_2.png) [@jjok](https://discourse.mopidy.com/u/jjok)\
**Post date:** [December 15, 2016, 12:07pm UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/19 "2016-12-15T12:07:10Z")

</div>

Has anyone tried using different settings to output to the Snapcast pipe? Presumably you don’t need it to be 48KHz if you’re just playing MP3s. Could you get much of a performance improvement by optimising it?

---

<div class="post-metadata">

**Author:** ![xsteadfastx](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.mopidy.com/xsteadfastx/32/480_2.png) [@xsteadfastx](https://discourse.mopidy.com/u/xsteadfastx)\
**Post date:** [December 15, 2016, 12:39pm UTC](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420/20 "2016-12-15T12:39:09Z")

</div>

@jjok i tried it with vorbis output and it started to have problems. i guess its because of the decoding on the client is too slow to play it without artefacts… but thats just my guess.

[Next page](https://discourse.mopidy.com/t/mopidy-on-raspberry-pi-zero-mpdroid-audio-output/1420.md?page=2)