Moode Audio Player for Raspberry Pi

Neither of those manufacturers ESS dacs have official Ess firmware afaik. So the auto-mute function when switching between DSD and other sample rates will not be implemented .
That is exactly how my ebay ESS 9018K2m performed before the settings below.

Use the Generic-2 (rpi-dac) setting in MoOde config (not the buffalo!) and install the advanced LL kernel then edit /boot/config.txt and add simple-bclk-64fs as below....



That should give the quietest transition.....
I not expert computer
this setting in moode config i try but no function install advance LL kernel
do I install in pi3 ?
 
I not expert computer
this setting in moode config i try but no function install advance LL kernel
do I install in pi3 ?

Configure>System>scroll down to System Modifications>Linux Kernel and use the drop down box to get Advanced LL.

If you're not seeing that then you are on an older release.
You will need to download the latest version for the LL.

Or you could install the "Advanced Kernel " option in the older release and add the
Code:
dtoverlay=simple-bclk-64fs
to /boot/config.txt
 
Last edited:
Shoutcast/Icecast radio station file info?

Catching up with reading here on the forum...

One thing I wanted to ask, could there be support for the radio stations that (I believe) are based on the Shoutcast format? Radio Paradise, Morow, got to be others, etc...

As I understand it, is that they burp out a file info packet in the stream every 10-20 seconds or so, so the player can display artist, track name, maybe the album cover art, etc...

Would be nice to see that on the Moode display, like good ol' Winamp... Currently I see nothing on those stations, someone let me know if it's in there and I haven't turned it on.
 
Catching up with reading here on the forum...

One thing I wanted to ask, could there be support for the radio stations that (I believe) are based on the Shoutcast format? Radio Paradise, Morow, got to be others, etc...

As I understand it, is that they burp out a file info packet in the stream every 10-20 seconds or so, so the player can display artist, track name, maybe the album cover art, etc...

Would be nice to see that on the Moode display, like good ol' Winamp... Currently I see nothing on those stations, someone let me know if it's in there and I haven't turned it on.


I think this is known as ICY-Metadata and it is up to the Radio station to put it in. I think Moode does not decode the stream itself it but puts it in the MPD play list and it is MPD and its plugins that decodes the stream, extracts the Meta Data.

The radio station usually puts in the Track Title and Artist but occasionally the Album but I don't think any put album artwork in there.

When Moode displays the details for a Radio station I think it has got this from MPD, and the currentsong txt file is built from this MPD status data.

So what I am saying in a round about way is Moode does support metadata that MPD decodes.
 
Last edited:
Catching up with reading here on the forum...

One thing I wanted to ask, could there be support for the radio stations that (I believe) are based on the Shoutcast format? Radio Paradise, Morow, got to be others, etc...

As I understand it, is that they burp out a file info packet in the stream every 10-20 seconds or so, so the player can display artist, track name, maybe the album cover art, etc...

Would be nice to see that on the Moode display, like good ol' Winamp... Currently I see nothing on those stations, someone let me know if it's in there and I haven't turned it on.

Hi,

Metadata is coming through on my end.

-Tim
 

Attachments

  • moode-r38-radio-morrow.png
    moode-r38-radio-morrow.png
    166.7 KB · Views: 311
  • moode-r38-radio-radioparadise.png
    moode-r38-radio-radioparadise.png
    150.1 KB · Views: 294
Hi - Some screen shots of moOde 3.8 including UI improvements, kernel 4.9.33, and new USB boot capability made possible by Raspbian 2017-04-10 release.

Hats off to the Raspbian dev's for making USB boot so easy to configure :)

-Tim
 

Attachments

  • moode-r38-playback.png
    moode-r38-playback.png
    279.2 KB · Views: 285
  • moode-r38-audiocfg.png
    moode-r38-audiocfg.png
    70.9 KB · Views: 286
  • moode-r38-chipoptions.png
    moode-r38-chipoptions.png
    88.3 KB · Views: 276
  • moode-r38-kernel4.9.y.png
    moode-r38-kernel4.9.y.png
    62 KB · Views: 177
  • moode-r38-usbboot-cmdline.png
    moode-r38-usbboot-cmdline.png
    77 KB · Views: 167
  • moode-r38-usbboot-mount.png
    moode-r38-usbboot-mount.png
    84.4 KB · Views: 169
Hi - Some screen shots of moOde 3.8 including UI improvements, kernel 4.9.33, and new USB boot capability made possible by Raspbian 2017-04-10 release.

Hats off to the Raspbian dev's for making USB boot so easy to configure :)

-Tim

Yes, it's very easy to set up.

Thanks for including it. With SSDs at basement prices, it's a much more reliable platform than SD, where quality of disk is imperative.
 
Hi @soldeed,

Programming the OTP memory to enable USB boot does not affect booting from SD card. The system can still boot from an SD card. If both a bootable SD card and a bootable USB drive are connected then the system defaults to booting from the SD card.

moOde 3.8 will include a System config setting to enable USB boot capability and a new File System Expander that works on both SD cards and USB drives. :)

-Tim
 

Attachments

  • moode-r38-sysconfig-usbboot.png
    moode-r38-sysconfig-usbboot.png
    90 KB · Views: 463
Is it correct to assume that if you follow the above procedure to boot by USB that once the OTP has been changed then you can never boot by SD card again?

Does 3.8 change anything with regards to the USB boot ability?

Thanks

Just to clarify: the multi-boot feature was available with the new support chip, but hadn't been tested, so they left it turned off in the production Pi3. Once turned on, now there is support, there's really no need to turn it back off.

As well as USB MSD boot, it supports PXE (remote boot over Ethernet) which, once you set it up, is seriously cool - run Moode for Audio, Kodi for multimedia, or whatever other custom os you want - great for testing, etc. Just tell the PXE server what os to serve and reboot - great for "Pi in the wall" installations or distributed headless Pi across a network.

No storage needed at all on the Pi, you can assign network storage of whatever size you want (My 'work' PXE server has 12TB of SAS storage - only a few cents per GB!) or you can distribute a custom Moode config to each device based off a common image - you only need to change the hostid, which you can script to be the MAC address or a portion of. Great for distributed multi-room.

If you have kids, get them a Pi3 and PXE a desktop image with centralised storage, printing, etc. and no need to worry about corruption, virii, etc. - desktop performance for a fraction of a desktop pc price. Of course PXE will distribute any OS - windows, Linux, Mac OS - as long as the device supports it (most modern kit does) depending on what you want to do. Buy some second hand thin clients if you want more grunt and distribute Windows or Linux. My home PXE server is on a Mac mini, but it could be a Windows pc, Linux box, or Pi (put that Pi2 to work - PXE server doesn't need to be able to PXE boot itself) and doesn't need to be dedicated - PXE and network storage doesn't need much grunt.
 
Last edited:
Controlling moode from USB remote

Hi Javier,

I'm not aware of anything like this on Linux but you could try asking the DAC manufacturer if they support Linux for returning player cmds from their remote via the USB audio connection.

-Tim

Context: I have moode installed on a RPi, with a USB DAC connected. This USB DAC has an infrared remote, and I am still trying to be able to control moode with this remote.

I have been investigating a bit, and it looks like this could be accomplished as follows: moode has a Linux kernel compiled with HID support. In moode, I can see a /dev/input/event0 socket where the commands from the remote are visible (meaning: if I cat the file, I get hexadecimal output every time I press the remote). Now, I have to connect this input to mpd, I have found a tool called triggerhappy that would be helpful for that.

Do you think this makes sense? If I have an external source going directly to mpd, would that confuse moode somehow? Anybody has any other, better ideas on how to implement this?

TIA,

Javier
 
Just to clarify: the multi-boot feature was available with the new support chip, but hadn't been tested, so they left it turned off in the production Pi3. Once turned on, now there is support, there's really no need to turn it back off.

As well as USB MSD boot, it supports PXE (remote boot over Ethernet) which, once you set it up, is seriously cool - run Moode for Audio, Kodi for multimedia, or whatever other custom os you want - great for testing, etc. Just tell the PXE server what os to serve and reboot - great for "Pi in the wall" installations or distributed headless Pi across a network.

No storage needed at all on the Pi, you can assign network storage of whatever size you want (My 'work' PXE server has 12TB of SAS storage - only a few cents per GB!) or you can distribute a custom Moode config to each device based off a common image - you only need to change the hostid, which you can script to be the MAC address or a portion of. Great for distributed multi-room.

If you have kids, get them a Pi3 and PXE a desktop image with centralised storage, printing, etc. and no need to worry about corruption, virii, etc. - desktop performance for a fraction of a desktop pc price. Of course PXE will distribute any OS - windows, Linux, Mac OS - as long as the device supports it (most modern kit does) depending on what you want to do. Buy some second hand thin clients if you want more grunt and distribute Windows or Linux. My home PXE server is on a Mac mini, but it could be a Windows pc, Linux box, or Pi (put that Pi2 to work - PXE server doesn't need to be able to PXE boot itself) and doesn't need to be dedicated - PXE and network storage doesn't need much grunt.

Thanks for the information, I am going to read up on a PXE server.
 
Context: I have moode installed on a RPi, with a USB DAC connected. This USB DAC has an infrared remote, and I am still trying to be able to control moode with this remote.

I have been investigating a bit, and it looks like this could be accomplished as follows: moode has a Linux kernel compiled with HID support. In moode, I can see a /dev/input/event0 socket where the commands from the remote are visible (meaning: if I cat the file, I get hexadecimal output every time I press the remote). Now, I have to connect this input to mpd, I have found a tool called triggerhappy that would be helpful for that.

Do you think this makes sense? If I have an external source going directly to mpd, would that confuse moode somehow? Anybody has any other, better ideas on how to implement this?

TIA,

Javier

Hi Javier,

I think you need to install and configure lirc package to be able to map remote control device cmds to MPD cmds.

I don't have any experience with remotes but I recall some posts in this thread by others that have successfully configured lirc with their remotes.

-Tim
 
Configure>System>scroll down to System Modifications>Linux Kernel and use the drop down box to get Advanced LL.

If you're not seeing that then you are on an older release.
You will need to download the latest version for the LL.

Or you could install the "Advanced Kernel " option in the older release and add the
Code:
dtoverlay=simple-bclk-64fs
to /boot/config.txt

I up to 3.7 now
boot/config.txt I have to do in which step need to connect lan and wifi ?
now I put sd card to pi3
and have advance LL kernel select it .