Another thing is that, whatever the problems with the USB mount, the player probably shouldn't mount an unexistant NAS instead, so this could indicate a bug.
You should change the name of the host to "moode" instead of "raspberrypi" which is the Raspbian default.
Hi,
Yes I understood that. That's what the following commands do, right?
Code:
pi @ raspberrypi: ~ $ echo "pi: moodeaudio" | sudo chpasswd
pi @ raspberrypi: ~ $ sudo sed -i "s / raspberrypi / moode /" / etc / hostname
pi @ raspberrypi: ~ $ sudo sed -i "s / raspberrypi / moode /" / etc / hostsThanks
The { -C 5 } is what I use on a pi running Jessie-Lite with just Squeezelite and Spotify-Connect and a dac-hat.
But I don't think it is really needed, as by the time I have stopped one instance and then navigated to the other instance, more than 5 secs have passed 🙂
Hi, my name is Richard, I am new here.
Joined DiyAudio to take part in the discussion about moode. Tim has already via mail been really helpful, but I thought I shouldn't waste more of his time with my noob questions.
Anyway, I have built Beta 10 using the build recipe encountering the same "host cannot be resolved" issues as above. However, I did not encounter Kernel panics but the whole installation went on fine.
Maybe the two problems stem from different sources? If helpful, I could attach my whole install log to look for differences.
Regarding host names, I was also unable to ssh into my RPi via pi@raspberry or later pi@moode. Only after adding ".local" it worked.
I have my own question about the DSP part in Moode. This seemed a big plus of moode compared to e.g. volumio for me.
However, I didn't get it to work as I needed.
Firstly, it seems to not touch audio which is streamed via airplay. Is there a way to apply DSP in this case?
Secondly, testing with some internet radio, the equalizer seemed to do something - but not what I expected... I design the filters using REW, and applying these filters audio just sounds completely wrong (hardly any bass at all instead of just curing my two room modes). Could it be that there are different definitions for example for the Q? Could you point me to some help with this?
Overall, I really like moOde! Thanks a lot to those who make it possible!!
However, I didn't get it to work as I needed.
Firstly, it seems to not touch audio which is streamed via airplay. Is there a way to apply DSP in this case?
Secondly, testing with some internet radio, the equalizer seemed to do something - but not what I expected... I design the filters using REW, and applying these filters audio just sounds completely wrong (hardly any bass at all instead of just curing my two room modes). Could it be that there are different definitions for example for the Q? Could you point me to some help with this?
Overall, I really like moOde! Thanks a lot to those who make it possible!!
Right, didn't notice that you did change the name already, sorry.
While a reboot wouldn't hurt, I unzipped the distribution package right after changing the name, without errors. In fact, I rebooted strictly according to the recipe.
While a reboot wouldn't hurt, I unzipped the distribution package right after changing the name, without errors. In fact, I rebooted strictly according to the recipe.
For ssh, for example just: "ssh pi@moode.local"
Don't know if this can help also in the build process / recipe.
@flambeur and @wilb
This is a pesky issue regarding the services on your local network and not moOde or Raspberry Pis specifically. Your local name server (running on your router, perhaps) isn't resolving the bare host name "raspberrypi" or "moode" to an IP address when the computer you are using queries it. Adding the .local top-level domain to the host name causes your computer to bypass DNS (Domain Name Service) in favor of mDNS (multicast DNS) to resolve the host name. Quoting from the Wikipedia article: "By default, mDNS only and exclusively resolves host names ending with the .local top-level domain (TLD)."
mDNS is a zero-configuration service which does not use a local name server but can peacefully coexist with one. It's implemented, for example, in Apple's Bonjour and FOSS avahi (used in moOde and most Linux systems), Windows, and lots of A/V gear. Sadly, it is available in Android but not used in the resolver so neither "moode" nor "moode.local" trick works in a web browser on Android.
This is just background. I'm still noodling about @wilb's original problem.
Regards,
Kent
In my memory there are get me the same problem of "Kernel Panic" right after:
Code:
pi@raspberrypi:~ $ echo "pi:moodeaudio" | sudo chpasswd
pi@raspberrypi:~ $ sudo sed -i "s/raspberrypi/moode/" /etc/hostname
pi@raspberrypi:~ $ sudo sed -i "s/raspberrypi/moode/" /etc/hosts
pi@raspberrypi:~ $ sudo rebootWhen moode 4 with all new features will reach the level of stability we have with moode 3.8.4, it will be a fantastic software.
Remy
@mario74m
I haven't examined the part of moOde's codebase which deals with sources, but I suspect this Browse-panel display of an empty NAS folder is an artifact of moOde using a pre-defined subdirectory /mnt/NAS in which to mount NAS'es it knows about. That moode.log entry: "Mountall initiated" means that while it was starting up, moOde set off a process to mount NAS'es if it has 'em, so to speak. It doesn't mean moOde has mounted a nonexistent NAS.
I still find the lowercase 'nas' curious. Unlike '/mnt/NAS', a quick search of the moOde codebase doesn't turn up any instances of '/mnt/nas' [1]. Shooting in the dark, I've tried creating the subdirectory /mnt/nas on a working r40b11 system. No additional folder appears after updating the MPD database. Creating a subdirectory /media/nas and updating, on the other hand, causes a new, empty "nas" folder to show up in the USB directory, as expected.
@rtaylor76's question about your USB drive is a good one. If you haven't reformatted it yet, how about showing the output of "sudo fdisk -l /dev/sda" (or whatever the correct drive is). Maybe something about it is confusing moODe.
Also, have you tried another USB drive as a test? I keep on hand an old thumbdrive with a few tracks on it for just such testing purposes.
Regards,
Kent
[1] there's a ton of hits on 'nas' but AFAICT they are all in comments or labels. Maybe someone else will see something I don't.
Hi,
NAS mount only happens if a NAS config is created via the Sources screen.
Maybe the symlinks are messed up. Unplug all USB drives from the Pi then run the cmds below and you should get same results as mine.
pi@moode:~ $ ls -l /var/lib/mpd/music
total 12
lrwxrwxrwx 1 root root 8 Dec 4 23:39 NAS -> /mnt/NAS
drwxrwxrwx 2 root root 12288 Dec 4 23:39 RADIO
lrwxrwxrwx 1 root root 11 Dec 4 23:39 SDCARD -> /mnt/SDCARD
lrwxrwxrwx 1 root root 6 Dec 4 23:39 USB -> /media
pi@moode:~ $ ls -l /mnt
total 12
drwxr-xr-x 2 root root 4096 Dec 4 23:39 NAS
drwxr-xr-x 3 root root 4096 Dec 4 23:39 SDCARD
drwxr-xr-x 2 root root 4096 Dec 4 23:39 UPNP
pi@moode:~ $
USB drives are auto-mounted by their disk label to /media directory so this should be empty if no USB drives plugged in
pi@moode:~ $ ls -l /media
total 0
You can also check the Source sql table to make sure its empty, since you mentioned there are no NAS configs.
pi@moode:~ $ sqlite3 /var/local/www/db/moode-sqlite3.db "select * from cfg_source"
pi@moode:~ $
If there were actually a NAS config the moode log would print an entry indicating whether the NAS mount existed
pi@rp3:~ $ cat /var/log/moode.log | grep NAS
20171204 200525 worker: NAS sources (mountall initiated)
-Tim
HDMI output is good, but it keeps gone after 10 min.
Dear All,
just joined this wonderful community from South Korea, to make my own network player with screen (like kiosk).
Since I started following the kind build recipe yesterday, I finally got sound from my USB-DAC, and now-playing screen on my old HDMI monitor (actually it's DVI with 1680*1050 though)
However, this wonderful now-playing screen keeps disappearing every 10 minutes if I cut connections with keyboard / mouse. Although I spent all day to resolve this, trying many things, it always go to blank. I don't know which one makes like this because i am a kind of beginner 🙂
so, Can anybody help me?
ps) picture attached my local UI screen
ps) Here are my settings:
1. /boot/config.txt
disable_splash=1
disable_touchscreen=1
hdmi_force_hotplug=1
hdmi_drive=1
hdmi_group=2
hdmo_mode=57
#dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=audio=on
#dtoverlay=pi3-disable-wifi
#dtoverlay=pi3-disable-bt
avoid_warnings=1
2. /opt/start-gui (which is newly composed)
pi@moode:~ $ cat /opt/start-gui
#!/bin/bash
SCREENSIZE="$(fbset -s | awk '$1 == "geometry" { print $2","$3 }')"
/usr/bin/xinit /usr/bin/chromium-browser --kiosk --touch-events --disable-touch-drag-drop --disable-overlay-scrollbar \
--enable-touchview --enable-pinch --window-size=$SCREENSIZE --start-fullscreen --window-position=0,0 \
--disable-session-crashed-bubble --disable-infobars --no-first-run --app=http://localhost/ -- -nocursor
3. /home/pi/.xinitrc
# turn off display power management
xset -dpms &
# turn on screensaver (default = 10 mins)
xset s off &
# disabling blank the video device
xset s noblank &
# launch chrome browser
SCREENSIZE="$(fbset -s | awk '$1 == "geometry" { print $2","$3 }')"
chromium-browser --kiosk --touch-events --disable-touch-drag-drop --disable-overlay-scrollbar \
--enable-touchview --enable-pinch --window-size=$SCREENSIZE --window-position=0,0 \
-- start-fullscreen --disable-session-crashed-bubble --disable-infobars --no-first-run --app=http://localhost/
Dear All,
just joined this wonderful community from South Korea, to make my own network player with screen (like kiosk).
Since I started following the kind build recipe yesterday, I finally got sound from my USB-DAC, and now-playing screen on my old HDMI monitor (actually it's DVI with 1680*1050 though)
However, this wonderful now-playing screen keeps disappearing every 10 minutes if I cut connections with keyboard / mouse. Although I spent all day to resolve this, trying many things, it always go to blank. I don't know which one makes like this because i am a kind of beginner 🙂
so, Can anybody help me?
ps) picture attached my local UI screen
ps) Here are my settings:
1. /boot/config.txt
disable_splash=1
disable_touchscreen=1
hdmi_force_hotplug=1
hdmi_drive=1
hdmi_group=2
hdmo_mode=57
#dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=audio=on
#dtoverlay=pi3-disable-wifi
#dtoverlay=pi3-disable-bt
avoid_warnings=1
2. /opt/start-gui (which is newly composed)
pi@moode:~ $ cat /opt/start-gui
#!/bin/bash
SCREENSIZE="$(fbset -s | awk '$1 == "geometry" { print $2","$3 }')"
/usr/bin/xinit /usr/bin/chromium-browser --kiosk --touch-events --disable-touch-drag-drop --disable-overlay-scrollbar \
--enable-touchview --enable-pinch --window-size=$SCREENSIZE --start-fullscreen --window-position=0,0 \
--disable-session-crashed-bubble --disable-infobars --no-first-run --app=http://localhost/ -- -nocursor
3. /home/pi/.xinitrc
# turn off display power management
xset -dpms &
# turn on screensaver (default = 10 mins)
xset s off &
# disabling blank the video device
xset s noblank &
# launch chrome browser
SCREENSIZE="$(fbset -s | awk '$1 == "geometry" { print $2","$3 }')"
chromium-browser --kiosk --touch-events --disable-touch-drag-drop --disable-overlay-scrollbar \
--enable-touchview --enable-pinch --window-size=$SCREENSIZE --window-position=0,0 \
-- start-fullscreen --disable-session-crashed-bubble --disable-infobars --no-first-run --app=http://localhost/
Attachments
![20171206_003429[1].jpg](/community/data/attachments/597/597662-491bdc6a5329c7d139dffe1e591735d6.jpg?hash=SRvcalMpx9)
Hi,
There is a Screen blank setting on System config. Did you try that?
If not then undo all your custom configs first so there is no chance of interferrence.
-Tim
Hi, Tim.
Can I infer from this that the mountall process is triggered by content in the cfg_source table?
Regards,
Kent
Hi Tim, thx for quick reply.
How can I approach to "System config" ?? Can you tell me the location of file if exists?
How can I approach to "System config" ?? Can you tell me the location of file if exists?
Hi Kent,
Yes, thats exactly the case. If there are rows in cfg_source (each row represents a NAS config) they are all mounted during Worker startup. moOde does not use /etc/fstab.
-Tim
Yes, thats exactly the case. If there are rows in cfg_source (each row represents a NAS config) they are all mounted during Worker startup. moOde does not use /etc/fstab.
-Tim
Hi,
Is the System config screen in moOde. Its same screen where you turn on the Local UI feature.
Menu, Configure, System
-Tim