Hey Tim,
Small curious question
if i want to add some custom cover for station added manually (no cover found), did i need to edit the SQL row entry in addition to put the img file in the right place ?
Nvm previous post. I sent u email this morning
-Tim
For all newbies, somewhat like myself.
If you didn't try to build moode before (when it was in beta), you must know that the build happens in the background, as I myself found after rebooting the pi a few times. There's no information on this on the web site or somewhenre in this forum (at least not after the official announcement for 4.0), so after the first reboot you have to wait patiently or start moslog to see what's going on. mosbrief only shows a brief info about the progress of the build, but I think this is not enough.
If I had a bit more time, I'd write an installation/build guide. Unfortunatelly I'd have some time next month.
If you didn't try to build moode before (when it was in beta), you must know that the build happens in the background, as I myself found after rebooting the pi a few times. There's no information on this on the web site or somewhenre in this forum (at least not after the official announcement for 4.0), so after the first reboot you have to wait patiently or start moslog to see what's going on. mosbrief only shows a brief info about the progress of the build, but I think this is not enough.
If I had a bit more time, I'd write an installation/build guide. Unfortunatelly I'd have some time next month.
Hi Ronnie,
Just downloaded and it looks ok to me.
-Tim
////////////////////////////////////////////////////////////////
//
// STEP 9 - Alsaequal
//
////////////////////////////////////////////////////////////////
NOTE: The amixer command below will generate the alsaequal bin file.
sudo amixer -D alsaequal > /dev/null
sudo chmod 0755 /usr/local/bin/alsaequal.bin
sudo chown mpd:audio /usr/local/bin/alsaequal.bin
sudo rm /usr/share/alsa/alsa.conf.d/equal.conf
mpc enable only 1
////////////////////////////////////////////////////////////////
//
// STEP 10 - Optionally squash /var/www
Just downloaded and it looks ok to me.
-Tim
////////////////////////////////////////////////////////////////
//
// STEP 9 - Alsaequal
//
////////////////////////////////////////////////////////////////
NOTE: The amixer command below will generate the alsaequal bin file.
sudo amixer -D alsaequal > /dev/null
sudo chmod 0755 /usr/local/bin/alsaequal.bin
sudo chown mpd:audio /usr/local/bin/alsaequal.bin
sudo rm /usr/share/alsa/alsa.conf.d/equal.conf
mpc enable only 1
////////////////////////////////////////////////////////////////
//
// STEP 10 - Optionally squash /var/www
MoOde 4.0 Install
Using the two step process described in the support section of MoOdeaudio.org was successful on the first go. As someone new to Linux I found this is the only way to go.
Have not really tested out all the features / capabilities but to this point found not bumps in the road.
Hats off to the many contributors to huge development effort. Well done!
Using the two step process described in the support section of MoOdeaudio.org was successful on the first go. As someone new to Linux I found this is the only way to go.
Have not really tested out all the features / capabilities but to this point found not bumps in the road.
Hats off to the many contributors to huge development effort. Well done!
In fact, during first part of process, you should have something like this on screen :
**
** Base OS image created on boot SDCard
Pi must be powered off then back on
The build will automatically continue at STEP 2 after boot
It can take around 1 hour to complete
Use cmds: mosbrief, moslog and moslast to monitor the process
Maybe you didn't see that
I can add one thing (if i remember well, Kent ask for something like this
) :When process building is starting after first boot ... a few sec after that, you will see the ACT LED permanently ON ... and like that after each reboot due to all building STEPS.
It will be revert back to blinking on IO activity only when building is totally finished or stopped on error.
This is just an "eye-witness" and not a way to monitor but interesting to know
Regards
Hi,
Some good news re the librespot project. It appears that some devs have revived the abandoned project and are working on fixing the volume issues and other important issues
-Tim
Something is different with the new 4.0 release: Spotify now connects to Moode at around 50% volume by default. With 4.0 Beta12 it's still 100%
Thanks for the info, I did a fresh download from "sources" on a different computer and it is, indeed, as you state.
Anyway, recopied everything and it ran OK
Sorry for the noise
Ronnie
Thanks for the info, but then again: there's no information about the fact that the process is taking place in the background. Some people (especially people who are new to this process) may think that nothing happens and try to reboot or even start all over again.In fact, during first part of process, you should have something like this on screen :
**
** Base OS image created on boot SDCard
Pi must be powered off then back on
The build will automatically continue at STEP 2 after boot
It can take around 1 hour to complete
Use cmds: mosbrief, moslog and moslast to monitor the process
Maybe you didn't see that
I can add one thing (if i remember well, Kent ask for something like this
When process building is starting after first boot ... a few sec after that, you will see the ACT LED permanently ON ... and like that after each reboot due to all building STEPS.
It will be revert back to blinking on IO activity only when building is totally finished or stopped on error.
This is just an "eye-witness" and not a way to monitor but interesting to know
Regards
Anyway... I'm running the build process at this very moment and it's already been two hours (RPi 2) and it's stuck on this line:
Code:
** Compile Libupnpp
...
...
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I./libupnpp -DDEBUG -g -Wall -pthread -I/usr/include/upnp -I/usr/include/arm-linux-gnueabihf -DDATADIR="/usr/share/libupnpp" -DCONFIGDIR="/etc" -std=c++11 -std=c++11 -g -O2 -MT libupnpp/control/avtransport.lo -MD -MP -MF libupnpp/control/.deps/avtransport.Tpo -c libupnpp/control/avtransport.cxx -fPIC -DPIC -o libupnpp/control/.libs/avtransport.oIt's like this for 40-45 minutes. Not sure what to do: leave it to run or reboot.
Have a look to running process with a ps command and see if compiler is currently eating some cpu. Don’t stop it until building is stopped in error.
Yup, same here. I'm sure I formatted the SD card, and cleared my browser cache though.
Yes there should be - unless you happened to check your router during one of the reboots.
Thank's jonner,
than i got no luck:
pi@moode:~ $ cat ./mosbuild.log | grep "^// \|^\*\* "
** Tue 30 Jan 18:12:11 UTC 2018
// STEP 2 - Direct build so no need to expand Root partition
** Change password for user pi to moodeaudio
** Download latest moOde release
** Unzip release
** Install boot/config.txt
** Reboot 1
** Tue 30 Jan 18:12:41 UTC 2018
// STEP 3A - Install core packages
** Basic optimizations
** No proxy configured
** Update Raspbian package list
** Upgrading Raspbian installed packages to latest available
** Reboot 2
** Tue 30 Jan 18:28:27 UTC 2018
// STEP 3B - Install core packages
** Install core packages
** Tue 30 Jan 18:30:13 UTC 2018
// STEP 3B - Install core packages
** Install core packages
** Error: should never arrive at case = *
** Error: should never arrive at case = *
than i got no luck:
pi@moode:~ $ cat ./mosbuild.log | grep "^// \|^\*\* "
** Tue 30 Jan 18:12:11 UTC 2018
// STEP 2 - Direct build so no need to expand Root partition
** Change password for user pi to moodeaudio
** Download latest moOde release
** Unzip release
** Install boot/config.txt
** Reboot 1
** Tue 30 Jan 18:12:41 UTC 2018
// STEP 3A - Install core packages
** Basic optimizations
** No proxy configured
** Update Raspbian package list
** Upgrading Raspbian installed packages to latest available
** Reboot 2
** Tue 30 Jan 18:28:27 UTC 2018
// STEP 3B - Install core packages
** Install core packages
** Tue 30 Jan 18:30:13 UTC 2018
// STEP 3B - Install core packages
** Install core packages
** Error: should never arrive at case = *
** Error: should never arrive at case = *
Automated build-quick howto
The automated build is great. Runs without errors and builds cleanly.
I have used it for both Pi2 and PiB
Here is my How-to. It may be of help to newcomers....
download Raspbian Stretch Lite release 2017-11-29.
Download Raspbian for Raspberry Pi
Unzip and write the image to sdcard. Etcher is very reliable for this if your os supports it...
Etcher
Use a text editor to create a file without any content and name it "ssh" (without the quotes)
Copy that file to the boot partition of Raspbian Stretch Lite that you wrote to the sdcard.
unmount/cleanly remove/eject the sdcard and insert it into your pi.
Boot the pi and log in via ssh user pi password raspberry.
run the following in order ....
Then start the automated build by running...
you will be asked some questions finishing with poweroff the pi y/n
Answer y and wait for the pi to poweroff.
Repower the pi.
The build begins. login via ssh to see it. (login changes after that first poweroff and the password is then 'moodeaudio'.)
once logged in run...
for updates on progress.
when it finishes the mosbrief command will show 'END'
The pi reboots several times so you will have to log in often and check for END or just wait an hour or two then log in to check for END.
Once the build has ended you can access MoOde from your browser.
More at....moodeaudio.org (scroll down to 'Support')
The automated build is great. Runs without errors and builds cleanly.
I have used it for both Pi2 and PiB
Here is my How-to. It may be of help to newcomers....
download Raspbian Stretch Lite release 2017-11-29.
Download Raspbian for Raspberry Pi
Unzip and write the image to sdcard. Etcher is very reliable for this if your os supports it...
Etcher
Use a text editor to create a file without any content and name it "ssh" (without the quotes)
Copy that file to the boot partition of Raspbian Stretch Lite that you wrote to the sdcard.
unmount/cleanly remove/eject the sdcard and insert it into your pi.
Boot the pi and log in via ssh user pi password raspberry.
run the following in order ....
Code:
cd /home/pi
Code:
sudo wget -q [url]http://moodeaudio.org/downloads/mos/mosbuild.sh[/url] -O /home/pi/mosbuild.sh
Code:
sudo chmod +x /home/pi/mosbuild.shThen start the automated build by running...
Code:
sudo ./mosbuild.shyou will be asked some questions finishing with poweroff the pi y/n
Answer y and wait for the pi to poweroff.
Repower the pi.
The build begins. login via ssh to see it. (login changes after that first poweroff and the password is then 'moodeaudio'.)
once logged in run...
Code:
mosbrieffor updates on progress.
when it finishes the mosbrief command will show 'END'
The pi reboots several times so you will have to log in often and check for END or just wait an hour or two then log in to check for END.
Once the build has ended you can access MoOde from your browser.
More at....moodeaudio.org (scroll down to 'Support')
Hi,
Very odd.
Couple of things to help troubleshoot.
1. Downloading the 4.0 Sources or the Mosbuild.sh script should take less than 1 min.
2. Mosbuild should display "version 2.2" in its header screen.
pi@rp3:~ $ sudo ./mosbuild.sh
****************************************************************
**
** Moode OS Image Builder v2.2
**
3. Verify the MD5 hash of 4.0 Sources download zip with what is listed at moodeaudio.org under the "download moode 4.0" button
2a957aac5a60c6c8da0aac906446ea94
-Tim