@Kent
Why do people climb mountains? Because they there to climb 🙂
While as you said the RPi is very easy to work with, it is also very hard to ignore the power the Tinker Board provides so I'm still hoping more support will come over time.
I'm trying out another approach I came across in a Japanese discussion board, where you have moOde on one RPi, which will take care of the GUI, UPnP, etc and MPD part, and pass along the PCM stream to another board with the DAC, in my case the Tinker Board.
Regards
goldhorse
A bit old ... but got it to work without modifications except editing mpd.conf (i can't choose this in Moode configuration), so let me explain :
On RPI3 (Wifi disabled), paired my bluetooth speaker with bluetoothctl (not a big deal , trust, pair, connect ) after discovering it.
In bluetoothctl :
[UE BOOM NOIR]# info 88:C6:26:XX:XX:XX
Device 88:C6:26:XX:XX:XX
Name: UE BOOM NOIR
Alias: UE BOOM NOIR
Class: 0x240418
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v000ApFFFFdFFFF
[UE BOOM NOIR]#
Then edit mpd.conf to add :
audio_output {
type "alsa"
name "Bluetooth Speaker"
device "bluealsa:HCI=hci0,DEV=88:C6:26:XX:XX:XX,PROFILE=a2dp"
}
But currently if i switch on my amp, i got also music on my speakers !!!
Maybe just because added on mpd.conf and not making a possible choice.
Maybe someone can rework this kind of settings 😉
regards
brought me a 7" touchscreen, and SmartiPi Touch case, so yesterday after all the gifts were unwrapped and the kids were busy with games and/or LEGO, I sat down to try out Moode. I already had a Pi3 and IQAudio DAC Pro assembled and tested with the IQAudio test image, but had so far failed to get other music player packages all sorted 
(mostly Max2Play and OpenElec, a few hours of fiddling on each).HUGE kudos to Tim and this forum!
The SmartiCase comes with a power splitter, so you don't even need to solder in the 5 pin header to pull power to the screen from the Hat. Physical assembly was trivial. Then I:
- Burned a blank Raspbian stretch image with ApplePi Baker
- ssh'd into the Pi3 and followed the Build Script 2.2 instructions, copy and paste style
- So many reboots. Bonus: wow a Pi3 with a minimal image boots FAST.
- After the basic "Initial Configuration" procedures in step 12 of the build script, I followed the 2 IQAudio DAC config steps for Moode from page 38 of this guide:
http://www.iqaudio.com/downloads/IQaudIO.pdf - After "Step 13" cleanup and reboot, I skipped the optional components until getting to "Component 8 - Local UI Display"
- This is literally the only build step I had to interpret: Where Tim writes, "NOTE: These steps are performed AFTER actually starting local display via System config, rebooting and then accessing moOde on the local display" you need to hop to page 1103 of this very thread and read @Morias hints. Execute anything there that isn't in the build script. Side Note: as someone who has been around since X11R3, it is hysterical to me that we still fiddle with 3-5 line .xinitrc configs to make everything go.
Now I'm copying the big music library to a fresh drive, and will move everything down to the big stereo this afternoon 🙂
[Then, because I am a cranky old masochist with firm opinions about computing topics, I will see if I can extract systemd from the mix without breaking everything. Quiet you. Yes I am That Guy. Leave me to my quirks]
Which build script are you referring to?
HUGE kudos to Tim and this forum!
The SmartiCase comes with a power splitter, so you don't even need to solder in the 5 pin header to pull power to the screen from the Hat. Physical assembly was trivial. Then I:
...and BOOM. Fully functional touchscreen music player with high quality DAC output, first time through, no hassles. That's impressive as hell.
- Burned a blank Raspbian stretch image with ApplePi Baker
- ssh'd into the Pi3 and followed the Build Script 2.2 instructions, copy and paste style
- So many reboots. Bonus: wow a Pi3 with a minimal image boots FAST.
- After the basic "Initial Configuration" procedures in step 12 of the build script, I followed the 2 IQAudio DAC config steps for Moode from page 38 of this guide:
http://www.iqaudio.com/downloads/IQaudIO.pdf- After "Step 13" cleanup and reboot, I skipped the optional components until getting to "Component 8 - Local UI Display"
- This is literally the only build step I had to interpret: Where Tim writes, "NOTE: These steps are performed AFTER actually starting local display via System config, rebooting and then accessing moOde on the local display" you need to hop to page 1103 of this very thread and read @Morias hints. Execute anything there that isn't in the build script. Side Note: as someone who has been around since X11R3, it is hysterical to me that we still fiddle with 3-5 line .xinitrc configs to make everything go.
Now I'm copying the big music library to a fresh drive, and will move everything down to the big stereo this afternoon 🙂
[Then, because I am a cranky old masochist with firm opinions about computing topics, I will see if I can extract systemd from the mix without breaking everything. Quiet you. Yes I am That Guy. Leave me to my quirks]
Hi,
Just a heads up that I've been testing latest MPD 0.20.13, Hardware volume, and am seeing an issue where sending MPD a "setvol 0" command occasionally results in 100% volume!!
Regressing to MPD 0.20.12 and no issues.
-Tim
Just a heads up that I've been testing latest MPD 0.20.13, Hardware volume, and am seeing an issue where sending MPD a "setvol 0" command occasionally results in 100% volume!!
Regressing to MPD 0.20.12 and no issues.
-Tim
I don't care i'm MPD bugproof :
An externally hosted image should be here but it was not working when we last tested it.
😀
It's in the other/build subdir of the latest source package:
Code:
wget [url]http://moodeaudio.org/downloads/beta/rel-stretch-r40b12.zip[/url]
unzip rel-stretch-r40b12.zip
more ./rel-stretch/other/build/build_recipe_v2.2.txtMoOde r4b12 with power button
Then the command:
I find myself with:
Then when ordering:
once the file edit I can not save it:
Have you had this problem?
Hi,
Then the command:
Code:
sudo cp worker.php worker.sav
Code:
cp: can not create regular file 'worker.sav': Read-only file system
Code:
sudo nano worker.php
Code:
[Error writing worker.php: Read-only file system]
Building moOde -- the story so far . . .
Hello everyone,
I hope you had a wonderful holiday spending time with the most important people in your life.
For those just joining the thread -- perhaps Santa brought you a brand new RPi -- I thought I'd quickly summarise the build options for Tim Curtis's moOde audio player:
Emendations or updates are very welcome.
Richard
Hello everyone,
I hope you had a wonderful holiday spending time with the most important people in your life.
For those just joining the thread -- perhaps Santa brought you a brand new RPi -- I thought I'd quickly summarise the build options for Tim Curtis's moOde audio player:
- IMG file: There is no img option at the moment due to GPL licensing issues. Short answer here http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-1218.html#post5282792
- Source files + build recipe: this is a step-by-step process that involves building moOde on a Raspberry Pi running the Raspbian OS via SSH terminal commands. You will need two microSD cards, one for running Raspbian and one for building moOde, and a microSD-USB card adapter (multi-card adapters are not recommended as they can appear as multiple mount points and confuse things). This essentially involves copying commands from the build recipe into the terminal and allows a lot of customisation opportunities for experienced Linux users. Source files and recipe can be downloaded at moodeaudio.org
- moOde OS Image Builder: this is an automated script by koda59 and Tim that uses the above build recipe that is run on an RPi with Raspbian. As per the build recipe, it requires two SD cards and an adapter. It is (mostly) set and forget but there are some options that need user input at the start and you will be prompted to remove the microSD card from the USB adapter and use it to reboot the RPi to continue the build. Details are in the support section of moodeaudio.org
- Moosimbu script: this is a patched version of the automated image builder provided by HeeBoo. It requires only one microSD card and updates the existing Raspbian installation to moOde OS. It is a work in progress and supported by HeeBoo. See this post for downloading the script http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-1216.html#post5281736
- DietPi installation: moOde is now installable via the DietPi distribution. Some functionality is not integrated yet but this should be solved in the future: DietPi / Fuzon • View topic - v159
- I suggest using ethernet to connect the RPi to the network/internet while building as the process seems to run more smoothly than via WiFi. However YMMV.
- Be patient and allow some time for the build process. Some users have reported more than an hour.
- You can monitor the build process via SSH during the final stage (the RPi booting from the moOde OS card) with the following command (thanks HeeBoo). The password to login at this stage is moodeaudio:
Code:
ssh pi@moode "cat ~/mosbuild.log | grep 'COMPONENT\|STEP\| Compile \| END\| Error'"Richard
There may be an alternative method but this works for me. Go to browse, click on RADIO and on the far right you will see . . . click on the three ... to get pop with options. Click on create and you enter in the address for your new station.
Hope this helps.
Attachments
Thank's guys for that script, it works nicely!
It would be good if the build steps could be outlined on the website as well - I had to check the forum for the details.
It would be good if the build steps could be outlined on the website as well - I had to check the forum for the details.
Tim,
Will it be difficult to integrate pairing Bluetooth from Moode instead using bluetoothctl command ?
In the same spirit, is there a way to choose an audio output from Moode from mpd.conf ? ( i changed mine to have Moode as source sink).
All is working well, but i need to tweak mpd.conf if i only want output on my speakers or on Bluetooth speaker.
Could be cool to have it direct in MoOde interface 🙂 even if BT speaker is not very audiophile.
Maybe it is too much changes.
Will it be difficult to integrate pairing Bluetooth from Moode instead using bluetoothctl command ?
In the same spirit, is there a way to choose an audio output from Moode from mpd.conf ? ( i changed mine to have Moode as source sink).
All is working well, but i need to tweak mpd.conf if i only want output on my speakers or on Bluetooth speaker.
Could be cool to have it direct in MoOde interface 🙂 even if BT speaker is not very audiophile.
Maybe it is too much changes.
Last edited:
Err, not easy for this idiot, but I'll get there. Like Malefoda said,
Zootalaws's comment,
... really is arrogant. We all stand on the shoulders of giants. We shouldn't forget that we were all newbie's once, even the giant (grinch) Zootalaws!
Trying out the mosbuild.sh script. running over Ethernet
I can get through Step One and the new "OS" written onto the second (newly formatted) SD card. Remove first SD and replaced with second, and reboot.
Bootup sequence runs for a bit and then gives me
[FAILED] Failed to start /etc/rc.local Compatibility
and then dumps me out to the moode login.
What have I missed?
I can get through Step One and the new "OS" written onto the second (newly formatted) SD card. Remove first SD and replaced with second, and reboot.
Bootup sequence runs for a bit and then gives me
[FAILED] Failed to start /etc/rc.local Compatibility
and then dumps me out to the moode login.
What have I missed?
Just installed Moode 4 Beta 12 on Pi 2B successfully without any problem whatsoever.
Followed Heeboo's instructions for a single SD Card installation and came back a couple of hours later to a fully working setup.
Initial setup done via hardwired ethernet, set Wi-Fi up afterwards and am now listening to 24/192 FLAC over the air.
Many thanks to Tim for all the hardwork you put into this project. Thanks too to koda59 and Heeboo for their input into the installation scripts.
Followed Heeboo's instructions for a single SD Card installation and came back a couple of hours later to a fully working setup.
Initial setup done via hardwired ethernet, set Wi-Fi up afterwards and am now listening to 24/192 FLAC over the air.
Many thanks to Tim for all the hardwork you put into this project. Thanks too to koda59 and Heeboo for their input into the installation scripts.
That's the way to go, IMHO.
I suspect that most users have a single instance of Moode and don't need the added complication of trying to build an installable Moode image.
Cheers,
Phil
Hi,
Do you mean allowing moOde to send audio over BT for example to a BT Speaker?
If you have a working config, email me and lets see what can be done to integrate into moOde 🙂
MPD outputs are changed via command below where N is a number from 1 - 4 that identifies the output. If you have added an output block to end of mpd.conf then it would be 5.
mpc enable only N
-Tim
Hi koda59,
I changed mosubuild wait4rc 10 to 30 in mosbuild_worker.sh and build process goes well. I can build beta12 on my RasPi1B and that works fine.
Thank you for your advice.
Regards,