Moode Audio Player for Raspberry Pi

Hi,

I built 4.0 beta 9 using recipe 1.7. On the whole things seem to work.

I installed the following extras: shairport-sync, squeezelite and upmpdcli.

I am not getting any metadata with shairport-sync (it is toggled on) otherwise the audio is working correctly.

As previously noted, I am getting "cover art not found" when using upnp from BubbleUPnP or Linn Kazoo. Audio and track info are working fine.

Squeezelite is not working for me inasmuch as the player is not visible to the server. My other squeezelite instances are visible.

Any ideas?

Thanks.
 
Hi,

Pretty easy to implement using avahi (mDNS) but whats the usage scenario for this feature?

Typically multiple players would be open in Browser tabs, or is it just more convenient to be able to switch to different player from within the player itself?

-Tim
On android I saved the url to one player on my home screen. From there I can then control all volumio devices. You don't have to type - or remember - URLs, no need to add multiple tabs; It just works. I find it a very welcome addition.
 

Attachments

  • Screenshot_20171118-001831.png
    Screenshot_20171118-001831.png
    431.5 KB · Views: 277
Using Build Recipe v1.9, 2017-11-15. At Step 2 trying to expand root partition.
This error message is returned sudo: unable to resolve host raspberrypi

I am on a MAC with Rpi3 connected via ethernet cause my network can't see the Rpi.

See screen shot attached.

Thanks for any suggestions.
 

Attachments

  • Screen Shot 2017-11-17 at 11.48.51 AM.png
    Screen Shot 2017-11-17 at 11.48.51 AM.png
    23 KB · Views: 234
sudo nano /etc/hosts

And add raspberry after moode on the line which contains moode and don’t forget the Space between the two hostnames.

Save and you can resume the recipe

You will be able to delete this add after next reboot if you wish
Using Build Recipe v1.9, 2017-11-15. At Step 2 trying to expand root partition.
This error message is returned sudo: unable to resolve host raspberrypi

I am on a MAC with Rpi3 connected via ethernet cause my network can't see the Rpi.

See screen shot attached.

Thanks for any suggestions.
 
Last edited:
sudo nano /etc/hosts

And add raspberry after moode on the line which contains moode and don’t forget the Space between the two hostnames.

Save and you can resume the recipe

You will be able to delete this add after next reboot if you wish

Thanks I made the change you suggested. Looks like it worked so I am able to move ahead. See screen shot. Cheers
 

Attachments

  • Screen Shot 2017-11-17 at 1.26.39 PM.png
    Screen Shot 2017-11-17 at 1.26.39 PM.png
    22.4 KB · Views: 262
where does the cd ~ come from?

isn't this what you should be applying:

sudo apt-get -y install bluez bluez-firmware pi-bluetooth \
dh-autoreconf expect libortp-dev libbluetooth-dev libasound2-dev \
libusb-dev libglib2.0-dev libudev-dev libical-dev libreadline-dev libsbc1 libsbc-dev

cd /tmp
sudo git clone GitHub - Arkq/bluez-alsa: Bluetooth Audio ALSA Backend
cd bluez-alsa
sudo autoreconf --install
sudo mkdir build
cd build
sudo ../configure --disable-hcitop --with-alsaplugindir=/usr/lib/arm-linux-gnueabihf/alsa-lib
sudo make
sudo make install
cd ~
sudo rm -rf /tmp/bluez-alsa

sudo systemctl daemon-reload
sudo systemctl disable bluetooth.service
sudo systemctl disable bluealsa.service
sudo systemctl disable hciuart.service

sudo mkdir -p /var/run/bluealsa
sudo sync
sudo apt-get clean

sudo reboot
--------------------------------------------------------------------
Please note that I am not running this install as 8 worked fine for me and I have simply updated to Beta 9. Good Luck, you will get there through perseverance or help from the forum.
 
Last edited:
where does the cd ~ come from?

isn't this what you should be applying:

sudo apt-get -y install bluez bluez-firmware pi-bluetooth \
dh-autoreconf expect libortp-dev libbluetooth-dev libasound2-dev \
libusb-dev libglib2.0-dev libudev-dev libical-dev libreadline-dev libsbc1 libsbc-dev

cd /tmp
sudo git clone GitHub - Arkq/bluez-alsa: Bluetooth Audio ALSA Backend
cd bluez-alsa
sudo autoreconf --install
sudo mkdir build
cd build
sudo ../configure --disable-hcitop --with-alsaplugindir=/usr/lib/arm-linux-gnueabihf/alsa-lib
sudo make
sudo make install
cd ~
sudo rm -rf /tmp/bluez-alsa

sudo systemctl daemon-reload
sudo systemctl disable bluetooth.service
sudo systemctl disable bluealsa.service
sudo systemctl disable hciuart.service

sudo mkdir -p /var/run/bluealsa
sudo sync
sudo apt-get clean

sudo reboot
--------------------------------------------------------------------
Please note that I am not running this install as 8 worked fine for me and I have simply updated to Beta 9. Good Luck, you will get there through perseverance or help from the forum.

Ok - see there error.

Have started again with Step 4.2. Same error message. Time to start from scratch it seems. Glad folks on this forum are here with a helping hand.

See attached.
 

Attachments

  • Screen Shot 2017-11-17 at 4.38.49 PM.png
    Screen Shot 2017-11-17 at 4.38.49 PM.png
    47.9 KB · Views: 240