Where can I find the default cover image on the SD card? The one in var/www/images/default-cover.jpg doesn't seem the right one (changed this image for a test)
JW
JW
CPU: armv6l, 1.0 GHz, 22%, 28°
Tried apt-get dist-upgrade multiple times on fresh Moode 3.1 but just wouldn't work for me.
Cheers,
energyman
The best thing with these electronic projects is just keep at it and tackle one thing at a time.
1) Download the current disk image (3.1) from the Moode site. You will need a utility to write the image onto an SD card--8 mb should do fine--you can't just copy the file as you would normal files.
2) Get the Pi, put the card with the Moode OS in it. At this point, just use the power supply that comes with the Pi, or similar USB one. Leave the battery for a later stage of the project. As you know now, everything you will want to do with Moode on the rpi, you will do with a web interface, which is pretty clean and straightforward. The Raspberry Pi 3 has it's own wi-fi built in. If you're using an earlier version, you will need an "access-point compatible" wi-fi adaptor.
3) Now you must absolutely follow the Moode instructions for setup step-by-step. This will allow you to access the rpi and configure its system to suit your needs and hardware.
4) Once you have some music playing, you can go on and figure out how you want to do the volume control, how you want to set up your battery power supply, case and so on.
You didn't say how portable a rig you're interested in building. If you're building a really portable player (walkman-style), you will of course need to pay special attention to how much power is being consumed, so that will affect choices of which Pi to use, which DAC, etc. Also, the DACs are mostly designed to output a line-level signal and won't drive headphones. So you would need a headphone amp stage or possibly a DAC with a headphone amp built in. I don't know if anyone has done this yet, but it's an interesting project.
Don't give up. These projects can appear daunting at first, but like I said, just go step-by-step and eventually you'll learn a ton and get something you can be proud of. That's the whole point of all of this.
Cheers,
The 4.9 kernel must have been updated since I tried it, then. Which is not unlikely, as the 4.4 kernel was updated after I had started testing my Pi Zero W.
Cheers,
Phil
Who will be first to use Moode Audio to output audio through the bluetooth on a Raspberry Pi Zero W?
energyman
energyman
Noise issue with spotify-connect-web and Moode
Hi guys,
I have been using Moode for a while now, and am totally amazed. I have Pi3, and an Audioquest Dragonfly USB as DAC. I'm not super with the programming end, although I do enjoy it.
Everything is up and running, including the spotify web connect service from RafaPolit.
However, when I switch from playback in Moode to Spotify, I hear a huge amount of static noise and faintly in the background, the music. I don't know where the issue is, from Moode playback everything works smoothly, and only when changed to Spotify music - nothing but static...
Help?
Inez
Hi guys,
I have been using Moode for a while now, and am totally amazed. I have Pi3, and an Audioquest Dragonfly USB as DAC. I'm not super with the programming end, although I do enjoy it.
Everything is up and running, including the spotify web connect service from RafaPolit.
However, when I switch from playback in Moode to Spotify, I hear a huge amount of static noise and faintly in the background, the music. I don't know where the issue is, from Moode playback everything works smoothly, and only when changed to Spotify music - nothing but static...
Help?
Inez
Hi,
Some screen shots of two nice new features coming to Moode 3.5: Airplay 3.0 configs and System information. Thanks to MikeB for a fantastic shairport-sync 3.0 release and to inmate SC for a wonderful system info script.
-Tim
Some screen shots of two nice new features coming to Moode 3.5: Airplay 3.0 configs and System information. Thanks to MikeB for a fantastic shairport-sync 3.0 release and to inmate SC for a wonderful system info script.
-Tim
Attachments
@TimCurtis, this looks amazing, can't wait to try it!
On a side note: I tried to use my moode players for voice output via openhab and realized that apparently the squeezelite version has problems with playing back short files.
According to the maintainer it is fixed: Issue streaming VoiceRSS mp3 content to piCorePlayer - Page 2
Not sure about the versions used in moode, but an upgrade would be very nice.
On a side note: I tried to use my moode players for voice output via openhab and realized that apparently the squeezelite version has problems with playing back short files.
According to the maintainer it is fixed: Issue streaming VoiceRSS mp3 content to piCorePlayer - Page 2
Not sure about the versions used in moode, but an upgrade would be very nice.
Hi,
The version currently included in Moode 3.5 is v1.8.6-829. I'll need to bump to v1.8.6-938 which has the fix. Should be doable.
-Tim
Very nice indeed, can't wait!
What about Spotify Connect in v3.5? Any news?
Maybe USB automount? 🙂
What about Spotify Connect in v3.5? Any news?
Maybe USB automount? 🙂
Hi,
Auto mount by disk label for USB storage has been in Moode for a long time.
The dev for librespot recently updated issue #150 regarding volume and he plans to implement a setting for initial-volume. https://github.com/plietar/librespot/issues/150
When this is done, I'll integrate the super nice librespot renderer in Moode 🙂
-Tim
Hi Inez,
Can you tell me what power supply you are using and what the mA rating is? When I got this sort of symptom on my Pi3, it was because I was using a power supply that was too small.
That would be great update, because volumio or rune don't work okay with spotify.
***
Okay not "automount" but automatic mpd db update after automount in raspbian. If I put USB stick in, nothing happens. I have to go to sources and press update mpd db and after that it is visible under browse. For me it's okay, because I don't use usb sticks but every new user I recommend Moode, I got call or msg with: wtf, why I can't use usb stick/hdd with moode. I think it would be nice if this is initiated in the background without user interaction, just a notification with USB device connected. It works fine in rune and libreElec.
Hi,
I'm not sure auto-indexing is such a great idea. I'll bet an equal number of users would absolutely not want that to happen each time they plugged in their USB stick(s).
Just point your friends to Step #4 in Moode Setup Guide
4. ADD SOURCE(S) CONTAINING MUSIC FILES
- USB AND SDCARD STORAGE DEVICE
a) Menu, Configure, Sources
b) press UPDATE MPD DATABASE button
c) WAIT for completion (no spinner on the Browse tab)
d) click Browse tab. If more folders appear than those containing music then restart MPD
-Tim
Hi,
I'm using an USB adapter I had lying around, with 2A output. But if that is the issue, shouldnt all my audio be static? It's only when I switch to spotify connect. When I play from my harddrive (attached with USB hub with its own power supply) the sound is normal.
Yes I totally agree with you, but it would be really great to see usb device immediately after I plug it in. No need for mpd db update or indexing. It would be temporary device anyway. More like a shortcut to mnt/SDCARD...
Just like a regular player/computer/phone/tablet etc. What do you think?
Not necessarily - but 2A should be enough, so that probably isn't the cause.
I'm not a spotify user, but the spotify boards are full (hundreds of threads) of people complaining about the exact same thing. Maybe it's just that their protocols are easily disturbed? Check https://community.spotify.com, given the thousands of posts about the same thing, it may be something completely unrelated to your Pi or Moode - like wifi, internet, whatever device you are streaming from...
So you want to 'see' the device, or you want Moode to be aware of music tracks on the HDD?
You can see the device as soon as it's plugged in, or at least I can, when I'm logged in via ssh, but without Moode updating the MPD database, you can't play anything.
if it's just that selecting the 'update' button is too many clicks away, I'm sure you could write a script that is triggered on USB insertion that kicks off a DB update.