Moode Audio Player for Raspberry Pi

Jump to Latest
#7,581
Roller123 said:
Unfortunately, I can not see the previous version, since I wrote a new version on top of it. As I said, maybe the system does not define my USB device as audio. With other players (volumio) everything works well. When I try to select an audio device, I see only the standard device on the board and do not see the USB audio device. Previous version 3.0.
I found information that the information about devices by default is contained in the /etc/modprobe.d/alsa-base.conf file, but on your system this file is empty. Therefore, my question about the file, which contains such information.
Click to expand...

Hi,

Here are all the possible ALSA files on Raspbian Jessie

/usr/share/alsa/alsa.conf
/usr/share/alsa/alsa.conf.d/
/var/lib/alsa/asound.state
/etc/asound.conf (optional)
~/.asoundrc (optional)

-Tim
 
Last edited:
#7,582
belt250 said:
Audiophonics ES9023 using DIY I2S cable to connect with RPi 3B

b66d09ebd35c5a2423a883137fc55187.jpg
Click to expand...

Any chance of listing all the other components in that rig? You obviously took great pains in design and details. Thanks for sharing the photo.

energyman
 
#7,584
Intermittent Connection Failure

Hi Tim,

I recently moved to Moode 3.6 from Moode 3.5. I burned the 3.6 image to a fresh SD Card and configured it.

I have noticed something since using Moode 3.6. My modem is configured to assign a fixed IP to my RPi2B according to the MAC of the RPi. I switch off my modem each night. Under Moode 3.5, after starting the modem next morning, I could reliably connect to the RPi. With Moode 3.6, sometimes I cannot connect with my iPad or iMac. Restarting the modem or ethernet switch makes no difference. I have to reboot the RPi.

Do you know why this is happening? Is there anything I can do to ensure reliable reconnection to the RPi?

In addition, using Safari on my iMac, I can connect using the IP address, but cannot connect using moode.local - whereas on my iPad, I can connect with either moode.local or the IP address. Resetting Safari makes no difference. However if I use Firefox, I have no problem connecting either way. If I could always connect with moode.local, then I could forget about setting a static IP. This has been happening with both V3.5 and V3.6. Any thoughts on what is happening here?

Thanks, Rob
 
Last edited:
#7,585
sonatina said:
Hi Tim,

I recently moved to Moode 3.6 from Moode 3.5. I burned the 3.6 image to a fresh SD Card and configured it.

I have noticed something since using Moode 3.6. My modem is configured to assign a fixed IP to my RPi2B according to the MAC of the RPi. I switch off my modem each night. Under Moode 3.5, after starting the modem next morning, I could reliably connect to the RPi. With Moode 3.6, sometimes I cannot connect with my iPad or iMac. Restarting the modem or ethernet switch makes no difference. I have to reboot the RPi.
Thanks, Rob
Click to expand...

Same here..
.I have to reboot the RPi.
Click to expand...
Pi3 takes 2 boots to find the ip...I seem to recall that the IP check happened too fast in another iteration.... will go and look and get back to you..
 
#7,586
I just can't get this thing to work fully. Half the radio stations don't play and I keep getting a blank playback screen. It displays the controls and thats all. Refresh doesn't work, but the occasional reboot and the playback screen returns. Do you have to reboot every time you change whats playing? Do I need to do an update, even though I downloaded the latest?
 
#7,587
An externally hosted image should be here but it was not working when we last tested it.

Moode Audio Player is a derivative of the wonderful WebUI audio player client for MPD originally designed and coded by Andrea Coiutti and Simone De Gregori, and subsequently enhanced by efforts from the RaspyFi/Volumio projects.


Platform Information


  • An externally hosted image should be here but it was not working when we last tested it.
    ver: 1.1
  • Linux kernel: 4.4.30-v7+
  • Architecture: ARMv7l
  • MPD version: 0.19.19
  • Hdwr rev: Pi-2B 1GB
  • Thanks Mike
 
#7,589
DRONE7 said:
Same here.. Pi3 takes 2 boots to find the ip...I seem to recall that the IP check happened too fast in another iteration.... will go and look and get back to you..
Click to expand...

Hi Bob, @sonatina,

Very odd. Nothing changed wrt networking between 3.5 and 3.6 and I'm not seeing anything like this on my end, but I leave Router on 7/24 except for the nasty 5 day power outage back in March :-0 After power finally came back on though, all my Pi's came up no issues.

Is this happening with Std or just the Adv kernels?

To troubleshoot, after a failure case occurs, take a look at syslog and your Router/Modem logs for anything suspicious.

-Tim
 
#7,590
Hi,

User ElmarL sent me list of radio stations with non-working links. See below. I'll see if I can get good links for next update. If I'm not able to find links then the station will be removed.

If anyone has direct stream links for any of the stations, please email me 🙂

Absolute Radios (I think this is geo-blocked outside the UK)
Addicted to Radio - Blues Classics
Ambient Sleeping Pill
EuroRadioJazz (all 3 listed stations)
Farpastpost
FM106
KWAX Classic
La Premiere
Mad Music Asylum
Musiq 3
Phases Radio
RMC 1
Radio X Brussels (noise/signal, no music)
Rinse FM
Rock FM
Smooth Jazz Global Radio
SomehowJazz
Triple J Unearthed
Triple J
UCFM
WFMT
WRTI Philadelphia

I've confirmed that the two stations below are no longer broadcasting.

Ann Channel Detroit
Classic and Jazz

-Tim
 
#7,592
Switch on/off amplifier

Hello,

I tried to search for my problem - but as this thread is so huge, i wasn't sucessfull.
So I hope you are patient with me...

I am using Moode 3.6 - works fine.
Now i would like to use it with two amplifiers for different rooms. And i would like to switch between them.
I would like to control both amplifies from the Moode UI.
And i think i would by some relayboard to switch the amps by GPIO.

Has anyone already done this?
And if yes, what do I have to adapt in the web UI? As I am not familiar with JS I think, that this is the most comlicated part.

Any links or tutorials are welcome!

Thank you
Vogi
 
#7,597
@Soldeed,

I've seen these messages with m4a (ALAC) format. The link below suggests the message is thrown when ffmpeg reaches an internal time limit as its scanning a Variable Bit Rate song file to determine its duration.
https://www.mail-archive.com/get_iplayer@lists.infradead.org/msg02724.html

I don't see these messages though with Variable Bit Rate FLAC format files. Possibly FLAC stores the duration as a metadata element and m4a does not, or maybe a bug in ffmpeg.

-Tim
 
#7,598
TimCurtis said:
Hi Vogi,

Moode is not really designed to be used in shared Kiosk type scenarios where there is a need for access control and login or landing pages. Its too narrow a usage scenario for me to devote time to code and support it.

-Tim
Click to expand...

Hi Tim,

thanks to some hints here in the forum, I found a good working solution.

Restricted Acces to Config Pages:
Added the following to /etc/nginx/nginx.conf:
Code: 
            location ~ /(apl|mpd|net|snd|sqe|src|sys)\-config.php$ {
                satisfy any;
                allow 192.168.10.0/24;
                deny all;
                auth_basic "Konfigurationsbereich";
                auth_basic_user_file /etc/nginx/htpasswd;
                fastcgi_pass unix:/var/run/php5-fpm.sock;
                fastcgi_param SCRIPT_FILENAME $request_filename;
                fastcgi_read_timeout 600000;
                include fastcgi_params;
            }
This allows access to config pages only from my private subnet (192.168.10.x). In other nets, a password is required.

Catch-All WLAN:
First I tried with the built in AP feature - it worked, but my USB WLAN device had very poor performance. So I did it with a VLAN, as my router runs on OpenWRT:

Modiefied /etc/network/interfaces:
Code: 
auto eth0
iface eth0 inet dhcp
post-up ifup eth0.14

auto eth0.14
iface eth0.14 inet static
address 192.168.1.10
netmask 255.255.255.0
My VLAN eth0.14 doesn't provide internet access.
On the OpenWRT device the running dnsmasq alway serves the Rasperry IP by adding
Code: 
address=/#/192.168.1.10
Additionally I disbaled DHCP client for the VLAN as it still requested a second address, by adding
Code: 
denyinterfaces eth0.14
to /etc/dhcpcd.conf

Maybe this is interesting for others, too

Greetings
Vogi
 
#7,599
Zootalaws said:
Nano is part of the standard build. Just exec 'sudo nano filename ' and you should be in - there are hints on screen for saving, searching, etc.

Can't confirm or deny the likelihood of SD card being at fault, but when you do have a slow or dodgy card, all manner of odd behaviour occurs 🙂 Prolly worth swapping with a name-brand class 10 card to see.

Good to see the accented file names aren't a problem - I wasn't sure that it was, but worth a crack.
Click to expand...

Thanks for this. I was able to run nano and get a look at the log files. An error message caught that one of my files was corrupted. When I looked in the Moode > Library panel, I saw that the corrupted file was not displayed. I guess MPD didn't add it to its database. That made me think about data corruption. I'll have to swap out the sdcard for a different one to see if the one I have is defective in some way.

Is there a way to test the sdcard?

Also, am I inviting problems trying to store all my music files on the sdcard along with the OS? I've read posts from other users saying they have thousands of tracks stored on various media (NAS, USB thumb drives, etc.) but I haven't seen anyone saying they're using a microSDXC card both to run Moode and store all the music. Maybe that's not a good way to use a pi w/ Moode?

Incidentally, the sdcard I'm using is a Sandisk 128GB microSDXC. This one:
https://www.amazon.com/SanDisk-microSDXC-Standard-Packaging-SDSQUNC-128G-GN6MA/dp/B010Q57S62

--

Errors from two files that are not recognized:

Apr 30 17:33 : ffmpeg/flac: Could not find codec parameters (Audio: flac, 0 channels)
Apr 30 17:33 : ffmpeg/flac: Estimating duration from bitrate, this may be inaccurate
Apr 30 17:33 : update: ignoring unrecognized file SDCARD/Thad Jones-Mel Lewis Orchestra/14. Polka Dots And Moonbeams.flac
Apr 30 17:33 : update: reading SDCARD/Thad Jones-Mel Lewis Orchestra/15. Mornin' Reverend.flac
Apr 30 17:33 : flac: Failed to read FLAC tags: FLAC__METADATA_CHAIN_STATUS_NOT_A_FLAC_FILE
Apr 30 17:33 : flac: Failed to read FLAC tags: FLAC__METADATA_CHAIN_STATUS_NOT_A_FLAC_FILE

This happened before to a different set of tracks. I left the pi sitting powered on for a day, and ran the Update MPD DB again. Then the files were recognized and added to the database.

This kind of now you see it, now you don't behavior feels reminiscent of dying hard drives. Does it sound like a failing sdcard to you?
--
 
Last edited:
#7,600
Strange behavior...

On Friday, I had copied two artists and five albums to the sdcard.

I ran Update MPD DB. The Browse panel changed to Updating with the two spinning arrows. It was stuck there.

I went away for Saturday, so I left the pi running while I was away.

This morning (Sunday) I looked in the Moode Library and saw that the Browse panel was back to Browse. One artist and two of his albums had been added. It took a day to do that?

I looked in mpd.log and the one artist and two albums were reported added. But the first artist's third album, and second artist and his two albums were not mentioned at all.

So I shutdown/rebooted the pi, re-ran Update MPD DB. Again the Browse panel changed to Updating (with spinning arrows) and stayed that way. I checked in the Library and nothing had changed.

I left the pi running for another hour, and checked back. The third album of the first artist and the second artist and his two albums had now appeared in the Library.

It seems very slow to update after copying music over to the sdcard. Does that behavior sound like something's wrong? Does it normally take Update MPD a long time to scan and add files? Or should it take a few seconds at most?

--
 
You must log in or register to reply here.
Top Bottom