It seems that on most Android revs mDNS resolution isn't supported by Android core code, but by individual licensees - so LG may support mDNS resoiution, while Samsung might not.
This is becoming more of an issue and I suspect there will be a change with Android soon.
For those revs that have mDNS, but don't resolve .local, that is because they ignore the DNS server returned by DHCP and just use Google's 8.8.8.8 amd 8.8.4.4, therefore they can't resolve .local addresses.
There is a workaround:
Code:
Settings > WiFi> your WiFi network's entry.
Long-Tap the entry, chose to edit.
Activate Advanced settings
Switch from DHCP to static, and replace the first DNS server
(usually 8.8.8.8 ) with your own (your router, or the default ip for Moode AP)
Save
Now Android should use your DNS server first, and switch to the secondary
only if yours cannot resolve. Which means "moode.local" should now be found
Last edited:
Works fine on my iPad v4 (A1458) running iOS 9.3.1 with Safari, Chrome, and Dolphin.
Aha! Success!
Mpdas needs to have MPD running, so adding the systemctl start mpdas to the worker solves the startup problem and its scrobbling away
So what did I do?...
I followed your instructions - worked perfectly, except wget - I used:
Code:
wget [url]https://github.com/hrkfdn/mpdas/archive/0.4.1.tar.gz[/url]Which I got from the AUR repository: https://aur.archlinux.org/packages/mpdas/
Hi Steve,
Ok looks like its assigned to card 1 correctly.
What is output from the following cmds:
1) cat /proc/asound/card0/id
2) cat /proc/asound/card1/id
3) amixer -c 1
Regards,
Tim
Hi,
Very odd. The symptoms suggest either a bad sd card or network issues, something external to Moode software.
I would run a 30 sec ping test from Pi to your router and then examine the ping stats for %packet loss, long round trip times, dropped packets, etc.
This post provides a bit of info on how MPD and ALSA handle bit-depth.
http://www.diyaudio.com/forums/pc-based/271811-moode-audio-player-raspberry-pi-268.html#post4695445
-Tim
The Resonance FM stream link no longer works.
Correct one is http://stream.resonance.fm:8000/resonance
Cheers,
Phil
Correct one is http://stream.resonance.fm:8000/resonance
Cheers,
Phil
Hi Tim,
Output below;-
pi@moode:~ $ cat /proc/asound/card0/id
ALSA
pi@moode:~ $ cat /proc/asound/card1/id
M20
pi@moode:~ $ amixer -c 1
amixer: Mixer hw:1 load error: Protocol error
Many thanks
Steve
Hey Tim...
Using 2.6 TR2 and everything works great, and thanks for adding the file playback info below the artwork window!
Still getting clicks on 24/96k+ files - setting re-sample to 48k fixes this. I get the same thing on all Pi3 MPD players I've tried, so it's probably not a Moode thing.
Feature request: very minor, but it would be nice to have a Refresh button on the top bar. Maybe a Moode logo in the upper left that would refresh the player if clicked...? Just a thought.
Using 2.6 TR2 and everything works great, and thanks for adding the file playback info below the artwork window!
Still getting clicks on 24/96k+ files - setting re-sample to 48k fixes this. I get the same thing on all Pi3 MPD players I've tried, so it's probably not a Moode thing.
Feature request: very minor, but it would be nice to have a Refresh button on the top bar. Maybe a Moode logo in the upper left that would refresh the player if clicked...? Just a thought.
Hi Steve,
The error indicates that ALSA is not able to successfully read the DAC's device descriptor and load its mixer control information. I did a bit of searching and found a couple of references for the error but nothing in terms of a fix or bug report.
Regards,
Tim
Hi Phil,
Try these cmds to show the addresses that DHCP configured for name server and gateway on the Pi.
cat /etc/resolv.conf
ip route show
-Tim
Hi,
Interesting. After a quick search it appears that MPD's implementation of shuffle play may be lacking. I'll add to my TODO list to investigate.
-Tim
Hi,
Some excellent Classical stations (plus Jazz) added to Moode 2.6 courtesy of diyAudio member TheOldPresbyope. Thx Kent
WBJC Baltimore - Classical
WCLV Cleveland - Classical
WCRB Boston - Classical
WFMT Chicago - Classical
WQED Pittsburgh - Classical
WRTI Philadelphia - Classical
WRTI Philadelphia - Jazz
-Tim
Some excellent Classical stations (plus Jazz) added to Moode 2.6 courtesy of diyAudio member TheOldPresbyope. Thx Kent
WBJC Baltimore - Classical
WCLV Cleveland - Classical
WCRB Boston - Classical
WFMT Chicago - Classical
WQED Pittsburgh - Classical
WRTI Philadelphia - Classical
WRTI Philadelphia - Jazz
-Tim
Attachments
Hi,
I'm testing a solution named 'ashuffle' that appears to work nicely, at least from the cmd line. It might be a possible to integrate something like this.
Automatic shuffle
https://github.com/Joshkunz/ashuffle
I'm using it in its second mode where it continuously adds a random track to the end of the Playlist after the last track ends. If consume mode is turned on then you get random play without the Playlist growing. Interesting.
Regards,
Tim
Are you planning to update to mpd 0.19.15 from my understanding this update
master/mpd.git -
has enabled hls support
https://forum.musicpd.org/viewtopic.php?f=11&t=3748#p5809
Also i am experiencing a bug with current stable moodeaudio.
I am having a poor internet connection and when i am playing a radio if internet is too slow and the music stalls because of the stream. moode keeps displaying the radio playing by updating the time and after that it is impossible to add a song or clear the playlist.
master/mpd.git -
has enabled hls support
https://forum.musicpd.org/viewtopic.php?f=11&t=3748#p5809
Also i am experiencing a bug with current stable moodeaudio.
I am having a poor internet connection and when i am playing a radio if internet is too slow and the music stalls because of the stream. moode keeps displaying the radio playing by updating the time and after that it is impossible to add a song or clear the playlist.
I've just replicated this on another SD card with a Pi Zero and USB Wifi.
Flash Moode 2.6 TR2 onto SD card.
Create moodecfg.txt as per documentation with correct ssid and password.
Boot the Pi and it comes up, gets the IP address from DHCP server, but there are no entries in resolv.conf and DNS resolution from the Pi Zero fails.
Easily fixed by manually setting the wireless adapter's IP address as static from Moode's network config page, then setting it back to DHCP.
Cheers,
Phil