Hi,
Some screen shots of Audio output routing for Bluetooth coming in moOde 4
-Tim
This is the most exciting news to me!
I don't know why it is so hard to you to make it work but I started from scratch and it only took me 40 minutes with build recipe if we discount the wasted time when I forgot to plugin my Ethernet switch power.
Sorry to hear that, are you able to put the required Raspian base image on a TF card using Etcher app? Once you do that, apply Heeboo's one-script-rules-all script. It works perfectly for me.
Sorry to hear that. I quote some posts which can really help you to success.
Please don’t forget automatic building process need around 40 minutes with at least 8 reboot.
You can monitor this with a cat command as described below, you must wait to have the END output before configuring or using MoOde.
Regards
You can stream Tidal, GooglePlay and Qobuz via Bubble but not Spotify. To stream Spotify over Moode you would need to install Raspotify, but there are volume issues which have made Tim reluctant to include it.
Best to stick with iOS/Airplay.
Hi everybody. I built my own speakers, and now that they’re done I hear that they can use some equalizing. I stream to a Raspberry Pi with a Dion Loco DAC AMP with Airplay and I assumed that I could use Moode to equalize the signal before it goes to the Loco.
But this is not how it works, right? The equalizers don’t seem to have any effect on the Airplay stream.
Do you have any ideas how I can enable this feature? Can it be built in into Moode? Or is there any other way I could achieve this? Any help is very much appreciated.
But this is not how it works, right? The equalizers don’t seem to have any effect on the Airplay stream.
Do you have any ideas how I can enable this feature? Can it be built in into Moode? Or is there any other way I could achieve this? Any help is very much appreciated.
I bought Tidal HiFi subscription now.
Tried BubbleUPnP on my Android device for this - it did not stream anything to MoOde UPnP.
Then I downloaded Tidal app on my iphone and tried using MoOde Airplay. No streaming there as well.
I thought it was a problem due to the HiFi quality, so I selected normal and that did not play either.
Then I restarted MPD and tried.
Still no luck.
MoOde 3.8 here.
Where is the new mosbuild ?
Sorry,
But i don't understand why Tim doesn't update the Koda's script to the latest version... It's more accurate than the first version, it's moOde version independent (for the mosbuild.sh part) and it's ready for the actual version (4b12).
Too many are bad installation experiences and don't want anyway redo these. I had made some patches for improve this, Koda take some, but never Tim feedback theses patches, why ? Because I change Koda script without permission ? I just want improve the User Experience.
@Tim, why wait the next "revision" for distrib it ? for the next version mosbuild_worker.sh must be redo (modified?) in all cases.
If it's distributed we can,(maybe with Koda), have feedback and improve this new script without waiting like now.(i'm not waiting)
If you need some help for the installation process maybe i can help us, tell me !
Thanks for all.
Good Next
Sorry,
But i don't understand why Tim doesn't update the Koda's script to the latest version... It's more accurate than the first version, it's moOde version independent (for the mosbuild.sh part) and it's ready for the actual version (4b12).
Too many are bad installation experiences and don't want anyway redo these. I had made some patches for improve this, Koda take some, but never Tim feedback theses patches, why ? Because I change Koda script without permission ? I just want improve the User Experience.
@Tim, why wait the next "revision" for distrib it ? for the next version mosbuild_worker.sh must be redo (modified?) in all cases.
If it's distributed we can,(maybe with Koda), have feedback and improve this new script without waiting like now.(i'm not waiting)
If you need some help for the installation process maybe i can help us, tell me !
Thanks for all.
Good Next
Last edited:
It seems MoOde got stuck on Airplay and never switched to another audio source.
After a restart of MPD and a complete shutdown of RPI and restart Tidal started working via Airplay and also via Bubble Upnp.
After a restart of MPD and a complete shutdown of RPI and restart Tidal started working via Airplay and also via Bubble Upnp.
Hi @HeeBoo,
Priority is to get newUI and Bluetooth Connect finished. They are almost done! Next on the list is to get the new mosbuild script tested and uploaded
In the meantime maybe I'll upload the script as-is and make a "TEST" link for it so people can begin to use it now.
What do you think?
-Tim
A modest proposal:
Some of you already know that a GitHub account "moode-player" was created about a month ago containing two GitHub repos: moode and mosbuild
See Moode Audio Player * GitHub
AIUI, this was done as a convenience to provide a snapshot of Tim's codebase to the DietPi project (which is based in GitHub). Tim has not been using these moode/mosbuild repos in his daily workflow but that doesn't mean we can't contribute via GitHub:
Post comments to Tim's mosbuild repo, clone the mosbuild repo to your own GitHub or git project, make your revisions, and post pull-requests to Tim's mosbuild repo. That way, your proposals can be tracked, we can discuss them in the GitHub comments, and agreed changes can be merged as appropriate. We'll all be seeing the "latest version" as well as the history of merged and rejected changes.
A parallel proposal is to use the "GitHub Project Page" capability to create a website with expanded installation instructions and possibly even HowTo's on various topics. It can be integrated into the above GitHub site [1]. I've already dabbled with this in a cloned repo and hope in the coming weeks to post a first cut as my own GitHub project, built in such a way that it can be merged into either the moode or the mosbuild repo. As above, the GitHub workflow enables others to comment and propose changes.
To me, full use of GitHub conveys several benefits:
- organizes proposals for technical changes (in place of the current cacophony of thread posts, emails, and tweets addressed to Tim)
- clarifies which proposals are accepted and how the changes are made
- reduces the techie crosstalk on this thread
- interested parties receive email notifications
I'm sure Tim is overwhelmed with work already and I don't want to add to his burden. IMHO this approach could help spread the work in a controllable way but that's just me based on my experiences in other GitHub-based projects. I'm proposing we start with mosbuild but if we're successful, then maybe moode too?
Full disclosure: Tim and I had several exchanges about git/GitHub when he was creating the GitHub repos. As a courtesy, he added me as an administrator, a power I have not exercised.
Regards,
Kent
[1] It is possible to configure GitHub to serve a Project Page to a custom domain. I haven't tried this capability, but it might be possible to serve the GitHub Project Page via a subdomain of Tim's moodeaudio.org. A lot depends on the DNS manager for his domain.
Hi Kent,
I don't currently use the Git repos for workflow or issue tracking so this definitely is not something I can support. Their only purpose at this time is to contain a snapshot of the releases and nothing more.
-Tim
Use your feelings, you must.
But currently, risk of multiple workflow :/
Maybe Tim can release a beta installer ... or maybe we can wait a bit more
But currently, risk of multiple workflow :/
Maybe Tim can release a beta installer ... or maybe we can wait a bit more
Last edited:
Hi @HeeBoo,
Priority is to get newUI and Bluetooth Connect finished. They are almost done! Next on the list is to get the new mosbuild script tested and uploaded
In the meantime maybe I'll upload the script as-is and make a "TEST" link for it so people can begin to use it now.
What do you think?
-Tim
@Tim: I think we must found a solution for upgrade this part without linking to the moOde revisions for the moment.
I don't want my patches in test mode but a way to update (in a short time) the builder part when it's ready. The first revision is for sure buggy and all these are already corrected by Koda. But we can't access to it.
I can put my scripts on a server too for testing but I don't want distribute myself without autorisation any work i do or Koda do for the installation process and i don't think is a good way (multiple adresse server, multiple different versions, etc...)
I love the proposal of theOldPresbyope.
For the moment I haven't GitHub account and I doesn't want "fork" the mosbuild project, but it's a good idea to use the actual GitHub for talk about all of this, make a dev "branch" and open it to all of us for helping and improving the development.
With a dev branch all of us can test and give feedback without replace the original way and give a chance to all who have problem with the original version to test with the dev version and maybe avoid the problem.
This is for me a good way for the 2 repos (mosbuild & moode), this is more simple for keep multiple revision up-to-date.
If I must create a GitHub account for helping the dev of moOde, i will do it !
And I hope we can continue to talk about that there ! for more clarity here and more clarity for the development !
I'm pretty sur Tim work like no others on this project and hope my comment no hurting any of you, this is not the goal. I just want make better this project and helping.
I'm ready for all moves just give me the way.
Regards
Hi @HeeBoo,
Priority is to get newUI and Bluetooth Connect finished. They are almost done! Next on the list is to get the new mosbuild script tested and uploaded
In the meantime maybe I'll upload the script as-is and make a "TEST" link for it so people can begin to use it now.
What do you think?
-Tim
Hi @Tim, @HeeBoo,
from the perspective of "user experience" I would strongly recommend to make the "one-card-script" available on the MoodeAudio website. Perhaps additionally to the official builder and with a short step-by-step instruction.
All I can comment to the script is: It worked flawlessly for my configuration (Win7 PC with Putty for SSH, RPi3 with official 7" touchscreen, network via ethernet, audio out via HDMI to Harman Kardon AVR). Took about 2 hours from blank SD card to working image. Again: Big thanks to HeeBoo for his modifications and of course the same to Koda59 for the initial script.
@Tim: I never before had a feature request (BT speaker support) positively answered within 2 days. "Our" IT guys usually need 2 weeks only to answer whether the request will be considered... This is awesome, like the entire MoodeAudio project is! Big thanks to you - the pure amount and the speed of your work is impressive.
Ok, the better
Regarding patience: This is my second name. And I have a working beta12 which is more than fine for me currently...