Moode Audio Player for Raspberry Pi

Hi, i found out that airplay reciver doesn't work with the last beta and my usb-dac-amplifier (alientek d8).
searching on internet i found out that you have to change this line:

output_device = "hw:1"

to

output_device = "plughw:1"

in the "/usr/local/etc/shairport-sync.conf"

starting shairport-sync from command line infact work flawlessly, but this change in the config file doesn't effect moode, as i can see on the moode.log there is a script wich pass this command:

(/usr/local/bin/shairport-sync -a "Moode Airplay" -S soxr -w -B /var/local/www/commandw/spspre.sh -E /var/local/www/commandw/spspost.sh --metadata-pipename=/tmp/shamp/shairport-sync-metadata --get-coverart -- -d hw:1 -c "Mic" > /dev/null 2>&1 &)

how i can edit this script? i think i've to change hw:1 to plughw:1

can you help me?

Hi,

Instead, open the Airplay Config screen and try changing the bit-depth to 24 or 32.

-Tim
 
Hi,

is there any way of streaming from the moodeaudio device to a bluetooth speaker? I installed my rasberry with hifiberry dac in the caravan, I sometimes would like to stream from there to a bluetooth speaker outside. I am using version 4b12.


Hi,
Yes there is way to send audio to Bluetooth speaker and the feature will be integrated to the next build of moOde (4.0 final), but if you want the feature now, maybe you can make it with the Koda's proof of concept here :

A bit old ... but got it to work without modifications except editing mpd.conf (i can't choose this in Moode configuration), so let me explain :

On RPI3 (Wifi disabled), paired my bluetooth speaker with bluetoothctl (not a big deal , trust, pair, connect ) after discovering it.

In bluetoothctl :

[UE BOOM NOIR]# info 88:C6:26:XX:XX:XX
Device 88:C6:26:XX:XX:XX
Name: UE BOOM NOIR
Alias: UE BOOM NOIR
Class: 0x240418
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v000ApFFFFdFFFF
[UE BOOM NOIR]#


Then edit mpd.conf to add :

audio_output {
type "alsa"
name "Bluetooth Speaker"
device "bluealsa:HCI=hci0,DEV=88:C6:26:XX:XX:XX,PROFILE=a2dp"
}


But currently if i switch on my amp, i got also music on my speakers !!!

Maybe just because added on mpd.conf and not making a possible choice.

Maybe someone can rework this kind of settings ;)

regards

Cheers
 
Hi,

is there any way of streaming from the moodeaudio device to a bluetooth speaker? I installed my rasberry with hifiberry dac in the caravan, I sometimes would like to stream from there to a bluetooth speaker outside. I am using version 4b12.

Hi,
Yes there is way to send audio to Bluetooth speaker and the feature will be integrated to the next build of moOde (4.0 final), but if you want the feature now, maybe you can make it with the Koda's proof of concept here :

Cheers

Hi,

Correct, this Bluetooth feature will be included in moOde 4.0 GA at end of month :)

-Tim
 
Beyond me

How to install moOde on a RPi

Needed :
- a Raspberry Pi
- a micro SD Card of 4Gb minimum
- a computer to install Raspbian on the microSD (windows, mac, linux, unix,...) with a microSD Card drive
- on windows you have to use a third software to take the control of the RPi with ssh (explanation here)
- a fresh image of the last Raspbian Stretch lite downloadable here
- a software to install the image on the microSD like Etcher
- an internet connection

Steps :
- launch Etcher on your computer, drag the image of raspbian on the first icon, insert your micro SD card in your computer and launch it...
- When it's finished re-insert the microSD card in your computer, if all is good you can see a disk appear named "boot"
- create a blank file called ssh : (use your favorite text editor like notepad, smultron, Atom,... to save an empty file inside the "boot" disk)
- if you use wifi create a wpa_supplicant.conf file like explain here
- Eject the SD card, put it in the Raspberry pi and boot the raspberry (if you don't use wifi plug the ethernet on you RPi !)
- login to it in ssh with this command (the password at this step is: raspberry) :
Code:
ssh pi@raspberrypi
[I][COLOR=SeaGreen]#on Mac OS :[/COLOR][/I]
ssh [email]pi@raspberrypi.local[/email]
- And finally, just launch this command :
Code:
wget [url]https://transfer.sh/TWE3G/moosimbu.sh[/url] && chmod +x ./moosimbu.sh; sudo ./moosimbu.sh -u

How to know the installation process status

This is a (very) long process (depend of the connection, the microSD card and version of the RPi) and you must wait the END of the process. For look at the progress you can type this (the password at this step is: moodeaudio):
Code:
ssh pi@moode "cat ./mosbuild.log | grep  '^// \|^\*\* '"

[I][COLOR=SeaGreen]#on Mac OS :[/COLOR][/I]
ssh [email]pi@moode.local[/email] "cat ./mosbuild.log | grep  '^// \|^\*\* '"

[I][COLOR=SeaGreen]#if you are already logged to the raspberry, just enter:[/COLOR][/I]
cat ./mosbuild.log | grep  "^// \|^\*\* "
(yes, this is a different one... I have much more in my basket)

!!!! YOU MUST WAIT FOR THIS !!! :
Code:
// END
** Final reboot
If this is the case so you can enjoy your new installation of moOde, on your computer launch your web browser and access to http://moode or http://moode.local on a mac.

But Maybe you have this in the last line :
Code:
** error: ......
Don't panic and just reboot the RPi with this command:
Code:
ssh pi@moode "sudo reboot"

[I][COLOR=SeaGreen]#on Mac OS :[/COLOR][/I]
ssh [email]pi@moode.local[/email] "sudo reboot"

[I][COLOR=SeaGreen]#if you are already logged to the raspberry, just enter:[/COLOR][/I]
sudo reboot

The shorter version of the installation:
From a fresh installation of Raspbian Stretch lite launch this command:
Code:
wget [url]https://transfer.sh/TWE3G/moosimbu.sh[/url] && chmod +x ./moosimbu.sh; sudo ./moosimbu.sh -u
Finished !

Good Luck

PS: my link of the moosimbu.sh script expire in 14 days... i hope the new mosbuild came it before this date.

Well - I must be the dumbest bloke on the planet, followed instructions to the letter. 1st time ( after apparent succesful completion ) trying to access moode - got a page thanking me for installing INGXS or something similar. So - re-write card and run process again - FAILS unable to purge something or other.

Now I'm not a great techy but I am blessed with a certain amount of patience ( which has now been exhausted ) but after several years of using moode ( and paying - albeit not very much - for the prior version ) I'm afraid I need a less techy and more robust product to feed my passion for music. I'll be sad to change, moode has been great, the best of the bunch but spending a whole afternoon mucking about with a product that can now only apply to linux techs etc is not what I need. What I need is a music player - that works out of the box. So - goodbye, farewell and thank you for the music - it was great.
 
Hello AitchKay,
First at all, i'm not a moOde developper or anything like this and i don't guarantee my patches to be replace the official way.
For the moment the final version of moOde 4.0 is not ready, and the next builder version has been greatly improved by Koda since this modified version.

Well - I must be the dumbest bloke on the planet, followed instructions to the letter. 1st time ( after apparent succesful completion ) trying to access moode - got a page thanking me for installing INGXS or something similar. So - re-write card and run process again - FAILS unable to purge something or other.

I'm not sure i'm really clear in my post when i read your's. The part "How to know the installation process status" is very important. You must wait for the final reboot for using moOde. If an error appear, you must reboot your Pi not really restart the process from scratch.

Now I'm not a great techy but I am blessed with a certain amount of patience ( which has now been exhausted ) but after several years of using moode ( and paying - albeit not very much - for the prior version ) I'm afraid I need a less techy and more robust product to feed my passion for music. I'll be sad to change, moode has been great, the best of the bunch but spending a whole afternoon mucking about with a product that can now only apply to linux techs etc is not what I need. What I need is a music player - that works out of the box. So - goodbye, farewell and thank you for the music - it was great.

Maybe, you can contact directly Tim Curtis by mail, i think he gave you solutions for your problems.

We all know it's not an optimal solution and we try to do better. It's about time, and we want make things more easier, it's my goal and i think it's the goal of Koda, Tim and all contributors too.

Regards.
 
Last edited:
Probably you didn't wait long enough for the build to complete. It can take an hour or more.
Hi,

2+ hours each time. Fast ethernet & internet. On the first occasion everything terminated as per the instructions ( thats the one I got IGNX thingy with ). Second one really didn't want to play but assuming all would be good in the end I just left it 2+ hours no progress.

Clearly this type of install is beyond a simpleton like me - it's a great shame I've loved Moode for years and swear it sounds better than the alternatives ( and Tims approach to support is enviable ) but if this is the type of acrobatics I need to go through to keep it up to date then it's probably no longer for me.
 
Hello AitchKay,
First at all, i'm not a moOde developper or anything like this and i don't guarantee my patches to be replace the official way.
For the moment the final version of moOde 4.0 is not ready, and the next builder version has been greatly improved by Koda since this modified version.



I'm not sure i'm really clear in my post when i read your's. The part "How to know the installation process status" is very important. You must wait for the final reboot for using moOde. If an error appear, you must reboot your Pi not really restart the process from scratch.



Maybe, you can contact directly Tim Curtis by mail, i think he gave you solutions for your problems.

We all know it's not an optimal solution and we try to do better. It's about time, and we want make things more easier, it's my goal and i think it's the goal of Koda, Tim and all contributors too.

Regards.
"If an error appear, you must reboot your Pi not really restart the process from scratch." - this may well be where I went wrong - notwithstanding my (following) post I'll give it another go later in the week - thank you for your reply, I REALLY don't want to stop using Moode.
 
Hi,

To troubleshoot, start by posting some basic information for example:

- what model DAC?
- are u using the USB (UAC2) fix?

-Tim

I use a JLSounds USB to I2S interface (XMOS) module between the Rpi3 and a DIY I2S DAC which is based on ESS Sabre 9023 chip.

I don't use the USB (UAC2) fix since I never used it on earlier Moode releases (3.X)
I am telling you that the MPD option "DoP =no" has no effect unless you enable SoX resampling as well.
 
Last edited:
I set Heeboo's "one SD card" script running and went to watch a movie....IIRC, "Harry Potter and the Chamber of Secrets". I then rebooted and all was well :)

Nice :)

I'm stress testing the new Builder and so far Direct Build, Build to 2nd SDCard and Resume after error on either type of build work perfectly.

The "resume" capability is truly wonderful. Just reboot and the Builder resumes starting at the last STEP that contained the error. Also the nice alias commands moslog, mosbrief and moslast make it really easy to monitor the build if so desired.

-Tim