DietPi-Software | moOde

Fourdee commented 7 years ago

Currently under testing:

- https://github.com/Fourdee/DietPi/issues/1223#issuecomment-344674384

http://moodeaudio.org/

Now with FOSS license 👍

Fourdee commented 6 years ago

@moodeaudio Thanks Tim 👍

DietPi automatically mounts USB drives to /mnt/UUID_OF_PARTITION via /etc/fstab. This would override udisks-glue.

Options:

Disable dietpi-drive_manager auto mounting in /etc/fstab, for moOde install (not ideal, core to DietPi operation/compatibility)
User manually symlink (not ideal)
Change mpd.conf to support /mnt (and all its sub-directories) as the music data location. music_directory && playlist_directory
🈯️ Symlink /mnt to /var/lib/mpd/music/MNT during installation. If drive is then mounted by dietpi-drive_manager, location is MNT > UUID_OF_DRIVE, else, it will be under USB

chirohito commented 6 years ago

Volume control is not updated properly. For example when I turn volume up on M.A.L.P. app on smartphone ad open moode on PC in browser volume is still on last value updated through that same browser. Page refresh does not help.

BR!

TheOldPresbyope commented 6 years ago

@chirohito

The behavior you report doesn't concern the integration of moOde into DietPi. Rather it is the consequence of the design of moOde itself. You can take it up with the moOde developer, Tim Curtis, on the moOde thread on diyaudio.com

http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi.html

Cheers

kaytata commented 6 years ago

With rp3b + Allo Kali + Piano 2.1dac Moode works very well in Dual Mono mode. Could not make it work in subwoofer mode though. either 2.1 or 2.2. When setting is applied, it automatically switches back to dual mono mode. Any thoughts?

Major difference with volumio I find is that the discovery of my attached 2tb external hd is super quick, a couple of minutes compared to 4-5 hours on volumio.

moodeaudio commented 6 years ago

Hi @kaytata,

Good to hear that you are enjoying the fast performance :-)

The Allo Piano 2.1 firmware files are required to enable Subwoofer 2.1 and 2.2 modes to function. These files apparantly were not accepted into mainline Linux kernel but are available in an Allo Git repo. Below is the procedure I use to install them.

cd ~
wget https://github.com/allocom/piano-firmware/archive/master.zip
sudo unzip master.zip 
sudo rm ./master.zip
sudo cp -r ./piano-firmware-master/lib/firmware/allo /lib/firmware
sudo rm -rf ./piano-firmware-master
sudo reboot

-Tim

kaytata commented 6 years ago

@moodeaudio Thanks Tim for the solution. Works like a charm. Cheers.

Fourdee commented 6 years ago

@moodeaudio Thanks Tim,

This should of been in our RPi kernel package, i've added it back in, fixed for new installations.

kaytata commented 6 years ago

Hi, I had installed using fourdee's Automated image installation of moOde: The moode version installed was beta 9. I noticed some hanging. Tried to update the version to beta12 using the interface. It says moode is up to date.

Is there a simple way to update the moode software to beta12 using SSH?

Cheers,

martintenor commented 6 years ago

Hi,

Just installed moOde 4 beta 9 using the automated script. I see that upmpdcli is included, however it fails to load due to below. I exclusively use Lumin app to play songs (I don't like to mount my NAS) so I would appreciate if this could be solved.

Dec 21 08:53:49 DietPi systemd[2502]: upmpdcli.service: Failed at step EXEC spawning /usr/bin/upmpdcli: No such file or directory

youpilai commented 6 years ago

Hi,

First thanks for your effort to make it happens

I wonder, is this will work on Sparky one day ? i have an ALLO Piano DAC 2.1 + Kali on a Sparky board and wanted to try Moode I also have one ALLO Piano 1 that i can try with a RPi2, but have only one Kali board for now For testing purpose, i also have a RPiZero with IQAudio Pi-DACZero if needed (i'll have to buy more SD cards...)

ernesternest commented 6 years ago

Hi Fourdee, I wonder, if you are still planning to work on that issue. I switched from a PI to an Allo USB bridge, which contains an Allo Sparky, due to SQ reason. It is so much better, that I can't go back. But I really liked the look and performance of Moode :-) and so I would really be happy if this would be continued here.

Cheers

Fourdee commented 6 years ago

@moodeaudio

Hi Tim,

Firstly, i'd like to apologise for the way I've handled this ticket, letting it continue for so long, without any progress.

The reasons for this are:

I've left this ticket open, because I really wanted to make this happen. I love the Moode project and what you have achieved, however,
Some time ago, I seen a install script for Raspbian which you endorsed. This really put me off continuing the addition, as you already have a working installation method that you can maintain to your needs.
Moode is very specific to Raspbian install, and, sets the device to a one use purpose. This is the opposite of what DietPi tries to achieve. It would be possible (with many many man hours from both our ends) to achieve this. However, even then, it would require constant maintenance for each update. As our man hours are very limited, we must prioritize areas which effect the most users.
Currently, we have 0 installs for Moode in our survey: https://dietpi.com/survey/

Therefore, i've taken the decision to drop Moode from our software lineup. Again, I apologise for this, and, I appreciate all the work you've done during the start of this.

Regardless, I wish you and your project all the best in the future. It is beautiful peice of software.

Fourdee commented 6 years ago

Marking as closed due to: https://github.com/Fourdee/DietPi/issues/1223#issuecomment-401549371

MichaIng commented 6 years ago

@Fourdee To be fair, 0 installs is due to moode was disabled/not listed within dietpi-software in v6.9, thus no chance to get install counts 😉: https://github.com/Fourdee/DietPi/blob/master/dietpi/dietpi-software#L1067

But I agree: Same as with NextCloudPlus and Pi-hole, if upstream installation methods are too intrusive, it is a pain for us to integrate it into DietPi.

HolyMacarony commented 2 years ago

Thanks for your efforts non the less. I'd like to ask whether someone still has this ominous moode install script everyone was mentioning 5 years ago? The script that was linked in the regarding issue is no longer available. So is there really still a way to integrate moode on top of dietpi? It would be great. Any help in this regard would be very much appreciated. Thanks you!

Joulinar commented 2 years ago

Maybe a question you will need to raise at the moOde forum if they offer a way to install the software on top of an existing os or if the only way is to flash their full os image https://moodeaudio.org/forum/index.php

MichaIng commented 2 years ago

I see no hint about another install method or any script on their website or GitHub repos. So I think the answer is clear: moOde is available and supported as single purpose image only, using their prepared images, or their pi-gen based scripts to build an own image from scratch: https://github.com/moode-player/imgbuild

TheOldPresbyope commented 2 years ago

Referring to @Fourdee post of 4 years ago

Moode is very specific to Raspbian install, and, sets the device to a one use purpose. This is the opposite of what DietPi tries to achieve. It would be possible (with many many man hours from both our ends) to achieve this. However, even then, it would require constant maintenance for each update. As our man hours are very limited, we must prioritize areas which effect the most users.

This is still true.

Everything needed to build moOde is available in the github distros---both the old script and the newer multipart, mostly automated build system.

Keep in mind that moOde has always been intended to be a stand-alone player. It is easy to install and works extremely well on every model RPi. Tim is constantly adding new features and has a few other contributors, some regular, some one-time. Until the recent disappearance of RPis from the retail market, this has been sufficient. Every competing SBC has its own quirks and support system which makes porting and maintenance a real grind. I could wish it were otherwise but for this bear of very little brain, at least, the effort [ETA: the effort, that is to take advantage of the good work of the DietPi project to reduce the grind] is too much.

MichaIng commented 2 years ago

Thanks for clarifying.

both the old script and the newer multipart

Just out of interest: Where can the old script be found?

I now found the moode-player package build scripts https://github.com/moode-player/pkgbuild/tree/main/packages/moode-player and https://dl.cloudsmith.io/public/moodeaudio/m8y/setup.deb.sh which sets up the package repository from where moode-player can be installed. This seems to be something to look into as starting point when aiming to install moOde on an existing Raspbian/Debian RPi system.

TheOldPresbyope commented 2 years ago

Argh. I shouldn't have depended on my memory. I forgot the whole other/build directory got deleted back when the new build system showed its mettle in building moOde 8.0.0

In the github repo https://github.com/moode-player/moode

checkout commit 647b6ce

look for other/build/build_recipe.txt

#  Build Recipe v2.36 2021-12-17
#
#  moOde 7.6.1 2021-12-17
#  - Based on RaspiOS Buster Lite 2020-12-02 (10.6)
#  - Based on Linux kernel 5.4.77 build #1371

I believe this is the last version of the script. Since then extensions and repairs have been made only in the separate repos for the new build system. (ATM we are at moOde 8.2.2)

Sidebar: some years ago, several of us were partially successful in adapting the steps in build_recipe.txt to build moOde on an alternative SBC & OS: in one case, an OrangePi and, in the other case, a CuBox-I 4Pro. Just a month ago, I had partial success bringing up moOde on a Le Potato board using the Libre Computer Raspbian Portability Tool to modify the moOde image to boot on the Le Potato.

I say "partially successful" because in both of these approaches we dealt with none of the incompatibilities in system configuration between Raspbian/RaspiOS and the foreign OS, audio HAT drivers, etc., so the related portions of the moOdeUI were useless. Once configured, they did manage music and play tracks through onboard headphone outputs and offboard USB DACs. Tim's nice system update feature likely would work for some updates and not for others, depending on whether they fiddled with the system files in the boot partition. The result isn't exactly newbie-user friendly.

tjengbudi commented 1 year ago

@TheOldPresbyope hello. could you share how you make running moode in orange pi? i interested to run it at armbian and specific sbc. might you can help

TheOldPresbyope commented 1 year ago

Sorry, I was not the one who worked with a Orange Pi. The only thing I can suggest is read the now antique build script I mentioned in a previous comment. I have no idea how close to a current moOde player one could get with it.

The current release of moOde is v8.3.6, soon to be v8.3.7. These are both built on Raspberry Pi OS Bullseye (which is based on Debian 11) and run on RPis. We are just now exploring how to move to RaspiOS Bookworm (Debian 12). Porting to other OSes and SBCs is still not in the works.

tjengbudi commented 1 year ago

Ah i see.

I planned to used it with armbian instead dietpi. Cause i used sbc that only works with armbian right now. I see the image builder will download os raspi and install some default apps. I still do not know how to replace that

On Thu, Nov 9, 2023, 8:19 AM TheOldPresbyope @.***> wrote:

Sorry, I was not the one who worked with a Orange Pi. The only thing I can suggest is read the now antique build script I mentioned in a previous comment. I have no idea how close to a current moOde player one could get with it.

The current release of moOde is v8.3.6, soon to be v8.3.7. These are both built on Raspberry Pi OS Bullseye (which is based on Debian 11) and run on RPis. We are just now exploring how to move to RaspiOS Bookworm (Debian 12). Porting to other OSes and SBCs is still not in the works.

— Reply to this email directly, view it on GitHub https://github.com/MichaIng/DietPi/issues/1223#issuecomment-1803013211, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXGEP5QXA566MCD4GLKDW3YDQVQVAVCNFSM4ECARZNKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBQGMYDCMZSGEYQ . You are receiving this because you commented.Message ID: @.***>

MichaIng / DietPi