Hi everyone! Maybe my question is right on time after the above posts about USB/SD/NAS sources. I'm using NAS as a source and everything is perfect with 16bit/44.1kHz FLACs. When i try to play 24bit/192kHz FLACs though i have frequent pauses in the playback for buffering. If i use the SD card as a source, everything is ok. I tried different settings in Moode, but without success. Any suggestions?
Thanks!
Thanks!
Hi,
Symptom suggests a network issue. Run a 30 sec ping test from Pi to NAS and then examine the ping stats for packet loss, long round trip times, dropped packets, etc.
-Tim
I'am using two raspberry's. One with a hifiberry dac pro, and one with a audiphonics es9023. They are connected to a power amplifier whitout volume control. I'am using
jriver to stream audio to moode, and use the volumecontrol of Jriver. With the hifiberry i can set the alsa volume to 60% so when something goes wrong in Jriver there is no problem. But with the audophonics i can't use the alsa volume. So when something goes wrong in jriver, i got the full output to the poweramp. Why is alsa not working with the audiophonics?
jriver to stream audio to moode, and use the volumecontrol of Jriver. With the hifiberry i can set the alsa volume to 60% so when something goes wrong in Jriver there is no problem. But with the audophonics i can't use the alsa volume. So when something goes wrong in jriver, i got the full output to the poweramp. Why is alsa not working with the audiophonics?
61 packets transmitted, 61 received, 0% packet loss, time 60019ms
rtt min/avg/max/mdev = 0.316/0.348/0.391/0.027 ms
I don't have another wired Pc on the network so i can compare the results. Maybe the problem is in the NAS, it's a NFS server running on Ubuntu. It was a fast setup and i didn't make any adjustments for performance. I don't know exactly how i works, but i noticed a burst of full speed data to Pi when it stops playing and almost no activity during playback.
Hi,
ES9023 does not have an on-chip hardware volume controller and thus there is no ALSA (hardware) volume.
The lack of hardware volume in ES9023 has been addressed in certain implementations for example the Objective DAC (ODAC) which uses the Tenor TE7022 USB receiver chip that provides a hardware volume controller.
I don't know of any ES9023 based DAC board for Raspberry Pi that provides hardware volume.
Btw, what are u using on Moode to receive the streams sent by Jriver?
-Tim
Hi,
Ping stats look normal. Thats similar to what I see for an Ethernet connection on my own network.
-Tim
uPnP not cataloguing
Hi all,
I've just installed the latest version of Moode. My mp3 library is loaded in Moode (it's on a USB drive connected to the Pi). I've enabled the uPnP server but it's not cataloguing my audio.
In the last Moode version you could see the catalogue being built when enabling uPnp and then the songs were available to select on my Roberts 83i radio.
Is there something that needs to be done on the latest version of Moode or are there any instructions out there. Is there some way I can debug what's going on?
Much appreciated.
Rob
Hi all,
I've just installed the latest version of Moode. My mp3 library is loaded in Moode (it's on a USB drive connected to the Pi). I've enabled the uPnP server but it's not cataloguing my audio.
In the last Moode version you could see the catalogue being built when enabling uPnp and then the songs were available to select on my Roberts 83i radio.
Is there something that needs to be done on the latest version of Moode or are there any instructions out there. Is there some way I can debug what's going on?
Much appreciated.
Rob
I have one of these > HiFimeDIY UX1 Sabre USB DAC+SPDIF/USB converter (which has the almost unique ability to take an optical SPDIF input and convert to USB audio)
It has a hardware volume control built in.
I use a different DAC for Moode audio but I have this piggy backed with a giant elastic band (Franken-DAC!) to a USB hub; back fed by a USB power bank and the usual Apple lightning camera connection kit straight to my iPhone with a modest pair of sennheiser headphone adequately powered straight from the ES9023 's 3.5mm socket. There's another 3.5mm output that is buffered through an amplifier, I personally find the direct connection loud enough.
The volume knob on this digitally alters the iPhones "AirPlay" volume, in the same way the phones volume buttons would.
One drawback is that it's powered throught the single USB port so you do need a powered hub to get it to work direct from the Lightning port due to its current draw.
I've never tested it with Moode but my other HIFIMEDIY DAC >> HiFimeDIY Sabre USB DAC 2 (external PSU) Asynchronous works fine with Moode via asynchronous USB and outputs a rich tone over coax In addition to line level and headphone outputs. The volume control is analogue headphone only.
I don't have the audio experience to reliably critique various high end systems but this USB > coax DAC sound slighter warmer than a direct USB connection to my entry/mid range TEAC A-H01 with burr brown 5102 DAC..
However I'm new to HQ audio so there may be a placebo effect 🙂
LTF
It has a hardware volume control built in.
I use a different DAC for Moode audio but I have this piggy backed with a giant elastic band (Franken-DAC!) to a USB hub; back fed by a USB power bank and the usual Apple lightning camera connection kit straight to my iPhone with a modest pair of sennheiser headphone adequately powered straight from the ES9023 's 3.5mm socket. There's another 3.5mm output that is buffered through an amplifier, I personally find the direct connection loud enough.
The volume knob on this digitally alters the iPhones "AirPlay" volume, in the same way the phones volume buttons would.
One drawback is that it's powered throught the single USB port so you do need a powered hub to get it to work direct from the Lightning port due to its current draw.
I've never tested it with Moode but my other HIFIMEDIY DAC >> HiFimeDIY Sabre USB DAC 2 (external PSU) Asynchronous works fine with Moode via asynchronous USB and outputs a rich tone over coax In addition to line level and headphone outputs. The volume control is analogue headphone only.
I don't have the audio experience to reliably critique various high end systems but this USB > coax DAC sound slighter warmer than a direct USB connection to my entry/mid range TEAC A-H01 with burr brown 5102 DAC..
However I'm new to HQ audio so there may be a placebo effect 🙂
LTF
MoOde Audio works with official Raspberry Pi 7” Touchscreen Display
Looks excellent. Could you share with us how you enabled the display?
Regards
Ian
Hey Tim, what info do you need and how can I test my hardware with my device name, instead of pretending to be some other compatible device? Is there a table I can update somewhere?
Unless you have to sign some sort of IP disclaimer when you buy their chips, they don't have a hope in hell in dictating what their customers do with their chips once they are paid for.
I can't see how a driver written by you can be in their control in any way whatsoever.
Possibly they have licensed and hard coded some third party IP and you writing a driver that unlocks those features puts them in violation, but that's their problem, not yours. The only issue for you would be if you made some devices and advertised them for sale with ESS-locked features, unlocked.
If the driver publishes information that was only made available under NDA, where by signing the NDA you agree not to publish any proprietary information..... I know more than I am willing to say in public on this matter.
Anyway, this is veering somewhat off-topic for this thread.
The default RPi kernel doesn't support > 192k. 384k support is possible if you are willing to patch the kernel and have hardware capable of 384k. It is unlikely that the 384k patch set will ever be included in the RPi kernel sources.
The 384k patch set is available from the Enable 352k8 and 384k sample rates for I2S connected boards/HATs that support those rates PR, and should still apply to current rpi-4.4.y sources.
The 384k patch set is available from the Enable 352k8 and 384k sample rates for I2S connected boards/HATs that support those rates PR, and should still apply to current rpi-4.4.y sources.
Last edited:
Of course.
Helped @lorenzoferrara of rataks
https://rataks.com/blog/first-test-with-moode-and-official-raspberry-pi-touch-display.html
It is not as nice as in the Rune, but it works.
Maybe someday @Tim also will do it. 😀
I connected from two pc at the same time while listening a radio and the UI went nuts, playlist disappeared and it was showing as stopped, while actually it was playing.
I could shuffle the playlist from lirc and mpc clients... 🙂
As soon I restart mpd, the UI starts working again.
Maybe add an automatic restart of mpd too if php stops?
I could shuffle the playlist from lirc and mpc clients... 🙂
Code:
20160905 140045 watchdog: PHP restarted ([B]fpm child limit 18 exceeded[/B])
Code:
[04-Sep-2016 15:42:04] NOTICE: fpm is running, pid 871
[04-Sep-2016 15:42:04] NOTICE: ready to handle connections
[04-Sep-2016 15:42:04] NOTICE: systemd monitor interval set to 10000ms
[[B]05-Sep-2016 14:00:45] NOTICE: Terminating ...[/B]
[05-Sep-2016 14:00:45] NOTICE: exiting, bye-bye!
[05-Sep-2016 14:00:45] NOTICE: configuration file /etc/php5/fpm/php-fpm.conf test is successful
[05-Sep-2016 14:00:46] NOTICE: fpm is running, pid 12070
[05-Sep-2016 14:00:46] NOTICE: ready to handle connections
[05-Sep-2016 14:00:46] NOTICE: systemd monitor interval set to 10000ms
Code:
Sep 5 14:00:45 moode systemd[1]: Stopping The PHP FastCGI Process Manager...
Sep 5 14:00:45 moode systemd[1]: Starting The PHP FastCGI Process Manager...
Sep 5 14:00:46 moode systemd[1]: Started The PHP FastCGI Process Manager.
Sep 5 14:01:21 moode systemd[1]: Starting user-1000.slice.
Sep 5 14:01:21 moode systemd[1]: Created slice user-1000.slice.
Sep 5 14:01:21 moode systemd[1]: Starting Session c1 of user pi.
Sep 5 14:01:21 moode systemd[1]: Started Session c1 of user pi.
Sep 5 14:01:21 moode systemd[1]: Starting User Manager for UID 1000...
Sep 5 14:01:21 moode systemd[12167]: Starting Paths.
Sep 5 14:01:21 moode systemd[12167]: Reached target Paths.
Sep 5 14:01:21 moode systemd[12167]: Starting Timers.
Sep 5 14:01:22 moode systemd[12167]: Reached target Timers.
Sep 5 14:01:22 moode systemd[12167]: Starting Sockets.
Sep 5 14:01:22 moode systemd[12167]: Reached target Sockets.
Sep 5 14:01:22 moode systemd[12167]: Starting Basic System.
Sep 5 14:01:22 moode systemd[12167]: Reached target Basic System.
Sep 5 14:01:22 moode systemd[12167]: Starting Default.
Sep 5 14:01:22 moode systemd[12167]: Reached target Default.
Sep 5 14:01:22 moode systemd[12167]: Startup finished in 71ms.
Sep 5 14:01:22 moode systemd[1]: Started User Manager for UID 1000.As soon I restart mpd, the UI starts working again.
Maybe add an automatic restart of mpd too if php stops?
Hi,
Moode 2.7 watchdog already has mpd auto-restart.
Which version of Moode are u using?
-Tim
Release: 2.7 2016-08-28 release notes
Update: (None)
😉
Mpd was running, it never stopped.
But when phpfhm closed and it was restarted by the watchdog, the UI wasn't operational until I manually restarted mpd (even though mpd was already running, I checked).
Weirdly as soon I restarted mpd, everything in the UI worked fine, playlist showed etc.
Update: (None)
😉
Mpd was running, it never stopped.
But when phpfhm closed and it was restarted by the watchdog, the UI wasn't operational until I manually restarted mpd (even though mpd was already running, I checked).
Weirdly as soon I restarted mpd, everything in the UI worked fine, playlist showed etc.