Correct, never hand modify the config files.
What issue are u having and what model is your DAC?
-Tim
Not true, moodes volume control is still acticve both with shairport and squeeze (hardware volume control via mpd settings with piano 2.1 dac)
Hello,
i'm using a fresh 4.0 moode build,
it worked fine but since 2 or 3 days i can't access any config page - for example "configure - sources" won't load.. so i cannot configure :/
Any way to reset the web server config files or something ?
i'm using a Rpi2 with a dac° pro
GREAT JOB btw !!!
i'm using a fresh 4.0 moode build,
it worked fine but since 2 or 3 days i can't access any config page - for example "configure - sources" won't load.. so i cannot configure :/
Any way to reset the web server config files or something ?
i'm using a Rpi2 with a dac° pro
GREAT JOB btw !!!
Thank you, Tim!
That is from the host side, am I right?
Could it be done from the raspberry itself, by the small application/script I planned to make?
Which intetface would be the most suitable?
Regards, Vlad.
Last edited:
Thank you, Tim!
That is from the host side, am I right?
Could it be done from the raspberry itself, by the small application I planned to make?
Which intetface would be the most suitable?
Regards, Vlad.
@Onvinyl Yes its true. The renderers control volume separately from MPD. If you also choose to adjust MPD volume then you are using two volume controls.
Airplay, when its session ends will restore moOde volume level but remain ON.
Squeezelite will do same but only when its turned OFF. This is because it does not provide session based events like Airplay.
Airplay, when its session ends will restore moOde volume level but remain ON.
Squeezelite will do same but only when its turned OFF. This is because it does not provide session based events like Airplay.
Yes the Web API would be used from host. If you are implementing directly on Pi then
mpc play, pause, next, previous
/var/www/vol.sh ...
-Tim
With respect Tim that just isn’t good advice. For example the default in the config file is a bit rate of 160kbs. I always alter it to 320kbs. The config file is there to be modified! This is Raspotify we are talking about, nothing else.
Well sure, if u install something thats not included in moOde then of course altering the configs is usually necessary. I was referring to the configs that are managed by moOde.
Btw, moOde doesn't include Spotify Connect due to the 100% initial volume issue, but it looks like some devs have begun to work on librespot again so hopefully this will be fixed.
-Tim
Tried multiple times still failing
Tried atleast 3 times in two different cards...am i missing something?
pi@moode:// $ mosbrief
// STEP 2 - Direct build so no need to expand Root partition
// STEP 3A - Install core packages
// STEP 3B - Install core packages
// STEP 4 - Install enhanced networking
** Compile bluez-alsa
// STEP 5 - Install Rotary encoder driver
** Compile WiringPi
** Compile rotary encoder driver
// STEP 6 - Compile and install MPD
// STEP 7 - Create moOde runtime environment
// STEP 8 - Install moOde sources and configs
// STEP 9 - Alsaequal
** STEP 10 - Squashfs option not selected
// STEP 11 - Optionally, install updated Linux Kernel
// STEP 12 - Launch and configure moOde!
// STEP 13 - Final prep for image
// COMPONENT 1 - MiniDLNA
// COMPONENT 2 - Auto-shuffle
// COMPONENT 3 - MPD Audio Scrobbler
// COMPONENT 4 - Shairport-sync
// COMPONENT 5 - Squeezelite
// COMPONENT 6 - Upmpdcli
** Compile Libupnp jfd5
** Compile Libupnpp
** Compile Upmpdcli
** Compile Upexplorer
// COMPONENT 7 - Optionally install gmusicapi
// COMPONENT 8 - Local UI display
** Error: install failed
** Error: image build exited
** Error: reboot to resume the build
Tried atleast 3 times in two different cards...am i missing something?
pi@moode:// $ mosbrief
// STEP 2 - Direct build so no need to expand Root partition
// STEP 3A - Install core packages
// STEP 3B - Install core packages
// STEP 4 - Install enhanced networking
** Compile bluez-alsa
// STEP 5 - Install Rotary encoder driver
** Compile WiringPi
** Compile rotary encoder driver
// STEP 6 - Compile and install MPD
// STEP 7 - Create moOde runtime environment
// STEP 8 - Install moOde sources and configs
// STEP 9 - Alsaequal
** STEP 10 - Squashfs option not selected
// STEP 11 - Optionally, install updated Linux Kernel
// STEP 12 - Launch and configure moOde!
// STEP 13 - Final prep for image
// COMPONENT 1 - MiniDLNA
// COMPONENT 2 - Auto-shuffle
// COMPONENT 3 - MPD Audio Scrobbler
// COMPONENT 4 - Shairport-sync
// COMPONENT 5 - Squeezelite
// COMPONENT 6 - Upmpdcli
** Compile Libupnp jfd5
** Compile Libupnpp
** Compile Upmpdcli
** Compile Upexplorer
// COMPONENT 7 - Optionally install gmusicapi
// COMPONENT 8 - Local UI display
** Error: install failed
** Error: image build exited
** Error: reboot to resume the build
Ty for quick answer. I did the same steps in morning. I also started from rapberry p i lite build and then went to get your ite and idd wget.
Still same error. Wil try again
V
Finally I was able to get Moode 4.0 installed.I tried 3X yesterday and it bombed at step 11. After reading Time;s post I was able to get it done earlier today. Thanks so much to Jrocker and all the other people who worked on this making the scripts, etc.
I use Ms Windows mostly to achieve this , not my Mac which I had used my for system until I learned about the PI and Moode Audio. The mac is used for headphone listening and for watching movies. The command to make the SD card bootable: echo "" > /Volumes/boot/ssh, Can that be used in a windows SSH client?
I use Ms Windows mostly to achieve this , not my Mac which I had used my for system until I learned about the PI and Moode Audio. The mac is used for headphone listening and for watching movies. The command to make the SD card bootable: echo "" > /Volumes/boot/ssh, Can that be used in a windows SSH client?
Tim, there is now a 4.9.80 which is meant to fix the kernel bug that was causing my and at least one other person on this forum Rpi3 to crash on boot. Can you add the hash for 4.9.80 instead of 4.9.79 which contained the bug.
again:
// STEP 2 - Direct build so no need to expand Root partition
// STEP 3A - Install core packages
// STEP 3B - Install core packages
// STEP 4 - Install enhanced networking
** Compile bluez-alsa
// STEP 5 - Install Rotary encoder driver
** Compile WiringPi
** Compile rotary encoder driver
// STEP 6 - Compile and install MPD
// STEP 7 - Create moOde runtime environment
// STEP 8 - Install moOde sources and configs
// STEP 9 - Alsaequal
** STEP 10 - Squashfs option not selected
// STEP 11 - Optionally, install updated Linux Kernel
tar: Error is not recoverable: exiting now
** Error: rpi-update failed
** Error: image build exited
** Error: reboot to resume the build
Unable to use the graphic equalizer. Doesn't seem to be an option to turn on, off is only option.
hi Tim and all,
on the BROWSE screen, there is no more line separator between artists(folders)
is it on purpose?
checked with FF and Chrome
Hiro
on the BROWSE screen, there is no more line separator between artists(folders)
is it on purpose?
checked with FF and Chrome
Hiro