@Tim
Nice!
Looks like the 'official' RPi touchscreen.
If so I have one too.
Willing test out if needed. 🙂
Regards,
Daniel
I am not getting my third level folders indexed on moode by mpd, which are by mpd on my pc. Do I need to set it mpd.conf, or should it be working. I was unable to find the answer by searching and thought I would ask before I started a trial and error process.. 🙂
thanks all,
john
thanks all,
john
Last edited:
Thanks, I will give it a try, both with Lumin on iPad and Kazoo on Mac...
Also, always learning something... what is ohradio (I kinda guess but but could not find much googling...)
Last edited:
Ohradio is the ability to play Radio through the control point.
If you are using Kazoo there should be a radio option , in there should be a couple of radio stations that are already defined in Moode, this is not the list in the web front end though.
What you are doing is switching between sources.
I think Kazoo does this automatically, not sure about lumin. On android you must use BubbleDS and change source in the menu when you switch between play lists and Radio.
What I mean is 'select' Radio through the control point, its Moode that plays the Radio stream the control point does not proxy
So there's this deal at Best Buy where you can get 6 months of Tidal HiFi for free with purchase of a select group of cds (bestbuy link) so in spite of seldom using streaming services when I've had them I went ahead and ordered something for $2.
I installed the missing (because I'd previously missed the steps) upnp stuff and downloaded the recommended Linn Kazoo and Lumin apps. These worked ok and if you enabled the dlna server on moode you could control playback with them, though I like the web interface better 😉. Unfortunately no Tidal. After a bit of flailing around looking at various configurations I broke down and checked the logs and syslog showed an error reading /etc/upmpdcli.conf. A peek in /etc showed this set to 600 rather than 644, a quick sudo chmod 644 /etc/upmpdcli.conf and a reboot (just to be on the safe side, plus Tim likes them so much they must be doing good things) and we're in business. This is much more likely a result of the piecemeal way I installed beta9 but if you find yourself in a similar situation you might want to check that file for the rw permissions.
I installed the missing (because I'd previously missed the steps) upnp stuff and downloaded the recommended Linn Kazoo and Lumin apps. These worked ok and if you enabled the dlna server on moode you could control playback with them, though I like the web interface better 😉. Unfortunately no Tidal. After a bit of flailing around looking at various configurations I broke down and checked the logs and syslog showed an error reading /etc/upmpdcli.conf. A peek in /etc showed this set to 600 rather than 644, a quick sudo chmod 644 /etc/upmpdcli.conf and a reboot (just to be on the safe side, plus Tim likes them so much they must be doing good things) and we're in business. This is much more likely a result of the piecemeal way I installed beta9 but if you find yourself in a similar situation you might want to check that file for the rw permissions.
Yes I think this could be due to the change of distribution. I think that the make install command adjusts the permissions to 600 on the conf file to to protect your credentials. The owner should be the upmdcli user, I am still on Beta 5 so I cannot check, can you confirm the owners of the conf file?
I change the permissions to 644 but I am generally messing about all the time with compiling and it hadn't dawned on me that this would matter in the new FOSS model.
@Tim sorry didn't think about this as the early Beta's had correct permissions.
It was root:root, changing it to upmpdcli:upmpdcli and reverting permissions to 600 didn't seem to work. Back to 644 and it's up again.
Pirate Radio and MoOde !!!
Not very audiophile but who knows ? Maybe someone will find it usefull.
I worked on this for a friend's young boy 😀
For sound, no problem at all ... Moode beta 9, choose Pimoroi pHAT DAC ... and so on.
After testing sound and everything looks fine, we can go for pivumeter.
And it is a bit more complex 😉
So first, you must have pivumeter library installed, for that :
Pre-requisite :
build-essential autoconf automake libtool libasound2-dev libfftw3-dev wiringpi
It looks like we only need to get libfftw3-dev (all others package are already in Moode distrib).
So :
sudo apt-get install libfftw3-dev
After pre-requisite OK :
cd ~
git clone [special=https://github.com/pimoroni/pivumeter]%[/special]
cd pivumeter
aclocal && libtoolize
autoconf && automake --add-missing
./configure && make
sudo make install
At this step, libpivumeter is installed in /usr/local/lib
then add mpd to gpio group :
sudo usermod -a -G gpio mpd
Then
edit mpd.conf and find audio output with "alsa" ...
look for hardware device usually "hw:0,0" (memorize it) and replace it with "softvolume"
create an /etc/asound.conf (where you must set hw with the one you memorized), it must looks like this one :
pcm.!default {
type plug
slave.pcm "softvol"
}
ctl.!default {
type hw
card 0
}
pcm.softvolume {
type plug
slave.pcm "softvol"
}
pcm.softvol {
type softvol
slave {
pcm "pivumeter"
}
control {
name "SoftMaster"
card 0
device 0
}
max_dB 0.0
min_dB -50.0
resolution 100
}
pcm_scope.pivumeter {
type pivumeter
decay_ms 500
peak_ms 400
brightness 128
output_device blinkt
}
pcm_scope_type.pivumeter {
lib /usr/local/lib/libpivumeter.so
}
pcm.pivumeter {
type meter
slave.pcm "hw:0,0"
scopes.0 pivumeter
}
pcm.dsp0 pivumeter
That's not all to have pivumeter working ... mpd must be able to access gpio
So adapt the rights to access gpiomem :
sudo vi /etc/udev/rules.d/99-com.rules
You have to change theses lines like this (changing to 777)
SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0777"
SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
chown -R root:gpio /sys/class/gpio && chmod -R 777 /sys/class/gpio;\
chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 777 /sys/devices/virtual/gpio;\
chown -R root:gpio /sys$devpath && chmod -R 777 /sys$devpath\
'"
This is not very clean but i wasn't able to set WIRINGPI_GPIOMEM=1 and pass it to mpd (not so easy with systemd ... even with PassEnvironment directive) but it works and look better than running mpd under root.
Boy is Happy 😀 😀
Not very audiophile but who knows ? Maybe someone will find it usefull.
I worked on this for a friend's young boy 😀
For sound, no problem at all ... Moode beta 9, choose Pimoroi pHAT DAC ... and so on.
After testing sound and everything looks fine, we can go for pivumeter.
And it is a bit more complex 😉
So first, you must have pivumeter library installed, for that :
Pre-requisite :
build-essential autoconf automake libtool libasound2-dev libfftw3-dev wiringpi
It looks like we only need to get libfftw3-dev (all others package are already in Moode distrib).
So :
sudo apt-get install libfftw3-dev
After pre-requisite OK :
cd ~
git clone [special=https://github.com/pimoroni/pivumeter]%[/special]
cd pivumeter
aclocal && libtoolize
autoconf && automake --add-missing
./configure && make
sudo make install
At this step, libpivumeter is installed in /usr/local/lib
then add mpd to gpio group :
sudo usermod -a -G gpio mpd
Then
edit mpd.conf and find audio output with "alsa" ...
look for hardware device usually "hw:0,0" (memorize it) and replace it with "softvolume"
create an /etc/asound.conf (where you must set hw with the one you memorized), it must looks like this one :
pcm.!default {
type plug
slave.pcm "softvol"
}
ctl.!default {
type hw
card 0
}
pcm.softvolume {
type plug
slave.pcm "softvol"
}
pcm.softvol {
type softvol
slave {
pcm "pivumeter"
}
control {
name "SoftMaster"
card 0
device 0
}
max_dB 0.0
min_dB -50.0
resolution 100
}
pcm_scope.pivumeter {
type pivumeter
decay_ms 500
peak_ms 400
brightness 128
output_device blinkt
}
pcm_scope_type.pivumeter {
lib /usr/local/lib/libpivumeter.so
}
pcm.pivumeter {
type meter
slave.pcm "hw:0,0"
scopes.0 pivumeter
}
pcm.dsp0 pivumeter
That's not all to have pivumeter working ... mpd must be able to access gpio
So adapt the rights to access gpiomem :
sudo vi /etc/udev/rules.d/99-com.rules
You have to change theses lines like this (changing to 777)
SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0777"
SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
chown -R root:gpio /sys/class/gpio && chmod -R 777 /sys/class/gpio;\
chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 777 /sys/devices/virtual/gpio;\
chown -R root:gpio /sys$devpath && chmod -R 777 /sys$devpath\
'"
This is not very clean but i wasn't able to set WIRINGPI_GPIOMEM=1 and pass it to mpd (not so easy with systemd ... even with PassEnvironment directive) but it works and look better than running mpd under root.
Boy is Happy 😀 😀
Last edited:
A tip of the hat to Gordon🙂
I'm still noodling about the two old 7-inch Android Tablets I have sitting in a drawer. Of course I can use them in the normal way via WiFi as a moOde GUI but I'd love to be able to use one as a USB-connected display. Has anyone come across a Debian-Linux equivalent to TwoMonUSB or Splashtop Wired XDisplay? Both of these are available only for Windows/Mac hosts. The beta Splashtop Streamer for Linux (at a glance, only for Ubuntu) uses WiFi.
Regards,
Kent
PS - for those who aren't following the DietPi-moOde effort closely, I believe I may have discovered the reason WiFi isn't working in DietPi V158 (Jessie and Stretch). Was running a copy via WiFi last night. Posted an issue on github. No time to test with the special moOde install until after Thanksgiving but if I'm right this is a nice step forward.
I am using Moode 3.84 and tried today to get Spotify working, by doing
curl -sL https://dtcooper.github.io/raspotify/install.sh | sh
The script seemed to run correctly and I do see a new entry in my list of devices in the Spotify application on my Mac. However, when I select the Moode entry and hit play, it stops immediately without playing. Doing tail /var/log/daemon.log shows:
Nov 22 13:07:25 iqaudio librespot[9361]: WARN:mdns::fsm: error sending packet Error { repr: Os { code: 99, message: "Cannot assign requested address" } }
Does anyone know how to fix this? I'll be grateful for any assistance!
curl -sL https://dtcooper.github.io/raspotify/install.sh | sh
The script seemed to run correctly and I do see a new entry in my list of devices in the Spotify application on my Mac. However, when I select the Moode entry and hit play, it stops immediately without playing. Doing tail /var/log/daemon.log shows:
Nov 22 13:07:25 iqaudio librespot[9361]: WARN:mdns::fsm: error sending packet Error { repr: Os { code: 99, message: "Cannot assign requested address" } }
Does anyone know how to fix this? I'll be grateful for any assistance!
Hi
I just bought a new western digital 1tb ssd drive to replace in my moode audio an old hard disk that was formated exfat. With the new ssd drive should i change the file system? does ntfs work well with moode? does ntfs have any advantage over exfat when used with moode?
Remy
I just bought a new western digital 1tb ssd drive to replace in my moode audio an old hard disk that was formated exfat. With the new ssd drive should i change the file system? does ntfs work well with moode? does ntfs have any advantage over exfat when used with moode?
Remy
It doesn’t really matter.
FAT works well because you can transfer data between computer types, ntfs works for a PC environment and Moode.
NTFS is more reliable, as a file system.
FAT works well because you can transfer data between computer types, ntfs works for a PC environment and Moode.
NTFS is more reliable, as a file system.
Running MoOde 4.9 Beta for the first time. As someone with SNHL in one having the EQ to compensate is fantastic!!! Have not been able to get BT to work. In Bluetooth Config screen I selected intialize and click on RUN. There was no indication on the screen that any action was taken. Have tried selecting scan for devices for grins. Again no apparent action was obeserved or ability to pair.
My system ino screenshot attached. Any sugestions would be appreciated.
My system ino screenshot attached. Any sugestions would be appreciated.
Attachments
Hi Tim, now you have had it a few days, how are you enjoying the touchscreen?
I have been using Moode with a touchscreen for sometime and really like having the screen where I can control it without grabbing a phone or tablet.
I built my player using a SmartPi Touch case in a similar style to this one on the Audiophonics website, however I used an IQAudio Dac + I already had and didn't bother with an on / off button as I always leave it on.
RaspTouch LTE I-Sabre V2 Back side - Streamer touch Raspberry Pi & DAC ES90023 - Audiophonics
I am glad the local display option is becoming an official Moode feature.
