Moode Audio Player for Raspberry Pi

Interesting. It could be a date/time issue.
Did you try to update kernel manually ?

I did the kernel update manually following the exact steps in the build recipe and it went through without an issue. When I boot it up it still does not broadcast the AP on wifi. When I connect to the RPI via LAN I can hit the moOde interface on my browser.

I will re-install the enhanced networking manually and see what happens.
 
Hi Tim,

It's not working for me -- doesn't seem to be writing to the SD card after invoking mosbuild.sh. Here's the terminal output:

Code:
pi@raspberrypi:~ $ ls
mosbuild  mosbuild.sh
pi@raspberrypi:~ $ ls -al
total 40
drwxr-xr-x 3 pi   pi    4096 Dec 12 04:11 .
drwxr-xr-x 3 root root  4096 Nov 29 01:22 ..
-rw-r--r-- 1 pi   pi     220 Nov 29 01:22 .bash_logout
-rw-r--r-- 1 pi   pi    3523 Nov 29 01:22 .bashrc
drwxr-xr-x 2 root root  4096 Dec 12 04:10 mosbuild
-rwxr-xr-x 1 root root 12562 Dec  8 22:14 mosbuild.sh
-rw-r--r-- 1 pi   pi     675 Nov 29 01:22 .profile
pi@raspberrypi:~ $ ls -al mosbuild
total 1814540
drwxr-xr-x 2 root root       4096 Dec 12 04:10 .
drwxr-xr-x 3 pi   pi         4096 Dec 12 04:11 ..
-rw-r--r-- 1 root root 1858076672 Dec 12 04:10 2017-11-29-raspbian-stretch-lite.img
pi@raspberrypi:~ $ sudo chmod +x /home/pi/mosbuild.sh
pi@raspberrypi:~ $ sudo ./mosbuild.sh
****************************************************************
**
**  Moode OS Image Builder v1.0
**
**  Welcome to the automated process for creating the wonderful
**  custom Linux OS that runs moOde audio player.
**
**  You will need a Raspberry Pi running Raspbian with SSH
**  enabled, at least 2.5GB free space on the boot SDCard and
**  a spare USB or USB-SDCard drive that the new OS will be
**  written to during the build process.
**
**  Be sure to backup the SDCard used to boot your Pi
**
****************************************************************

////////////////////////////////////////////////////////////////
//
// STEP 1 - Download Raspbian Lite and create a new, base image
//
////////////////////////////////////////////////////////////////

** Check free disk space
** Do you have a backup of your boot SDCard (y/n)? y
** Unplug all USB storage devices from the Pi
** Are all USB storage devices unplugged (y/n)? y
** Plug in target USB drive for the new OS
** Is target USB drive plugged in (y/n)? y
** USB drive detected on /dev/sda
/dev/sdb
/dev/sdc
/dev/sdd
/dev/sde
** Partitions unmounted on /dev/sda
/dev/sdb
/dev/sdc
/dev/sdd
/dev/sde
** Option 1-5: use a proxy server for Internet access (y/n)? n
** Option 2-5: use a WiFi connection instead of Ethernet (y/n)? n
** Option 3-5: configure /var/www as squashfs (y/n)? y
** Option 4-5: install latest Linux Kernel (y/n)? y
** Option 5-5: Airplay, Ashuffle, LocalUI, Scrobbler, Squeezelite and UPnP/DLNA
** Install additional components (y/n)? y
** Ready for automated image build
** Proceed (y/n)? y
** Test Internet connection
** Download helper files
** Add options to properties file
** Load properties into env
** Base OS image was saved from previous build
** Use saved image to write to USB drive (y/n)? y
** Write image to USB drive on /dev/sda
/dev/sdb
/dev/sdc
/dev/sdd
/dev/sde
dd: unrecognized operand ‘/dev/sdb’
Try 'dd --help' for more information.
** Flush cached disk writes
**
** New base OS image created
**
** Remove the USB drive and use it to boot a Raspberry Pi
** The build will automatically continue at STEP 2 after boot
**
** Save base OS img for additional builds (y/n)? dd--help
** Valid entries are y|n
** Save base OS img for additional builds (y/n)? y

I'm trying again with a freshly-FAT-formatted 32GB SD card. This time, the green light came on on reboot, but it seems to be stuck on with no flickering. Is that what is supposed to happen? How long is the writing wait time generally?

BTW, an explanation of the y/n questions would be appreciated, or maybe just the better ones?

Stuart
 
Tim, I have beta 12 which I made using the image builder.
Basic functions work fine, however, I have 2 problems.

1. The upnp renderer is set on but it is not showing in Bubble upnp or
when using a upnp device scanner.

2. I have standard kernel only with no option to install the advanced kernels.

Where have I gone wrong?
For upnp try

Sudo chmod 644 /etc/upmpdcli.conf

And reboot.
 
MoOde and Foobar Upnp

Tim - I would very much like a solution for this issue: Your latest versions of moode all make a short break of about 4 seconds after 1 hour, 2 minutes and 8 seconds of continously playing a stream coming from my windows laptop with foobar as upnp server. This did not happen with earlier versions of moode. I cant remember when it occured the first time, but it really did not. Actually I´m using 3.8.4. It will stop playing in total, with moode playing in regular play mode, without continously playing mode. What can I do? The foobar settings were never changed.

Thanks in advance

Luki
 
Hi,

Noted.

Manual build recipe for upcoming Beta 12 has been updated. The automated Image Builder preserves wpa_supplicant.conf if one was initially configured :)

-Tim

Thanks Tim. As always, stellar work!

Having a bit of an issue on build 11 with the pimoroni pHat DAC.
No Alsa device detected. I ran their curl script so I might need to hammer away at that for a while, although it most likely was something I did (or didn't do).
 
Hi Tim,

It's not working for me -- doesn't seem to be writing to the SD card after invoking mosbuild.sh. Here's the terminal output:

Code:
pi@raspberrypi:~ $ ls
mosbuild  mosbuild.sh
pi@raspberrypi:~ $ ls -al
total 40
drwxr-xr-x 3 pi   pi    4096 Dec 12 04:11 .
drwxr-xr-x 3 root root  4096 Nov 29 01:22 ..
-rw-r--r-- 1 pi   pi     220 Nov 29 01:22 .bash_logout
-rw-r--r-- 1 pi   pi    3523 Nov 29 01:22 .bashrc
drwxr-xr-x 2 root root  4096 Dec 12 04:10 mosbuild
-rwxr-xr-x 1 root root 12562 Dec  8 22:14 mosbuild.sh
-rw-r--r-- 1 pi   pi     675 Nov 29 01:22 .profile
pi@raspberrypi:~ $ ls -al mosbuild
total 1814540
drwxr-xr-x 2 root root       4096 Dec 12 04:10 .
drwxr-xr-x 3 pi   pi         4096 Dec 12 04:11 ..
-rw-r--r-- 1 root root 1858076672 Dec 12 04:10 2017-11-29-raspbian-stretch-lite.img
pi@raspberrypi:~ $ sudo chmod +x /home/pi/mosbuild.sh
pi@raspberrypi:~ $ sudo ./mosbuild.sh
****************************************************************
**
**  Moode OS Image Builder v1.0
**
**  Welcome to the automated process for creating the wonderful
**  custom Linux OS that runs moOde audio player.
**
**  You will need a Raspberry Pi running Raspbian with SSH
**  enabled, at least 2.5GB free space on the boot SDCard and
**  a spare USB or USB-SDCard drive that the new OS will be
**  written to during the build process.
**
**  Be sure to backup the SDCard used to boot your Pi
**
****************************************************************

////////////////////////////////////////////////////////////////
//
// STEP 1 - Download Raspbian Lite and create a new, base image
//
////////////////////////////////////////////////////////////////

** Check free disk space
** Do you have a backup of your boot SDCard (y/n)? y
** Unplug all USB storage devices from the Pi
** Are all USB storage devices unplugged (y/n)? y
** Plug in target USB drive for the new OS
** Is target USB drive plugged in (y/n)? y
** USB drive detected on /dev/sda
/dev/sdb
/dev/sdc
/dev/sdd
/dev/sde
** Partitions unmounted on /dev/sda
/dev/sdb
/dev/sdc
/dev/sdd
/dev/sde
** Option 1-5: use a proxy server for Internet access (y/n)? n
** Option 2-5: use a WiFi connection instead of Ethernet (y/n)? n
** Option 3-5: configure /var/www as squashfs (y/n)? y
** Option 4-5: install latest Linux Kernel (y/n)? y
** Option 5-5: Airplay, Ashuffle, LocalUI, Scrobbler, Squeezelite and UPnP/DLNA
** Install additional components (y/n)? y
** Ready for automated image build
** Proceed (y/n)? y
** Test Internet connection
** Download helper files
** Add options to properties file
** Load properties into env
** Base OS image was saved from previous build
** Use saved image to write to USB drive (y/n)? y
** Write image to USB drive on /dev/sda
/dev/sdb
/dev/sdc
/dev/sdd
/dev/sde
dd: unrecognized operand ‘/dev/sdb’
Try 'dd --help' for more information.
** Flush cached disk writes
**
** New base OS image created
**
** Remove the USB drive and use it to boot a Raspberry Pi
** The build will automatically continue at STEP 2 after boot
**
** Save base OS img for additional builds (y/n)? dd--help
** Valid entries are y|n
** Save base OS img for additional builds (y/n)? y
I'm trying again with a freshly-FAT-formatted 32GB SD card. This time, the green light came on on reboot, but it seems to be stuck on with no flickering. Is that what is supposed to happen? How long is the writing wait time generally?

BTW, an explanation of the y/n questions would be appreciated, or maybe just the better ones?

Stuart
I have the same problem. Using RPi B+ (connected via LAN), the target micro SD card appears to have been written to, but when reinserted in the RPi both green and red lights just stay on for an hour. Can't ssh into RPi, although it appears as active on my network. When I look at the card it has become read only and cannot be formatted by SD Formattter.
Have tried about 6 times. Perhaps I'm not waiting long enough.
BTW, build recipe works OK.
Ian
 
Hi Guys

I am getting as far as shh to my Pi3 from my mac, I have a 8GB microsd card as boot but on using the auto build installer script I get not enough space 2.5GB required. Tried using the expand to 3GB from Tim's build recipe 2.2 rebooted, but still no joy.

Could koda59 please let us know how to expand the drive to accommodate the build as he kindly did for one of the others.

Thanks in advance
Rod
 
Hi Tim,

It's not working for me -- doesn't seem to be writing to the SD card after invoking mosbuild.sh. Here's the terminal output:

Code:
pi@raspberrypi:~ $ ls
mosbuild  mosbuild.sh
pi@raspberrypi:~ $ ls -al
total 40
drwxr-xr-x 3 pi   pi    4096 Dec 12 04:11 .
drwxr-xr-x 3 root root  4096 Nov 29 01:22 ..
-rw-r--r-- 1 pi   pi     220 Nov 29 01:22 .bash_logout
-rw-r--r-- 1 pi   pi    3523 Nov 29 01:22 .bashrc
drwxr-xr-x 2 root root  4096 Dec 12 04:10 mosbuild
-rwxr-xr-x 1 root root 12562 Dec  8 22:14 mosbuild.sh
-rw-r--r-- 1 pi   pi     675 Nov 29 01:22 .profile
pi@raspberrypi:~ $ ls -al mosbuild
total 1814540
drwxr-xr-x 2 root root       4096 Dec 12 04:10 .
drwxr-xr-x 3 pi   pi         4096 Dec 12 04:11 ..
-rw-r--r-- 1 root root 1858076672 Dec 12 04:10 2017-11-29-raspbian-stretch-lite.img
pi@raspberrypi:~ $ sudo chmod +x /home/pi/mosbuild.sh
pi@raspberrypi:~ $ sudo ./mosbuild.sh
****************************************************************
**
**  Moode OS Image Builder v1.0
**
**  Welcome to the automated process for creating the wonderful
**  custom Linux OS that runs moOde audio player.
**
**  You will need a Raspberry Pi running Raspbian with SSH
**  enabled, at least 2.5GB free space on the boot SDCard and
**  a spare USB or USB-SDCard drive that the new OS will be
**  written to during the build process.
**
**  Be sure to backup the SDCard used to boot your Pi
**
****************************************************************

////////////////////////////////////////////////////////////////
//
// STEP 1 - Download Raspbian Lite and create a new, base image
//
////////////////////////////////////////////////////////////////

** Check free disk space
** Do you have a backup of your boot SDCard (y/n)? y
** Unplug all USB storage devices from the Pi
** Are all USB storage devices unplugged (y/n)? y
** Plug in target USB drive for the new OS
** Is target USB drive plugged in (y/n)? y
** USB drive detected on /dev/sda
/dev/sdb
/dev/sdc
/dev/sdd
/dev/sde
** Partitions unmounted on /dev/sda
/dev/sdb
/dev/sdc
/dev/sdd
/dev/sde
** Option 1-5: use a proxy server for Internet access (y/n)? n
** Option 2-5: use a WiFi connection instead of Ethernet (y/n)? n
** Option 3-5: configure /var/www as squashfs (y/n)? y
** Option 4-5: install latest Linux Kernel (y/n)? y
** Option 5-5: Airplay, Ashuffle, LocalUI, Scrobbler, Squeezelite and UPnP/DLNA
** Install additional components (y/n)? y
** Ready for automated image build
** Proceed (y/n)? y
** Test Internet connection
** Download helper files
** Add options to properties file
** Load properties into env
** Base OS image was saved from previous build
** Use saved image to write to USB drive (y/n)? y
** Write image to USB drive on /dev/sda
/dev/sdb
/dev/sdc
/dev/sdd
/dev/sde
dd: unrecognized operand ‘/dev/sdb’
Try 'dd --help' for more information.
** Flush cached disk writes
**
** New base OS image created
**
** Remove the USB drive and use it to boot a Raspberry Pi
** The build will automatically continue at STEP 2 after boot
**
** Save base OS img for additional builds (y/n)? dd--help
** Valid entries are y|n
** Save base OS img for additional builds (y/n)? y

I'm trying again with a freshly-FAT-formatted 32GB SD card. This time, the green light came on on reboot, but it seems to be stuck on with no flickering. Is that what is supposed to happen? How long is the writing wait time generally?

BTW, an explanation of the y/n questions would be appreciated, or maybe just the better ones?

Stuart

Well the detection of USB seems not working in your setup (5 devices detected, something has failed).
Could you, please, give us the result of :
ls -la /dev/disk/by-id
just before launching mosbuild.sh and after, when you cancel/quit mosbuild.sh ?

Another point, did you have any USB devices plugged on RPI's USB before launching mosbuild ?

Regards
 
Oh, yes! This is from the shairport conf:

Code:
//////////////////////////////////////////
//  This convolution filter can be used to apply almost any correction to the audio signal, like frequency and phase correction.
//  For example you could measure (with a good microphone and a sweep-sine) the frequency response of your speakers + room,
//  and apply a correction to get a flat response curve.
//////////////////////////////////////////
//
//  convolution = "yes";                  // Activate the convolution filter.
//  convolution_ir_file = "impulse.wav";  // Impulse Response file to be convolved to the audio stream
//  convolution_gain = -4.0;              // Static gain applied to prevent clipping during the convolution process
//  convolution_max_length = 44100;       // Truncate the input file to this length in order to save CPU.

Pretty tidy, actually... The filters would go into the the "impulse.wav" and things should work. I will try this out - let's see if REW can produce files which actually work.
REW filter do not have a master gain setting. But exporting the filters impulse response as wav has many settings (mono/stereo, sample rate, bit depth)... will play around...

If yes, then in my view it would be an additional selling point for moOde, if these could be part of the UI... But let us see...

Hey guys, tried to mock around in the config file, but nothing happens. I set the convolution gain to -14db (which should be clearly noticeable), save the file and restart Airplay from the UI.

Anything else I should do? Any logs I could look at to see what is happening?

:confused:
 
Hi Guys

I am getting as far as shh to my Pi3 from my mac, I have a 8GB microsd card as boot but on using the auto build installer script I get not enough space 2.5GB required. Tried using the expand to 3GB from Tim's build recipe 2.2 rebooted, but still no joy.

Could koda59 please let us know how to expand the drive to accommodate the build as he kindly did for one of the others.

Thanks in advance
Rod

sudo raspi-config and choose expand ;)

Look here :
raspi-config - Raspberry Pi Documentation
 
Thanks for the expand space help koda59 it was simple to do and solved the not enough space problem on a reboot.

I am now at the first boot after creating the new image on another micro SD card and placing into the Pi3 to continue setup - where apparently it should automatically continue at step 2 of the install but instead all it offers me is a picalhost login prompt on the Pi3. I can ssh into the Pi3 but nothing seems to be happening. What can i do to finish the setup? I am now logged into pi@localhost.

Thanks
Rod
 
I am now at the first boot after creating the new image on another micro SD card and placing into the Pi3 to continue setup - where apparently it should automatically continue at step 2 of the install but instead all it offers me is a picalhost login prompt on the Pi3. I can ssh into the Pi3 but nothing seems to be happening. What can i do to finish the setup? I am now logged into pi@localhost.

Thanks
Rod

How long did you wait? Step 2 may take 40 mins to complete, and you should then be able to connect to moode.local on your browser.