[PROBLEM] Volume going back to 0% by itself

[Sander]

I have an I2S device with hardware volume.
When switching from Spotify to MPD, the volume is going back to 0% even though I set it to 100 in the config.
When re-checking the config when this happened, it is back at 0% again.

moodeutl -l output:

Code:

20191016 205647 worker: -- Start
20191016 205648 worker: Successfully daemonized
20191016 205648 worker: Integrity check (passed)
20191016 205648 worker: Session loaded
20191016 205648 worker: Debug logging (off)
20191016 205649 worker: ALSA volume set to (0%)
20191016 205649 worker: -- System
20191016 205653 worker: Host name     (moode)
20191016 205653 worker: moOde release (6.3.0 2019-10-02)
20191016 205653 worker: Raspbian OS   (10.1)
20191016 205653 worker: Linux kernel  (4.19.75-v7+ #1270)
20191016 205653 worker: Platform      (Pi-2B 1GB v1.1)
20191016 205653 worker: Architecture  (armv7l)
20191016 205653 worker: MPD version   (0.21.15)
20191016 205653 worker: CPU governor  (ondemand)
20191016 205653 worker: USB boot not available
20191016 205653 worker: File system expanded
20191016 205653 worker: HDMI port off
20191016 205654 worker: File check (OK)
20191016 205654 worker: -- Network
20191016 205654 worker: eth0 exists
20191016 205654 worker: eth0 (10.20.30.54)
20191016 205654 worker: wlan0 does not exist
20191016 205654 worker: -- Audio
20191016 205655 worker: ALSA outputs unmuted
20191016 205655 worker: ALSA card number (0)
20191016 205655 worker: Audio output (I2S audio device)
20191016 205655 worker: Audio device (IQaudIO Pi-DAC+)
20191016 205656 worker: Supported audio formats (S16_LE, S24_LE, S32_LE)
20191016 205656 worker: ALSA mixer name (Digital)
20191016 205656 worker: MPD volume control (hardware)
20191016 205657 worker: Hdwr volume controller exists
20191016 205657 worker: -- Services
20191016 205657 worker: Reset renderer active state
20191016 205657 worker: MPD conf updated
20191016 205658 worker: MPD started
20191016 205701 worker: MPD accepting connections
20191016 205701 worker: Configure MPD outputs
20191016 205701 worker: MPD output 1 ALSA default (off)
20191016 205701 worker: MPD output 2 ALSA crossfeed (off)
20191016 205701 worker: MPD output 3 ALSA parametric eq (on)
20191016 205701 worker: MPD output 4 ALSA graphic eq (off)
20191016 205701 worker: MPD output 5 ALSA polarity inversion (off)
20191016 205701 worker: MPD output 6 ALSA bluetooth (off)
20191016 205701 worker: MPD output 7 HTTP stream (off)
20191016 205701 worker: MPD crossfade (off)
20191016 205701 worker: Audio source (Local)
20191016 205701 worker: Output device (Local)
20191016 205702 worker: Spotify receiver started
20191016 205702 worker: Shellinabox SSH started
20191016 205702 worker: USB auto-mounter (udisks-glue)
20191016 205702 worker: -- Music sources
20191016 205702 worker: USB sources (none attached)
20191016 205703 worker: NAS and UPnP sources (mountall initiated)
20191016 205703 worker: -- Miscellaneous
20191016 205703 worker: Saved MPD vol level (0)
20191016 205703 worker: Preamp volume level (0)
20191016 205703 worker: MPD volume level (0) restored
20191016 205703 worker: ALSA volume level (0%)
20191016 205703 worker: Auto-play (Off)
20191016 205703 worker: Maintenance interval (6 hrs)
20191016 205703 worker: Screen saver activation (Never)
20191016 205703 worker: Session permissions (OK)
20191016 205703 worker: Watchdog started
20191016 205703 worker: Ready
20191016 205752 worker: Job alsavolume

[Tim Curtis]

The ALSA volume setting in Audio Config just represents the current ALSA level. It's not persistent.

In upcoming moOde 6.3.1 update I've changed it to "Max ALSA volume" which is persistent and represents the ALSA volume level that is used to set 0dB when MPD volume control is set to Software or Disabled, or when any of the Audio Renderers are active.

[Norbert]

=> I have an I2S device with hardware volume.

I have a similar effect with the AMP2. It also runs with hardware volume control.

If I switch to a USB DAC as a test (Audioquest Dragonfly, also with hardware control) and then go back to I2S I have first to select software volume, reboot, and then back to hardware volume. Then it works (for ever).

But not really a problem, do not do that so often ..

Regads
Norbert