Moode Audio Player for Raspberry Pi

Hi,
I'm about to receive my first Raspberry Pi, which I'm going to bundle with Hifiberry's Digi+ Pro. After poking around, it looks like Moode is my best option for compatibility and sound quality and I like the look of the UI (great job!). So, my question is this....

I'd like to be able to stream my music library (flac + mp3) from my NAS through the digi+ pro and then via toslink to my DAC, for which Moode Audio looks like a perfect solution. However, I also want to be able to keep my wife's ability to easily control Spotify using Spotify Connect.

I've read about this project: https://github.com/Fornoth/spotify-connect-web, which would seem to allow the functionality I want (ie turning my Raspberry Pi into a kind of Spotify streamer), but I'm not clear on whether this is possible to do within Moode Audio (all reference to that spotify-connect-web project I've found relate to volumio or raspian). If this is possible, I'm also unsure whether I will be able to switch seamlessly between controlling moode audio player (playing my own audio library) and Spotify-Connect (ie that both options are always available without having to load or stop any app or service in order to switch).

The key thing here is that nothing disrupts my wife's ability to just open Spotify and play her music through our stereo with Spotify connect as she's always done. Anything else is going to confirm all her claims about my geekery making her life more complicated...and then she wins.
Is this spotify-connect-web project what I want? Is running this alongside/within Moode possible? Is doing do going to get me what I'm after? Are there any good tutorials for making what I'm talking about work? Is this even the best way to do what I'm after? Very grateful for any and all responses and thanks in advance! :)

You are aware of the fault with the Hifiberry Digi Pro that kills wifi? If you use Ethernet, it won't be an issue, up if you are intending on using wifi, it causes some issues.

I'm surprised they are still selling it, actually, as they are quite aware of the problem and have told current owners to return for a refund or wait for a replacement board.

You won't have any problem with the IQ Audio Pi-DAC+, a great bit of kit.
 
Maybe I'm an old git, but I find git confusing...

I thought you could create your code somewhere on your desktop and once you linked your root (branch) it would automagically replicate in the cloud.

I did have a bunch of them working when I was doing a lot of C on micro controllers, CNN machines and such, but I let them slide.

I found the act of creating files, refreshing, etc. ok, but there's was this whole other arcane side that managed versioning hat I never spent the time to learn and thus, found it annoyed me.

Anyone a git master? (Bad pun)


No "maybe" about it here. I know I'm an old git, and so do my grandkids, but that's life.

The thing I like about git is the ability at any time of development to make an existing directory into a git repository. For me, it's a great way to keep track of changes I make to configuration files (consider managing /etc as a git repo), to spawn branches for different systems/configurations, and to try out ideas, merging those that work and killing off those which don't, etc. I find it lightweight and easy to use and I would use it even if github didn't exist.

I would rank myself a brown belt in git-iness (we need a emoji to denote puns, especially bad ones). When I get into trouble, I pull out my git bible. As you say, git has its arcane side.

Regards,
Kent
 
No "maybe" about it here. I know I'm an old git, and so do my grandkids, but that's life.

The thing I like about git is the ability at any time of development to make an existing directory into a git repository. For me, it's a great way to keep track of changes I make to configuration files (consider managing /etc as a git repo), to spawn branches for different systems/configurations, and to try out ideas, merging those that work and killing off those which don't, etc. I find it lightweight and easy to use and I would use it even if github didn't exist.

I would rank myself a brown belt in git-iness (we need a emoji to denote puns, especially bad ones). When I get into trouble, I pull out my git bible. As you say, git has its arcane side.

Regards,
Kent

I suspect that a week spent investing in it would pay returns.

I use the arduino ide a bit, and they don't play well together. The insistence of putting the branch name in confuses arduino which means I am always renaming folders. That's what stopped me using it in the first place.

It does integrate well with Mac OS, including into the built-in Mac development environment. I've not investigated whether I can use it with adobe products yet, but if it could, that would be a bonus.
 
You are aware of the fault with the Hifiberry Digi Pro that kills wifi? If you use Ethernet, it won't be an issue, up if you are intending on using wifi, it causes some issues.

I'm surprised they are still selling it, actually, as they are quite aware of the problem and have told current owners to return for a refund or wait for a replacement board.

You won't have any problem with the IQ Audio Pi-DAC+, a great bit of kit.

I'm surprised too.

It's difficult to tell from their website that a problem even exists. Where exactly is this offer of a refund and does it apply to both the HiFiBerry Digi+ Pro and their DAC+ Pro? I acquired a DAC+ Pro to share with Tim back when it seemed there was only a driver problem and have suffered through the subsequent reveal of the hardware problem. I was snookered by the fact that I had had zero problems with my HiFiBerry DAC+.

Regards,
Kent
 
Last edited:
Thanks, Tim! I had read about Airplay, but had disregarded this option because (1) it's less straightforward than Spotify connect and (2) I've read that the quality suffers dramatically compared to pulling Spotify directly from their servers. Are you saying that the project I pointed toward won't work in Moode for some reason? I think it will. My question is more about allowing it to run in the background somehow, without disturbing Moode's local file playback service.
So, let's say I don't want to use Airplay...?
Thanks again!
J

Hi,

The Airplay implementation in Moode uses SoX to resample input thats < 16/44 to 16/44. Audio quality is excellent.

I don't know anything about spotify connect or the particular project you referenced but generally, based on what I do know about how music service API's work, it would take a substantial amount of time and effort to integrate into Moode.

If you are just talking about running another Airplay-like receiver/renderer alongside Moode then its a bit less effort to integrate but nonetheless not trivial.

-Tim
 
I'm surprised too.

It's difficult to tell from their website that a problem even exists. Where exactly is this offer of a refund and does it apply to both the HiFiBerry Digi+ Pro and their DAC+ Pro? I acquired a DAC+ Pro to share with Tim back when it seemed there was only a driver problem and have suffered through the subsequent reveal of the hardware problem. I was snookered by the fact that I had had zero problems with my HiFiBerry DAC+.

Regards,
Kent

Hi Kent,

Below is a link to the bug report on raspberry/linux Git for the DAC+Pro WiFi issue. It looks like Hifiberry has resolved the issue with new oscillators and the bug report has been closed. They posted a support link.

https://github.com/raspberrypi/linux/issues/1588

-Tim
 
Hi,

I'm using Rpi 1/B+ and Hifiberry DAC+.

Hi was using Rune audio, the NAS was working fine (NFS), but I was unable to setup my Hifiberry DAC+, and there was so many bugs ! I decided to switch to Moode, it's definitely more stable :)

Radio station are working fine.

I tried to load a network folder shared and my Synology NAS using NFS :

- Syno : I'm not sure about what to do with the "squash" parameter
- Moode /configure / sources => the NAS source seems to be loaded
- Moodle / Browse / NAS : the NAS item is visible in the list but empty
- SSH : ls /mnt/NAS/NAS show the content of my network folder

After reboot :
- Moodle / Browse : no NAS item in the list

I've tried multiple syno configurations and reboot but I didn't solve the problem.

If any idea, thank you for your help.
 
Hi Kent,

Below is a link to the bug report on raspberry/linux Git for the DAC+Pro WiFi issue. It looks like Hifiberry has resolved the issue with new oscillators and the bug report has been closed. They posted a support link.

https://github.com/raspberrypi/linux/issues/1588

-Tim

Thanks, Tim. The last time I looked at this repo, there was still only the supposition that the HiFiBerry DAC+ Pro board was emitting excessive EMI. i'm guessing the HiFiBerry Digi+ Pro board could be using the same oscillators and hence could suffer the same problem but searching the repo turns up no corresponding issue.

What I don't see on the HiFiBerry website is an official acknowledgment of the problem, an announcement of a modified board, or any suggestion that existing boards can be returned for exchange other than their generic guarantee in the fine print. To this old git, burying information in a blog and in the raspberry pi code repo isn't the same as being forthright with one's customers.

And just so first-time readers don't get the wrong impression, I'll repeat that my HiFiBerry DAC+ board is working flawlessly.

Regards,
Kent
 
Hi,

I'm using Rpi 1/B+ and Hifiberry DAC+.

Hi was using Rune audio, the NAS was working fine (NFS), but I was unable to setup my Hifiberry DAC+, and there was so many bugs ! I decided to switch to Moode, it's definitely more stable :)

Radio station are working fine.

I tried to load a network folder shared and my Synology NAS using NFS :

- Syno : I'm not sure about what to do with the "squash" parameter
- Moode /configure / sources => the NAS source seems to be loaded
- Moodle / Browse / NAS : the NAS item is visible in the list but empty
- SSH : ls /mnt/NAS/NAS show the content of my network folder

After reboot :
- Moodle / Browse : no NAS item in the list

I've tried multiple syno configurations and reboot but I didn't solve the problem.

If any idea, thank you for your help.

Hi, Bonelli.

I don't have any Synology equipment here but they have been mentioned on this thread before. Try entering "synology" in the "Search this thread" pulldown menu at the top of this page. IIRC someone else was having difficulties last summer.

Regards,
Kent
 
Hi,

The Airplay implementation in Moode uses SoX to resample input thats < 16/44 to 16/44. Audio quality is excellent.

I don't know anything about spotify connect or the particular project you referenced but generally, based on what I do know about how music service API's work, it would take a substantial amount of time and effort to integrate into Moode.

If you are just talking about running another Airplay-like receiver/renderer alongside Moode then its a bit less effort to integrate but nonetheless not trivial.

Ok. This is again helpful. Thanks again for the quick response. I'll see how things go. I'm actually curious now to see how Airplay compares. Spotify Connect is simply a feature of the app that allows you to choose what device you playing from. It's simple, intuitive and has worked flawlessly (on my old WIN box). Because the music itself streams directly from Spotify servers to whatever device you're actually playing from (i.e. not streaming it from a third device to a player as with Airplay), it's hard to imagine this not being a better quality signal, but I'll have to see. Thanks in any case for your response and all your work on this project!


-Tim
 
Hi Kent,

Below is a link to the bug report on raspberry/linux Git for the DAC+Pro WiFi issue. It looks like Hifiberry has resolved the issue with new oscillators and the bug report has been closed. They posted a support link.

https://github.com/raspberrypi/linux/issues/1588

-Tim

Thanks for information about this! I didn't realize that there this bug had even existed. Here's hoping you're right and it's been resolved.
 
Last edited:
Hi,

Here are a few screen shots of the wonderful Mamboberry LS DAC prepped for MoodeCase :)

-Tim
 

Attachments

  • mambo_ls_1.png
    mambo_ls_1.png
    865.3 KB · Views: 304
  • mambo_ls_2.png
    mambo_ls_2.png
    878.1 KB · Views: 286
I'm surprised too.

It's difficult to tell from their website that a problem even exists. Where exactly is this offer of a refund and does it apply to both the HiFiBerry Digi+ Pro and their DAC+ Pro? I acquired a DAC+ Pro to share with Tim back when it seemed there was only a driver problem and have suffered through the subsequent reveal of the hardware problem. I was snookered by the fact that I had had zero problems with my HiFiBerry DAC+.

Regards,
Kent

I think you have to email them and ask.
 
Thanks, Tim. The last time I looked at this repo, there was still only the supposition that the HiFiBerry DAC+ Pro board was emitting excessive EMI. i'm guessing the HiFiBerry Digi+ Pro board could be using the same oscillators and hence could suffer the same problem but searching the repo turns up no corresponding issue.

What I don't see on the HiFiBerry website is an official acknowledgment of the problem, an announcement of a modified board, or any suggestion that existing boards can be returned for exchange other than their generic guarantee in the fine print. To this old git, burying information in a blog and in the raspberry pi code repo isn't the same as being forthright with one's customers.

And just so first-time readers don't get the wrong impression, I'll repeat that my HiFiBerry DAC+ board is working flawlessly.

Regards,
Kent

The ability to admit his products are less than perfect seems to be difficult for Daniel.

He refuses to admit his driver for the Amp is a problem, apparently I am the only person that has ever questioned it.

That I can't use the hardware volume control, which he could easily verify himself, is irrelevant - I am the only user with this problem.

I have bought a number of his units over the years, never again.

His attitude was quite telling. I reminded him of how many units I had bought and of how evangelistic I was, but that his attitude was making it unlikely I would buy again. His response was, why should I work on a problem for someone that is no longer a customer.

He must have failed the 'service' part of the customer service course.