Hello, Moode player 2.7 very nice work. Using it on a PI3 with on board audio (3.5mm plug) which with some tweaking has resulted in pretty decent sound. I would like to step it up a notch using a DAC. There seems to be a lot of confusion around which DAC's (especially onboard PI3) are compatible and work with Moode. Can someone provide some guidance here of a decent board for say under $100 canadian that is compatible with the Moode player system. Output should be RCA jack as I have an older system in mind for this.
Thanks in advance.
Go to here : moodeaudio.org
Click on the "Audio Devices" link.
I have a Hifiberry DAC on a Pi B revision 2. A Sainsmart "PIFI or HIFI DAC" on a Pi3 and a CM6206 5.1 USB soundcard on a Pi Zero. All run Moode pretty well.
I s'pose the "Mamboberry" is closest to ultimate audio fidelity of the sat-on-top DAC hats.
a decent board for say under $100 canadian that is compatible with the Moode player system. Output should be RCA jack as I have an older system in mind for this.
Here, you'll get 5 of these for your budget...😉 not a hat but i2s connected. If you want to be able to use it on other FormFactors as well then get the matching xmos (usb) (I have both, they work Ootb for Moode .)
ES9018K2M ES9018 I2S input DAC decoder board Support IIS-32bit 384K / DSD64
NEWEST XMOS U8 USB 384K 32B I2S SPDIF output,support DSD for es9018 DAC | eBay
Works great, thank you! The problem with this is two-fold: you still have to access output from mpc current to get song length and position, and also I was expecting full access to all metadata (ie including lyrics) though. I want to try mediainfo, exiftool and mutagen-inspect but maybe you have a better approach, do you?Hi,
Turn on "External metadata" setting in System config. This will update /var/www/currentsong.txt file with song data from UI.
-Tim
Hello, Moode player 2.7 very nice work. Using it on a PI3 with on board audio (3.5mm plug) which with some tweaking has resulted in pretty decent sound. I would like to step it up a notch using a DAC. There seems to be a lot of confusion around which DAC's (especially onboard PI3) are compatible and work with Moode. Can someone provide some guidance here of a decent board for say under $100 canadian that is compatible with the Moode player system. Output should be RCA jack as I have an older system in mind for this.
Thanks in advance.
If you just want a cheapie, you can get an i2s HAT from aliexpress for around US$15-20. If you want quality, I would look at IQAudio in the U.K. Gordon knocks off the VAT for foreign buyers and his shipping prices are very reasonable.
The aliexpress unit is very much worth a look as your first DAC, and at CDN$20 it's not a lot on a punt. I've bought a ton of them to use with my vintage radio upgrades and they ain't half bad.
For anything more hifi I've tried a bunch including hifiberry but can't fault the IQAudio. Very nice.
Hello,
I was working on a dedicated radio in the last few weeks, with stand alone operation as radio with LCD and buttons and as music player with remote web control.
It works fine now, except one thing. My initialization and button watching python script starts too early (in rc.local now), when mpc is not ready yet. I was told to make it a service and make it depending on mpc. I try to learn that now, how to do. If you have suggestion on this, I appreciate, but I have and even more important question :
- how can I make it boot faster?
Now, on a pi 2, it takes about 2 min to boot, with "waiting for network" disabled (static address). Do you have ideas how can I make it much faster? Openelec boots in a few seconds. Do you have ideas how to go that direction?
Thanks a lot,
JG
I was working on a dedicated radio in the last few weeks, with stand alone operation as radio with LCD and buttons and as music player with remote web control.
It works fine now, except one thing. My initialization and button watching python script starts too early (in rc.local now), when mpc is not ready yet. I was told to make it a service and make it depending on mpc. I try to learn that now, how to do. If you have suggestion on this, I appreciate, but I have and even more important question :
- how can I make it boot faster?
Now, on a pi 2, it takes about 2 min to boot, with "waiting for network" disabled (static address). Do you have ideas how can I make it much faster? Openelec boots in a few seconds. Do you have ideas how to go that direction?
Thanks a lot,
JG
I did not see that it was a subject recently.
My moode.log :
pi@radio:~ $ cat /var/log/moode.log
20161115 142415 worker: Startup
20161115 142450 worker: Host (radio)
20161115 142450 worker: Hdwr (Pi-1B+ 512MB)
20161115 142450 worker: Arch (armv6l)
20161115 142450 worker: Krnl (4.4.19+)
20161115 142450 worker: OS (moodeOS 1.0)
20161115 142451 worker: Rel (Moode 2.7 2016-08-28)
20161115 142451 worker: Upd (None)
20161115 142451 worker: MPD (0.19.19)
20161115 142451 worker: Session loaded
20161115 142451 worker: Debug logging (off)
20161115 142451 worker: File check...
20161115 142454 worker: File check ok
20161115 142456 worker: Auto-shuffle deactivated
20161115 142457 worker: USB sources (none attached)
20161115 142458 worker: MPD started
20161115 142500 worker: wlan0 exists
20161115 142500 worker: wlan0 trying SSID (TMJ)
20161115 142501 worker: LCD updater engine started
20161115 142501 worker: Audio (I2S audio device)
20161115 142501 worker: Audio (HiFiBerry DAC+)
20161115 142503 worker: PCM5122 chip options applied
20161115 142505 worker: ALSA outputs unmuted
20161115 142505 worker: ALSA mixer name (Digital)
20161115 142505 worker: MPD volume control (software)
20161115 142505 worker: MPD output 1 ALSA default (enabled)
20161115 142505 worker: MPD output 2 ALSA crossfeed (enabled)
20161115 142506 worker: Hdwr volume controller exists
20161115 142507 worker: Volume level (26) restored
20161115 142507 worker: wlan0 (192.168.1.14)
20161115 142508 worker: eth0 exists
20161115 142508 worker: eth0 wait 1 for address
20161115 142512 worker: eth0 wait 2 for address
20161115 142516 worker: eth0 wait 3 for address
20161115 142519 worker: eth0 address not assigned
20161115 142519 worker: NAS sources (none configured)
20161115 142519 worker: MPD consume reset to off
20161115 142519 worker: Watchdog started
20161115 142519 worker: End startup
20161115 142519 worker: Ready
Thanks,
JG
My moode.log :
pi@radio:~ $ cat /var/log/moode.log
20161115 142415 worker: Startup
20161115 142450 worker: Host (radio)
20161115 142450 worker: Hdwr (Pi-1B+ 512MB)
20161115 142450 worker: Arch (armv6l)
20161115 142450 worker: Krnl (4.4.19+)
20161115 142450 worker: OS (moodeOS 1.0)
20161115 142451 worker: Rel (Moode 2.7 2016-08-28)
20161115 142451 worker: Upd (None)
20161115 142451 worker: MPD (0.19.19)
20161115 142451 worker: Session loaded
20161115 142451 worker: Debug logging (off)
20161115 142451 worker: File check...
20161115 142454 worker: File check ok
20161115 142456 worker: Auto-shuffle deactivated
20161115 142457 worker: USB sources (none attached)
20161115 142458 worker: MPD started
20161115 142500 worker: wlan0 exists
20161115 142500 worker: wlan0 trying SSID (TMJ)
20161115 142501 worker: LCD updater engine started
20161115 142501 worker: Audio (I2S audio device)
20161115 142501 worker: Audio (HiFiBerry DAC+)
20161115 142503 worker: PCM5122 chip options applied
20161115 142505 worker: ALSA outputs unmuted
20161115 142505 worker: ALSA mixer name (Digital)
20161115 142505 worker: MPD volume control (software)
20161115 142505 worker: MPD output 1 ALSA default (enabled)
20161115 142505 worker: MPD output 2 ALSA crossfeed (enabled)
20161115 142506 worker: Hdwr volume controller exists
20161115 142507 worker: Volume level (26) restored
20161115 142507 worker: wlan0 (192.168.1.14)
20161115 142508 worker: eth0 exists
20161115 142508 worker: eth0 wait 1 for address
20161115 142512 worker: eth0 wait 2 for address
20161115 142516 worker: eth0 wait 3 for address
20161115 142519 worker: eth0 address not assigned
20161115 142519 worker: NAS sources (none configured)
20161115 142519 worker: MPD consume reset to off
20161115 142519 worker: Watchdog started
20161115 142519 worker: End startup
20161115 142519 worker: Ready
Thanks,
JG
oops, running through this I realized something : it is a pi 1, not a 2. I mixed it up. I have some other at home, hope the 2 is much faster.
Regards,
JG
Regards,
JG
oops, running through this I realized something : it is a pi 1, not a 2. I mixed it up. I have some other at home, hope the 2 is much faster.
Regards,
JG
Hi,
I'm considering adding setting that allows the eth0 check to be bypassed This would trim 9 secs from Moode startup for configs that are WiFi-only or AP-only.
-Tim
good point,
I just set it to static also, so it does not wait for DHCP.
Another thing, I'm still struggling with the start of my script. Now I start only when mpc command responds, but still, it starts too early and does not initialize. I also made an initialization button now, if I press that after it really boots up, it works fine.
Do you know what service or event should I watch?
Basically the initialization script sets it into radio mode by loading a radio playlist (which is a channel list), sets volume level (I use hardware potentiometer) and starts play.
mpc clear
mpc load radio
mpc play
mpc volume 100
Same thing before the button press watching part, but that does not work. Just after a while (about another 30 sec) at a button press initialize well with the same commands.
I could add delay, but that is the last thing I want to do. The best would be to know what event should I wait for. Or, I could do a loop before the initialization that only exits when I have the right answer to a command. I have tried to look for "volume" answer to the mpc command, but that does not work either. Before play, mpc respond "volume:...". Unfortunately, when mpc answers, it is still to early to start.
Thanks,
JG
I just set it to static also, so it does not wait for DHCP.
Another thing, I'm still struggling with the start of my script. Now I start only when mpc command responds, but still, it starts too early and does not initialize. I also made an initialization button now, if I press that after it really boots up, it works fine.
Do you know what service or event should I watch?
Basically the initialization script sets it into radio mode by loading a radio playlist (which is a channel list), sets volume level (I use hardware potentiometer) and starts play.
mpc clear
mpc load radio
mpc play
mpc volume 100
Same thing before the button press watching part, but that does not work. Just after a while (about another 30 sec) at a button press initialize well with the same commands.
I could add delay, but that is the last thing I want to do. The best would be to know what event should I wait for. Or, I could do a loop before the initialization that only exits when I have the right answer to a command. I have tried to look for "volume" answer to the mpc command, but that does not work either. Before play, mpc respond "volume:...". Unfortunately, when mpc answers, it is still to early to start.
Thanks,
JG
Hi, Im new on this, congrats for your work, love it!
I have two questions about moode Audio (sorry if it's redundant):
Is there any way to force login (user/password) to connect to the web interface? I'm planning to use it in a bar and don't want anyone to access.
Will be in future updates features to manage the queue? For example "listen next" would be very nice
Thank you!
I have two questions about moode Audio (sorry if it's redundant):
Is there any way to force login (user/password) to connect to the web interface? I'm planning to use it in a bar and don't want anyone to access.
Will be in future updates features to manage the queue? For example "listen next" would be very nice
Thank you!
Last edited:
this is how my new radio hardware looks like : iohttps://mega.nz/#F!QsR1mQDL!ADKXUlrboCk1Oq0kmate8Q
Regards, JG
Regards, JG
Thanks for the advice in regards to usuable DAC's for the PI3. Can't wait to receive it and try it our on version 3.0. 🙂 No pressure. Yvon.
why moode in my system sounds better when I upsample to 24/192?? weird
Many, perhaps most DAC chips upsample internally, and go to 192/24 or 384/24 (or nearby variants). I most cases the internal upsampling is less than optimal as the DAC chips use expedient versions of the algorithms to minimize complexity, in-process memory, and heat. Upsampling software used by a player, like SoX inMOODE, is implemented in a more capable processing environment with more fully effective algorithims, so the upsampled data passed to the chip more correctly conform the the desired algorithmic output and the DAC chip processing load is lightened. There are many ins and outs to this, so I suggest you try many or most of the upsampling controls you have in MOODE.
Skip
this is how my new radio hardware looks like : iohttps://mega.nz/#F!QsR1mQDL!ADKXUlrboCk1Oq0kmate8Q
Regards, JG
Hi.
Is is possible to read manual about your project?
I have no manual, but I try to describe what I did.
Basically it is a Moode audio player with 2 hardware addition :
- a 2x16 char LCD display,
- 3 button,
Software side I added two scripts :
- the LCD updater, that is called by Moode
- the buttons handler, that is inserted as service now
I make some description and upload.
regards,
JG
Basically it is a Moode audio player with 2 hardware addition :
- a 2x16 char LCD display,
- 3 button,
Software side I added two scripts :
- the LCD updater, that is called by Moode
- the buttons handler, that is inserted as service now
I make some description and upload.
regards,
JG
Allo Piano Dac 2.0 ( and 2.1)
Hi Tim,
I had a look through the posts here and cannot find any reference.
Will Moode version 3 have configuration choices for the Allo Dacs?
(I see Max2play and Volumio have added the Allo devices to their repertoires, although the Volumio driver for the Allo 2.1 which adds the TI dsd output filtering doesn't work properly yet)
many thanks
regards
Patrick
Hi Tim,
I had a look through the posts here and cannot find any reference.
Will Moode version 3 have configuration choices for the Allo Dacs?
(I see Max2play and Volumio have added the Allo devices to their repertoires, although the Volumio driver for the Allo 2.1 which adds the TI dsd output filtering doesn't work properly yet)
many thanks
regards
Patrick
Hi,
I'm considering adding setting that allows the eth0 check to be bypassed This would trim 9 secs from Moode startup for configs that are WiFi-only or AP-only.
-Tim
Sounds like a great idea to me.
Hi,
I'm considering adding setting that allows the eth0 check to be bypassed This would trim 9 secs from Moode startup for configs that are WiFi-only or AP-only.
-Tim
+1 great idea!!! 🙂
- Home
- Source & Line
- PC Based
- Moode Audio Player for Raspberry Pi