Moode Player Help

[TimCurtis]

MoOde 2.7 up and running here. Painless and working fine... Thanks Tim

Hi Grant,

Glad to hear that :-)

-Tim

[Aligauld]

Hi Tim,
Just a wee note and thanks.
With your instructions the updater successfully updated 2.6.to 2.7. The Kernel update went smoothly and all is working beautifully

Cheers,
Alistair

[struth]

Just one point on new moode 2.7 Tim... Using ios ipad i have noticed that if i leve the browser page when moode is playing, say to read something and track changes, when i go back to moode the now playing info is a track behind. If i then say adj or touch vol it jumps back to last track showing. Doesnt do it with android.

[PeAK]

Hi,

Moode Audio Player release 2.7 is available for download at moodeaudio.org :-)

This release includes a new in-place software updater, Crossfeed DSP for headphone listening, support for Meridian Explorer 2 and MQA format, a universal rotary encoder driver that updates Moode volume knob and supports both hardware and software volume, some really great commercial-free, listener-supported radio stations, support for exciting new I2S audio devices, and numerous important updates and bug fixes.
.
.
.

Hi Tim,
Pretty neat to implement the Access Point feature to gain a simple elegant solution to allow a simple tablet control the Moode Music Player and doing away with the wi-fi router (an another box, to boot). The problem is the later solution (i.e.using an external wi-fi router) sounds better. I suppose part of the problem is the AP protocol that requires it to constant broadcast the availability SSID of the Pi to all potential tablets that wish to be a client. You can see this on my particular setup by a flashing LED that is flashing constantly in AP mode.

When the Pi's wi-fi dongle is configured to not be an AP, the LED comes only about once every 10 seconds.

Any chance you could consult with the AP code contributors to see if there is a way to quiet down that broadcasting activity once a connection is in place. I'm sure that bulk of people using this AP have only a single client (i.e. tablet) acting as a fancy remote control.

...just in case your team isn't too busy

Ray

[TimCurtis]

Hi Tim,
Pretty neat to implement the Access Point feature to gain a simple elegant solution to allow a simple tablet control the Moode Music Player and doing away with the wi-fi router (an another box, to boot). The problem is the later solution (i.e.using an external wi-fi router) sounds better. I suppose part of the problem is the AP protocol that requires it to constant broadcast the availability SSID of the Pi to all potential tablets that wish to be a client. You can see this on my particular setup by a flashing LED that is flashing constantly in AP mode.

When the Pi's wi-fi dongle is configured to not be an AP, the LED comes only about once every 10 seconds.

Any chance you could consult with the AP code contributors to see if there is a way to quiet down that broadcasting activity once a connection is in place. I'm sure that bulk of people using this AP have only a single client (i.e. tablet) acting as a fancy remote control.

...just in case your team isn't too busy

Ray

Hi Ray,

U can try changing the setting below in /etc/hostapd/hostapd.com

This link is useful
https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf

-Tim

# Send empty SSID in beacons and ignore probe request frames that do not
# specify full SSID, i.e., require stations to know SSID.
# default: disabled (0)
# 1 = send empty (length=0) SSID in beacon and ignore probe request for
# broadcast SSID
# 2 = clear SSID (ASCII 0), but keep the original length (this may be required
# with some clients that do not support empty SSID) and ignore probe
# requests for broadcast SSID
ignore_broadcast_ssid=0

[PeAK]

Hi Ray,

U can try changing the setting below in /etc/hostapd/hostapd.com

This link is useful
https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf

-Tim

# Send empty SSID in beacons and ignore probe request frames that do not
# specify full SSID, i.e., require stations to know SSID.
# default: disabled (0)
# 1 = send empty (length=0) SSID in beacon and ignore probe request for
# broadcast SSID
# 2 = clear SSID (ASCII 0), but keep the original length (this may be required
# with some clients that do not support empty SSID) and ignore probe
# requests for broadcast SSID
ignore_broadcast_ssid=0

I tried out the option with ignore_broadcast_ssid=1 and found that it does hide the SSID but the number of
"beacons" numbers roughly 400 within a minute interval.

Did some digging and found that the "hostapd" daemon
can have the "beacon interval" (beacon_int).

Here is a description from http://wiki.openwrt.org/doc/uci/wireless

MAC80211 Device Options:

Name: beacon_int
Type: integer
Required: no
Default: 100 (hostapd default)

Description:
Set the beacon interval. This is the time interval between beacon frames, measured in units of 1.024 ms. hostapd permits this to be set between 15 and 65535. This option only has an effect on ap and adhoc wifi-ifaces.

The range for "beacon_int" is anywhere from 15 to 65,535 units of 1ms (i.e. 15 ms to 65 seconds): I think something like a ten second (beacon_int=10,000) beacon interval would work for me.
I think the default is currently set to about 100ms.

Should be something straightforward to sort in a couple of days...thanks for your help, earlier.

Ray

[Update:]

beacon_int=1000 was added to /etc/hostapd/hostapd.conf and had the intended effect of decreasing the number of sent beacons to one every second.

When larger values (beacon_int=9000) were used, the intended effect of a beacon every 9 seconds, did not take. Instead it seems as if some sort of
internal limiting limits the sending of beacons to no more that once per second ???

Anyone out there familiar with "the other parameters" in the hostapd.conf file that might work around this limitation ?

Thanx in advance.

[PeAK]

Hi Marc,

(1) All that u mentioned including custom compiles of MPD, shairport-sync, upexplorer, etc, a bunch of OS stuff deleted or turned off, custom dir structures and permissions for certain things, custom udev rules, alsa config and the list goes on! The distro could probably be made from stock Raspbian by cloning a Github repo and then running scripts to compile and configure everything, but developing, debugging and maintaining install scripts would probably be more work than Moode itself :-)

(2) Moode 2.4 is a vast improvement over the code that I started with way back in 2014, but the 2.5 rewrite I'm currently working on is as radical as it can get with 2.x, everything is being overhauled and with particular attention to improved performance :-)

(3) The orion script (kernel tweak) does not exist anymore for 2.5. The service kills in the script are moved into main PHP worker and the scheduler tweeks not incorporated. There are several old legacy components that are not really needed anymore.

Regards,
Tim

Hi Tim,
I've only recently moved over to Moode from the RuneAudio player. I've been perusing this thread in hopes of not having to bother you again. The above post was from December of 2015...yes...a while back!

First, overall, the Moode menus seem to be more streamlined than those found on RuneAudio. I typically rip my music to USB Keys and prefer to play them that way for sound quality reasons. However, I cannot find a menu to unmount a mounted USB key. Is it safe to just pull the USB key out and plug in another USB key full of music ? These options existed in the other player.

Second, I was curious as to the removal of the Orion script/kernel tweak (aka as Orion or ACX latency settings). I really thought there was an audible difference between them and you did indicate that you prefererred one setting over the other. I thought the intent with the filters was to put them "out there" and to then narrow them down to the preferred setting. Was this done in a "formal" way so that it was decided to remove this choice. In the RuneAudio player, there were a choice of five settings.

P.S. Your earlier hint to alter AP settings in the hostapd.conf file was helpful. I really do prefer the "sound" with a longer "beacon interval" of one second versus 0.1 seconds.

Thanks for pursuing and sharing the evolution of this player,
Ray

[TimCurtis]

Hi Tim,
I've only recently moved over to Moode from the RuneAudio player. I've been perusing this thread in hopes of not having to bother you again. The above post was from December of 2015...yes...a while back!

First, overall, the Moode menus seem to be more streamlined than those found on RuneAudio. I typically rip my music to USB Keys and prefer to play them that way for sound quality reasons. However, I cannot find a menu to unmount a mounted USB key. Is it safe to just pull the USB key out and plug in another USB key full of music ? These options existed in the other player.

Second, I was curious as to the removal of the Orion script/kernel tweak (aka as Orion or ACX latency settings). I really thought there was an audible difference between them and you did indicate that you prefererred one setting over the other. I thought the intent with the filters was to put them "out there" and to then narrow them down to the preferred setting. Was this done in a "formal" way so that it was decided to remove this choice. In the RuneAudio player, there were a choice of five settings.

P.S. Your earlier hint to alter AP settings in the hostapd.conf file was helpful. I really do prefer the "sound" with a longer "beacon interval" of one second versus 0.1 seconds.

Thanks for pursuing and sharing the evolution of this player,
Ray

Hi Ray,

The USB auto-mounter (udisks-glue) automatically mounts and unmounts USB storage devices. No need to run any Linux commands.

The "kernel tweaks" were from the original OS that hosted the player. They along with some other things were removed during the 2.5 rewrite as part of an overall effort to simplify the code base. Moode 2.7 runs on a completely new OS (moodeOS) that is based on Raspbian Jessie-Lite. Stock kernel settings are used which, based on the absence of any user reports to the contrary, seem to be working well.

-Tim

[mikeyb]

I'm currently playing (fighting) with a Vanaplayer using the Sparky (RPi Clone), do you think MoOde could be made to run on it, I've tried latest version but nothing shows up when I look for it via Fing WiFi search or via IP Address?

[TimCurtis]

I'm currently playing (fighting) with a Vanaplayer using the Sparky (RPi Clone), do you think MoOde could be made to run on it, I've tried latest version but nothing shows up when I look for it via Fing WiFi search or via IP Address?

Hi,

Moode supports Raspberry Pi family of boards and Raspbian OS.

-Tim