Before:
Code:
pi@moode:~ $ uname -a
Linux moode 4.1.19-v7+ #858 SMP Tue Mar 15 15:56:00 GMT 2016 armv7l GNU/Linux
pi@moode:~ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 1537808 1158260 288560 81% /After:
Code:
pi@moode:~ $ uname -a
Linux moode 4.4.8-v7+ #880 SMP Fri Apr 22 21:55:04 BST 2016 armv7l GNU/Linux
pi@moode:~ $ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 1537808 1182592 264228 82% /My test case file is still playing without L/R-swapping after 20 minutes.
Might as well delete the backup directory /boot.bak as well, although it's small.
Regards,
Kent
Hi Daniel,
Static IP addr worked on my network, no issues. Are u sure the address you entered is not already assigned?
-Tim
Hi,
Radio station logo is linked to station through a sql table. U could copy logo image to the radio-logos folder but without the sql link only the default radio station cover will be displayed. My TODO list has "need UI and maint for station logos". Eventually I'll get to it.
-Tim
Hi Kent,
Ok great. My tests earlier today with 4.4.8 also yielded no channel swapping so "case closed" as they say.
Regards,
Tim
Hi,
I've never logged in as root on moodeOS (Jessie), only as pi/raspberry. I did a bit of research and it looks like root logon using password as authentication is effectively disabled. Only pubkey auth is allowed for root.
openssh - What does 'without password' mean in sshd_config file? - Ask Ubuntu
-Tim
Tim,
The USB work around worked great! Now all my music files play without resampling turned on. Thanks for the help and for a great program. Moode is the best and most versatile of all the audio players I've have tried.
Barry
Just tried 2.6 TR1 on my Pi3 eager to try the new wifi setup.... It does not work for me.
Can connect to "moode" with "moodeaudio" password fine.
Cannot connect with Chrome browser on my Nexus 4.... I get a "connection refused" error.
J.
Hi J,
AFAIK Android does not support multicast DNS (mDNS and the .local domain) which is required by hostapd thus "http://moode.local" will not resolve.
Try http://172.24.1.1
Thats the ip address of the access point.
Regards,
Tim
Last edited:
Hi Tim,
I've tried Max2play before as I have run Squeezeplayers for multi-room audio and managed to access their fixed address for the Pi from Android devices.
Is it possible to see how they have managed to get around this DNS issue?
Just an idea.
Thanks for 2.6 BTW, I've just updated and will be trying it out in work tomorrow with my Noble Audio K10s!
Sent from my LG-D855 using Tapatalk
Hi,
If by "fixed address" u are referring to ip address, then yes thats the only way I know of to access hostapd if client does not support .local (mDNS).
hostapd in Moode is at 172.24.1.1
-Tim
Hi,
Below is bugfix list (so far) for Moode 2.6 TR1.
BUG: NFS mount fails because rpcbind not enabled at boot
FIX: add systemctl enable rpcbind to OS build recipe
BUG: Ext4 file system fails to auto-mount
FIX: add ext4 filter to /etc/udisks-glue.conf
BUG: Channel swap can occur when Pi 3 + I2S + 16 bit audio
FIX: bump to kernel 4.4.8 which contains fixes for this issue
-Tim
Below is bugfix list (so far) for Moode 2.6 TR1.
BUG: NFS mount fails because rpcbind not enabled at boot
FIX: add systemctl enable rpcbind to OS build recipe
BUG: Ext4 file system fails to auto-mount
FIX: add ext4 filter to /etc/udisks-glue.conf
BUG: Channel swap can occur when Pi 3 + I2S + 16 bit audio
FIX: bump to kernel 4.4.8 which contains fixes for this issue
-Tim
Radio streams to add to moOde?
Tim,
First off, thanks for all the work you put into moOde - after playing with and testing most of the other Rpi music solutions out there, moOde had become my daily use program.
I wanted to add some radio station links, all of which should be direct links (confirmed via wireshark logs). They are all 160 or 192 - ambient, post-rock, drone and similar genres. They have been playing reliably by manually adding them.
Anything you can do to add them to the moOde radio library is appreciated. If you need specific information on the streams, I can pull more information using wireshark - I am more than willing to help out in any way.
Again, thanks for your extraordinary effort on moOde. The results so far are stellar.
Phil
Tim,
First off, thanks for all the work you put into moOde - after playing with and testing most of the other Rpi music solutions out there, moOde had become my daily use program.
I wanted to add some radio station links, all of which should be direct links (confirmed via wireshark logs). They are all 160 or 192 - ambient, post-rock, drone and similar genres. They have been playing reliably by manually adding them.
- 6forty radio - http://54.173.171.80:8000/6forty
- FarPastPost - http://streaming.radio.co:80/sbfe60794e/listen
- Maschinengeist Radio - http://i.20hz.biz:8000/maschinengeist.org.192.mp3
- Ambient Sleeping Pill - http://50.7.96.138:8379/stream
Anything you can do to add them to the moOde radio library is appreciated. If you need specific information on the streams, I can pull more information using wireshark - I am more than willing to help out in any way.
Again, thanks for your extraordinary effort on moOde. The results so far are stellar.
Phil
Last edited:
Hi Phil,
Thanks for the compliment! Great set of stations Btw. Will add to TR2
-Tim
Sorry no I meant "http://max2play/" to log into the Web GUI for configuration.
Sent from my LG-D855 using Tapatalk
Sterling effort Tim – thanks very much for continuing to develop Moode.
I tend to use Moode as a UPnP renderer interacting with Minimserver on my NAS and Linn’s Kazoo as a control point. I’ve noticed that with version 2.6 (TR 1) things are different for this OpenHome platform in that regardless of what might be assigned to Moode’s 'friendly UPnP name', Kazoo continues to inform that the Pi’s OpenHome name is ‘Main Room’.
As far as I can tell this is due to how OpenHome has now been implemented on the excellent app ‘upmpdcli’. I’m no techie and I very much suspect that there’s very good reasons why this change has occurred. In my setup, for instance, I no longer need to run BubbleUPnP server for my Pi to be seen on Kazoo as an OpenHome renderer called ‘Main Room’. However, in my humble opinion it would be great if there was some way of changing this name on Moode. This would enable a consistent naming approach and it should also help to avoid any potential confusions for those with multiple devices running Moode – surely, several instances of Moode running at the same time can’t all have an OpenHome renderer name called ‘Main Room’! This Limitation is recognised by the developer of upmpdcli who offers a solution to the issue, as per the comment posted on the 14th March on this page: https://github.com/medoc92/upmpdcli/issues/30
Nb - for those who may not know, recently Linn has put considerable effort into developing Kazoo, which is now an exceptionally good control point + if you run BubbleUPnP server it’s possible to access Tidal and Qobuz from the app. (The latter is also the case with the Lumin control app).
I tend to use Moode as a UPnP renderer interacting with Minimserver on my NAS and Linn’s Kazoo as a control point. I’ve noticed that with version 2.6 (TR 1) things are different for this OpenHome platform in that regardless of what might be assigned to Moode’s 'friendly UPnP name', Kazoo continues to inform that the Pi’s OpenHome name is ‘Main Room’.
As far as I can tell this is due to how OpenHome has now been implemented on the excellent app ‘upmpdcli’. I’m no techie and I very much suspect that there’s very good reasons why this change has occurred. In my setup, for instance, I no longer need to run BubbleUPnP server for my Pi to be seen on Kazoo as an OpenHome renderer called ‘Main Room’. However, in my humble opinion it would be great if there was some way of changing this name on Moode. This would enable a consistent naming approach and it should also help to avoid any potential confusions for those with multiple devices running Moode – surely, several instances of Moode running at the same time can’t all have an OpenHome renderer name called ‘Main Room’! This Limitation is recognised by the developer of upmpdcli who offers a solution to the issue, as per the comment posted on the 14th March on this page: https://github.com/medoc92/upmpdcli/issues/30
Nb - for those who may not know, recently Linn has put considerable effort into developing Kazoo, which is now an exceptionally good control point + if you run BubbleUPnP server it’s possible to access Tidal and Qobuz from the app. (The latter is also the case with the Lumin control app).
Last edited:
I must read instructions properly.... I couldn't get it to work from the phone (I'd misread the IP address as 174.4.1.1 - ho-hum!).
Used a Laptop instead.... Debian Jessie with iceweasel got it working fine.
J.
Hi,
Sure, I'll add "ohproductroom = " to the config file and set it to same as "friendlyname =". That should do the trick
-Tim