moOde release 4.1

[swizzle]

It's a Raspberry Pi 1B, and there is not connected any devices at all.

The sound is transferred via HDMI to my surround receiver, and the Pi is connected via wired network. Airplay and Squeezelite is On, other renderes is Off.

Looks like this is happening when a Squeezelight (or AirPlay or BT) session is active, I think because those page elements aren’t relevant then? If an element is dimmed you think shouldn’t be then let us know which and why.

[erlingt]

Ok, I tried turning the renderes Off and On. 

It looks like it is the Squeezelite that turns the dimming on. If I turn Squeezelite Off the dimming disappears. Turning Airplay On/Off has no influence on the dimming.

I can see, that it is fine, with the dimming when using Airplay or Squeezelite, because the elements that is dimmed is not in use. But unfortunately the dimming is also in effect, when playing "local" files from a NAS source.

/Erling

[Tim Curtis]

The dimming is to indicate that Airplay, Bluetooth or Squeezelite is active. There are differences in how these renderers behave.

1. Airplay is session based. This means that the Airplay renderer can be left turned on in Audio config and will only take over playback when and Airplay client starts playing something. **Dim UI only when client is playing.

2. Bluetooth is connection based. This means that the Bluetooth renderer takes over playback as soon as a Bluetooth client connects regardless of whether its playing anything. **Dim UI when client connects. MoOde can also function as a Bluetooth client to a Bluetooth Speaker and in this case MPD remains the playback client and UI is left un-dimmed.

3. Squeezelite simply takes over playback as soon as it starts. **Dim UI when Squeezelite is turned on in Audio config. There is a timeout param for Squeezelite that will cause it to release the audio channel after N secs but it does not signal this event so no way for moOde to know that the audio channel is free again. Conversely Squeezelite does not signal when it starts playing again.

-Tim

[vuckozagi]

Can **Dim UI be removed for Squeezelite?

[Tim Curtis]

Whats the usage scenario?

When Squeezelite is turned on it blocks MPD from playing and thus the Playback screen is non-functional.

-Tim

[pinkdot]

Tim Curtis pid='754' dateline='1524397783']Whats the usage scenario?

When Squeezelite is turned on it blocks MPD from playing and thus the Playback screen is non-functional.

-Tim

The unwanted effect is that Squeezelite always dims the ui, whether it is switched on and playing, or when its switched on but MPD is playing. The latter is the situation where the controls are needed, but dimmed. 
   

[Tim Curtis]

Are u running Squeezelite with the -C idle timeout param?

-Tim

[pinkdot]

Just the standard options:

Code:

 S Q U E E Z E L I T E    S E T T I N G S  

    Version            = 1.8.7-1052 "DSD/SRC enabled"
    Friendly name        = AuneS6
    ALSA device        = hw:1
    ALSA params        = 120:4::1
    Output buffers        = 40000:100000
    Task priority        = 45
    Codec list        = flac,pcm,mp3,ogg,aac,alac,dsd
    Other options        = -W -D 500 -R E

[Tim Curtis]

With std options Squeezelite will hog the audio output. MPD is non-functional in this case.

[pinkdot]

With std options Squeezelite will hog the audio output. MPD is non-functional in this case.

Yes, that's why I have to 'switch off' the squeezelite player in an Android app or LMS web ui, before switching to MPD. But still the screen will be dimmed.