I'm trying to get a Raspberry Pi B+ and a Twisted Pear Buffalo II DAC working with Moode via I2S, and would appreciate some help.
I've got Moode up and running with USB out to another DAC, but I'm unsure how to configure Moode for I2S to the Buffalo, i.e. which I2S device to choose. I tried the two generic I2S devices, but I get no audio out and my logic analyser shows nothing on the Pi's I2S pins.
Cheers,
Jon
I've got Moode up and running with USB out to another DAC, but I'm unsure how to configure Moode for I2S to the Buffalo, i.e. which I2S device to choose. I tried the two generic I2S devices, but I get no audio out and my logic analyser shows nothing on the Pi's I2S pins.
Cheers,
Jon
Hi Jon,
From Moode Setup guide, did u perform steps 2a - 2f under I2S DEVICE?
2. AUDIO DEVICE SETUP
- USB DEVICE
a) Menu, Configure, MPD
b) leave Volume control set to "Software"
c) set Audio output to "USB audio device" then press APPLY
- I2S DEVICE
a) Menu, Configure, System
b) select appropriate I2S audio device then press SET
c) reboot
d) Menu, Configure, MPD
e) leave Volume control set to "Software"
f) verify Audio output is set to "I2S audio device" then press APPLY
-Tim
RPi3 HiFiBerry DAC WiFi problem
well not getting any help here I tried using Volumio. I was able to set up wifi and the combination of RPi3, HiFiBerry Pro DAC, WiFi, and Volumio works perfectly well. I been able to shut down and restart numerous times
So it seems there is a problem with MoOde and this combination
I would rather use MoOde because I prefer the interface
well not getting any help here I tried using Volumio. I was able to set up wifi and the combination of RPi3, HiFiBerry Pro DAC, WiFi, and Volumio works perfectly well. I been able to shut down and restart numerous times
So it seems there is a problem with MoOde and this combination
I would rather use MoOde because I prefer the interface
Hi,
Its definately not a bug in Moode software. I was able to repro the issue on 3 different virgin Raspbian releases that did not contain Moode or any other additional software. Refer to post below.
http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-415.html#post4789594
The fact that another player/OS combination and DAC+Pro work only suggests that the issue is probably due to some OS component.
I know that Hifiberry is working with the Raspberry Pi dev's to debug the issue but I'm not aware of any status in that regard.
-Tim
It's Issue #1588 in the RaspberryPi/Linux Github repo:
https://github.com/raspberrypi/linux/issues/1588
OK I certainly cannot state anything other than I am listening to RPi3/HiFiBerryProDAC/WiFi/Volumio right now and its been stable for many cycles of shut downs and restarts and over 24hrs of playing web radio and files off my NAS
I still do not understand why no one would help me configure the Pi3 with a wifi dongle so I could still use MoOde the preferred interface
I still do not understand why no one would help me configure the Pi3 with a wifi dongle so I could still use MoOde the preferred interface
Last edited:
Tim, thanks for your reply. I have tried that, but will do so again. Do you know which I2S device I should select for a TP Buffalo II DAC?
Cheers,
Jon
Hi Jon,
I don't have any experience with that board so not sure what will work.
This is a question for TP
-Tim
Tim, Fair enough - I shall ask them. Out of interest, what's the impact of selecting different I2S devices? Presumably the raspberry PI I2S pins are always the same, so is this just a means of selecting different device capabilties such as hardware volume control?
Cheers,
Jon
I have Moode on a PI Zero with a Phat Dac. It sounds wonderful. Last night I plugged a pair of headphones directly into the Phat and used the "software" volume control.
For desktop use at work, this direct connection is more then loud enough.
Does plugging headphones directly into the DAC damage anything; Is it a bad thing to do?
I ask, because I do not necessarily understand impedance.
For desktop use at work, this direct connection is more then loud enough.
Does plugging headphones directly into the DAC damage anything; Is it a bad thing to do?
I ask, because I do not necessarily understand impedance.
Thanks for that. Finally some light has been shone on what is going on with RPi3/HiFiBerryProDAC/WiFi issue and it looks software related. Nothing to do with Moode itself which is running perfectly here on RPi2/HiFiBerryProDAC/WiFiDongle.
Hi Pelliott.
From one newb to another, I have no idea how to "configure" the wifi dongle. I simply plugged mine in and it was registered and available as "wlan1". When I had the onboard wifi and the dongle on at the same time I had "wlan0" and 'wlan1" available.
However, I could still not access moode over wifi with the Hifiberry dac+pro in either case (though I did not spend much time trying to figure out the dongle route). I have since moved this system to my living room and have it plugged into my wireless router and it is working great. I'm patiently waiting for the wifi to be sorted out so that I can move it back to my workshop but in the meantime I'll enjoy the music where I can.
Graham
From one newb to another, I have no idea how to "configure" the wifi dongle. I simply plugged mine in and it was registered and available as "wlan1". When I had the onboard wifi and the dongle on at the same time I had "wlan0" and 'wlan1" available.
However, I could still not access moode over wifi with the Hifiberry dac+pro in either case (though I did not spend much time trying to figure out the dongle route). I have since moved this system to my living room and have it plugged into my wireless router and it is working great. I'm patiently waiting for the wifi to be sorted out so that I can move it back to my workshop but in the meantime I'll enjoy the music where I can.
Graham
I've done nothing special. I already had RPi2 running Kodi so it was just a matter of swapping it over with RPi3. Didn't have to re-install anything. Moode with RPi3 config worked straight away with Pi2+dongle.
Last edited:
Hi Graham,
Try the following:
1) plug in WiFi adapter
2) System config, Maintenance section, Pi3 WiFi-BT adapter OFF, SET
3) Network config, enter WiFi (wlan0) SSID and password, APPLY
4) reboot
To return to using Pi3 integrated adapter
1) System config, Maintenance section, Pi3 WiFi-BT adapter ON, SET
2) shutdown
3) unplug WiFi adapter
4) power up
-Tim
I'm experiencing strange behaviour with my NAS sources.
I configured 2 NAS sources, both are SMB/CIFS shares on my Windows 10 computer. They are indexed and all work ok. I leave the Raspberry always on, but at the end of the day I hibernate my computer. With previous versions of moode this sometimes caused problems, maybe some timer disconnected the share (a quick googling showed that this could be a common Linux problem with hibernated SMB mounts) and moode didn't play songs from these NAS sources. Not always, sometimes there were no issues for about a week. But the reboot of the Raspberry always solved this problem.
Now, since I use Moode 2.7 things are worse. I used this new version for days without issues but once Moode looses the NAS sources a reboot does not solve anything. The green checkmark appears with the NAS sources on the config screen, but the sources are not mounted, /mnt/NAS/source is an empty dir and music does not play. Only solution is to go to the sources config screen, open the source configuration and press save without changing anything. Then that source gets indexed (quite quickly) then it works. Until the next Raspberry reboot (without hibernating Windows), because after that, the source is lost again (but it appears ok in the sources config screen).
I see that NAS mounts are not in /etc/fstab, but where do they get mounted from?
Edit: I use wired ethernet with static IP
I configured 2 NAS sources, both are SMB/CIFS shares on my Windows 10 computer. They are indexed and all work ok. I leave the Raspberry always on, but at the end of the day I hibernate my computer. With previous versions of moode this sometimes caused problems, maybe some timer disconnected the share (a quick googling showed that this could be a common Linux problem with hibernated SMB mounts) and moode didn't play songs from these NAS sources. Not always, sometimes there were no issues for about a week. But the reboot of the Raspberry always solved this problem.
Now, since I use Moode 2.7 things are worse. I used this new version for days without issues but once Moode looses the NAS sources a reboot does not solve anything. The green checkmark appears with the NAS sources on the config screen, but the sources are not mounted, /mnt/NAS/source is an empty dir and music does not play. Only solution is to go to the sources config screen, open the source configuration and press save without changing anything. Then that source gets indexed (quite quickly) then it works. Until the next Raspberry reboot (without hibernating Windows), because after that, the source is lost again (but it appears ok in the sources config screen).
I see that NAS mounts are not in /etc/fstab, but where do they get mounted from?
Edit: I use wired ethernet with static IP
Last edited:
Hi,
Mounts happen on-the-fly either during Moode startup or after saving a NAS source. Look in /var/www/command/worker.php for string 'mountall' or 'source cfg' and then in /var/www/inc/playerlib.php for the actual functions.
Post back contents of Moode log when this issue occurs. The 'mountall' process that takes place during startup returns a status which is logged in moode log.
Also just type mount at cmd prompt to get a list of mounts.
Moode log is: cat /var/log/moode.log or ./mlog.sh
-Tim
Thanks for the quick reply
Code:
pi@moode:~ $ mount
/dev/sda1 on / type ext4 (rw,noatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=469536k,nr_inodes=117384,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
/dev/sdb1 on /media/USB type vfat (rw,nosuid,nodev,noexec,noatime,nodiratime,sync,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,errors=remount-ro,uhelper=udisks)
/dev/mmcblk0p2 on /media/4D32-1997 type vfat (rw,nosuid,nodev,noexec,noatime,nodiratime,sync,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,showexec,utf8,errors=remount-ro,uhelper=udisks)
/dev/sda2 on /mnt/null1 type ext4 (rw,nodev,noexec,noatime,nodiratime,data=ordered)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=94776k,mode=700,uid=1000,gid=1000)
Code:
pi@moode:~ $ ./mlog.sh
20160915 231915 worker: Startup
20160915 232006 engine-mpd: Connect
20160915 232006 engine-mpd: Session loaded
20160915 232006 openMpdSocket(): could not connect to MPD
20160915 232006 engine-mpd: Connection to mpd failed
20160915 232007 worker: Host (moode)
20160915 232007 worker: Hdwr (Pi-2B 1GB)
20160915 232007 worker: Arch (armv7l)
20160915 232007 worker: Krnl (4.4.19-v7+)
20160915 232007 worker: OS (moodeOS 1.0)
20160915 232008 worker: Rel (Moode 2.7 2016-08-28)
20160915 232008 worker: Upd (None)
20160915 232008 worker: MPD (0.19.19)
20160915 232008 worker: Session loaded
20160915 232008 worker: Debug logging (on)
20160915 232008 worker: File check...
20160915 232008 worker: File check ok
20160915 232017 worker: Auto-shuffle deactivated
20160915 232017 engine-mpd: Connect
20160915 232017 engine-mpd: Session loaded
20160915 232017 openMpdSocket(): could not connect to MPD
20160915 232017 engine-mpd: Connection to mpd failed
20160915 232017 worker: USB sources (4D32-1997)
20160915 232017 worker: MPD started
20160915 232017 worker: wlan0 does not exist
20160915 232017 worker: Audio (I2S audio device)
20160915 232017 worker: Audio (Audiophonics ES9023 DAC)
20160915 232018 worker: ALSA outputs unmuted
20160915 232018 worker: ALSA mixer name (Digital)
20160915 232018 worker: MPD volume control (disabled)
20160915 232021 engine-mpd: Connect
20160915 232021 engine-mpd: Session loaded
20160915 232022 worker: MPD output 1 ALSA default (enabled)
20160915 232022 worker: MPD output 2 ALSA crossfeed (disabled)
20160915 232022 engine-mpd: Generating enhanced metadata
20160915 232022 engine-mpd: Metadata returned to client
20160915 232022 worker: Hdwr volume controller not detected
20160915 232022 engine-mpd: Connect
20160915 232022 engine-mpd: Session loaded
20160915 232022 engine-mpd: Idle
20160915 232022 engine-mpd: Idle timeout event=(changed: mixer)
20160915 232022 engine-mpd: Generating enhanced metadata
20160915 232022 engine-mpd: Metadata returned to client
20160915 232022 worker: Volume level (0) restored
20160915 232022 worker: wlan0 address not assigned
20160915 232022 worker: eth0 exists
20160915 232022 engine-mpd: Connect
20160915 232022 engine-mpd: Session loaded
20160915 232022 engine-mpd: Idle
20160915 232022 worker: eth0 (192.168.2.14)
20160915 232022 worker: NAS sources (mountall initiated)
20160915 232022 worker: MPD consume reset to off
20160915 232022 worker: Watchdog started
20160915 232022 worker: End startup
20160915 232022 worker: ReadyThanks Tim.
I just followed your instructions and am now listening to some great blues with no wire tethering my pi to my router. The last time I had time to play with this was before you added the on/off capabilities for the on board WiFi and I was probably not blacklisting the on board WiFi properly. Your support for this player has been second to none.
Graham
I just followed your instructions and am now listening to some great blues with no wire tethering my pi to my router. The last time I had time to play with this was before you added the on/off capabilities for the on board WiFi and I was probably not blacklisting the on board WiFi properly. Your support for this player has been second to none.
Graham