Moode Audio Player for Raspberry Pi

Tim:

I haven't upgraded to v3.8 yet but expect to do so in the near future. Moode is a terrific solution for me and I'm happy to support your efforts, but I do have a question: in my implementation, Moode does not recognize about half of the music stored on my home network. I have duplicate servers with 500GB SSDs running Daphile, each connected to a different stereo. The servers are storing nearly 11,000 tracks apiece but Moode's Library includes less then 6,000.

Any ideas?

Regards,
Scott
 
I've got three MoOde units, all of them have always been static IP'd from the original 1.7 release.

Your problem is external to MoOde, maybe your IP settings were incorrect? That certainly one area I've never had a problem with MoOde.

Cheers Zootalaws,

I will give it another go.
What i've found is that a static IP (with gateway but no DNS entry) "bricks" the player. No wifi and no connectivity whatsoever. I did leave "Check for eth0 ip" on though.
The switch doesnt "see" it and when connected straight through (no switch), i can't ping it. Its an enigma. I'm trying to circumvent the radio and i've currently got a DHCP server going which it seems to do the job.
Once i get a spare SD card and a system image going, it will be time for round #2. 😀
 
Tim,

Looks like you have a great media player - do you have any plans for a build for RPi CM3 modules - I guess with recommended WiFi dongles?

@JohnW

As inviting as some of the CM3 features look to this old hacker---the embedded 4Gb eMMC, lots of interfaces like 2xI2C, 2xSPI, 2xUART, 2xSD/SDIO, 1xDPI, and also 48 I/O lines---having to use a SODIMM socket to get at them seems a showstopper. The CM3 is cheap but the bespoke IO board is outrageously expensive. Are you cooking up something on your own?

Apart from the physical connector issue, how are you going to get audio out of the CM3 module to a DAC? I don't see I2S listed on the datasheet so the choices seem to be either USB or HDMI. There's only one USB2 interface which implies an offboard USB hub dealing with as many as 1) either a USB DAC or a USB-to-I2S adapter-to-I2S DAC, 2) any additional USB-based storage, and 3) either a USB WiFi adapter or a USB-to-ethernet adapter. I have no experience with taking audio out the HDMI interface but that would seem to require yet more "stuff".

This is not a criticism of your approach. Lord knows I have enough PC motherboards, SBCs, microcontrollers, and assorted paraphernalia in my basement to prove I've been up for almost any hack over the years if it looked interesting to me. I'm just really curious how you're going about this.

Regards,
Kent
 
Hi to all. I want to buy this LCD screen with touch support Waveshare 1024x600. To working them correctly, it must be setup some settings or simply connect to my RPi3 via HDMI and USB cable for touch functionality ?

Hi, evs.

moOde Player is designed to be a headless device. To implement local input and display takes some extra work. Search this forum for past messages, especially by Morias, for example, #7876

I successfully followed his instructions to get an HDMI display working with my moOde Player just to see if it were possible, but then removed it. I have no experience with getting a touchscreen working but I believe others have done it.

Regards,
Kent
 
Tim / Kent,

It’s a long story, but to skip over many details I retired and in my "bored" retirement offered performance tweaks’ to one of my designs on a great local British HiFi forum, however unhappy with the results / cost of these tweaks I started a design of a “crowd funded” project to develop a new replacement Mainboard for the DAC… that’s was a few year ago – and I’m now only just nearing the end of the design!!! (yes I'm VERY bad with time-scales).

Trouble is I have about 100 project sponsors and its just too expensive in Europe to manufacture “consumer audio” and 100 pcs is too small to consider a production run in China – so backed into a corner I purchased a small 1500 CPH PnP machine (arriving September), a cheap manual stencil printer and reflow oven so will build these PCB’s myself!!!

Obviously I’ve spent far more developing the design then I can ever hope to see back from the 100pcs… but this is the HiFi industry - the only way to make a Million dollars is to invest 10 million! I tell myself this is love!!!

Back to the media player / streamer for our little forum project, after a couple of false starts (Beaglebone – really under powered & a Chinese Allwinner H3 board (no support)) we settled on good old RPi – BUT only after the CM3 module (despite its limitations) was released as this allows us to design an “audio optimized” solution where all system clocks are synchronized to the Audio Master clock and other requirements.

Fundamental requirements of the streamer solution:-

DAC is Audio Master Clock – no ASRC or RAM buffer reclocking

Bit accurate audio Data to atleast 384KHz and DSD256 - no messing with the Audio data

Native DSD support

Controlled EMC – no internal WiFi / Bluetooth and synchronized system clocks

Video output support (HDMI)


Secondary “System” requirements:-

MQA decode and rendering

Ability too drive an internal system display via 24bit RGB GPIO port & touch panel.

“Over the air” system updates

ADC / SPDIF input support

System MCU control

For myself and Jarek (a fellow Brother in Arms) hardware design is no issue and despite XMOS being a real real pig to work with, we are able to implement the XMOS as an audio “Coprocessor” interfacing the CM3 USB to the Audio “subsystem” and handling the system “MCU” side and MQA decode, UART channels etc.

There is little “practical” documentation on the CM3 – but being based on the RPI3 one can figure it out – care has to be taken with the PCB design around the HDMI and USB – but we have in house TDR so can validate the critical HDMI layout – USB seems more tolerant, but its not a walk in the park to do the job correctly. Hardest part is the detective working filling out the missing information on the CM3 – I have no idea why RPi are so “protective” of there module design when its so simple, it does make the work harder for system implementers – its not like we could purchase the BCM processor if we wanted to!

Asides form the HDMI, USB, Ethernet, WiFi / BT, PSU, Clocks etc. have to be taken care off – to be honest, for most people the RPI3 is perfect, it’s only because we want a fully integrated streamer we have taken the hard path (and apparently I’m told I have that disorder where I drive for never achievable perfection)!

Our PCB is designed to fit within the existing product chassis and will connect to the new Mainboard (which is still in design) – so we quickly spun a “DevDAC” (Development DAC) based on a per of ESS9038Q2M’s operating in fully balanced mode and providing the required clocks etc. to the streamer PCB to allow development of the XMOS and streamer software. The “DevDAC” PCB also has the an interface connector for our ADC board (not started the design yet) and while is a very decent DAC (dual ES9038’s) is only intended as a “get me going hardware” development platform for the software guys to start playing with while we complete the design of the “proper” DAC mainboard.

We are committed to Volumio and are very happy with the solution for our shipped streamer software, but have promised that the platform is “open” allowing owners to install there own preferred Media player – and many have asked about support for Moode – hence my post here 🙂

I understand that Moode supports Squeezebox and that is a very big plus for many of our project sponsors….

Streamer PCB and DevDAC board:-

Dropbox - streamerDevDac.jpg

DEVDAC board

Dropbox - DEVDAC A01 2.jpg

Original A01 Streamer hardware (we are now on “final release” A03):-

Dropbox - MCM3 A01 SSP1.JPG

Dropbox - CM3 fitted.JPG

The streamer PCB is an odd “L” shape as its designed to fitted within an existing chassis and to avoid restricting heatsink airflow / being directly above the analogue section on the Mainboard below.

We will try Moode, but the I’m not sure if you have a Device Tree blob for the CM3? we will also have to define our Ethernet Enable / reset GPIO in the blob file + drivers for the external WiFi / BT USB dongle…

In a post above it was mentioned Moode is designed to be used headless... for me, a very big plus of Volmuio is its support for HDMI output UI and wireless keyboard.

I’m too old school to mess about with my phone / tablet (atleast initially) – being able to plugging in a HDMI monitor and keyboard / track pad is simple and painless…. Many of our project sponsors are just as old school and like myself are scared off by all the streaming / media player talk, so I just want a simple no mess solution… Yes, indeed I’m one of those guys still using WindowsXP!
 
Last edited: