moOde 5 Beta 1

[swizzle]

I can confirm the problem with auto-shuffle.

Pffff….for a moment I thought I was getting crazy...
Old yes, but crazy? pffff….

Is there a lesson to be learned here? I think so. Give all the details of a problem in the first message.

Can you guys try it with the older version of mpd (20.20 or whatever is selectable in the audio settings to work around a Bluetooth bug).

[JST1963]

Saving the MPD settings also changes the ALSA volume settings back to 100%

This can be very painful for my ears

I think that, whatever you put in the ALSA volume, should stay there, no matter what, until you manually change it...

ALSA Volume setting will go back to 100% after saving MPD settings

BTW: restarting MPD service does not change this setting.

[Tim Curtis]

@swizzle its a bug in the 'next' event handler. Already fixed :-)

[Tim Curtis]

Saving the MPD settings also changes the ALSA volume settings back to 100%

This can be very painful for my ears

I think that, whatever you put in the ALSA volume, should stay there, no matter what, until you manually change it...

ALSA Volume setting will go back to 100% after saving MPD settings

BTW: restarting MPD service does not change this setting.

When MPD volume is set to "Disabled" i.e., 0dB and the device has a hardware volume controller then ALSA volume is set to 100% to ensure that the overall volume output (MPD + ALSA) is 0dB. This also happens when resuming MPD playback after the renderers.

This is not a new behavior. It's been this way for years.

[JST1963]

I can confirm the problem with auto-shuffle.

Pffff….for a moment I thought I was getting crazy...
Old yes, but crazy? pffff….

Is there a lesson to be learned here? I think so. Give all the details of a problem in the first message.

Can you guys try it with the older version of mpd (20.20 or whatever is selectable in the audio settings to work around a Bluetooth bug).

Switching back from MPD 0.21.5 to MPD 0.20.20, regenerating the database, rebooting the whole system and clearing cache, I still have the same issue...

[JST1963]

Saving the MPD settings also changes the ALSA volume settings back to 100%

This can be very painful for my ears

I think that, whatever you put in the ALSA volume, should stay there, no matter what, until you manually change it...

ALSA Volume setting will go back to 100% after saving MPD settings

BTW: restarting MPD service does not change this setting.

When MPD volume is set to "Disabled" i.e., 0dB and the device has a hardware volume controller then ALSA volume is set to 100% to ensure that the overall volume output (MPD + ALSA) is 0dB. This also happens when resuming MPD playback after the renderers.

This is not a new behavior. It's been this way for years.

I understand, but isn't there a possibility that this parameter does not change after saving MDP, or any other renderer setting?
I set it at 80% and if all of a sudden it goes back to 100% it could not only harm my HP, but more importantly my precious ears.
It should be possible to force it always back to the value that was entered in this field, no?

Johan

[Tim Curtis]

Playback History is cool when you want to see what played in the near past.
What I don't like however are the entries of the radiostations. Each time a station changes the RDS info, an entry is written in the playback history. That implies several lines are identical… Pity...

Entries are repeated each RDS Info change

This is an issue where for some reason the broadcaster is re-transmitting duplicate metadata during a song instead of transmitting a single occurrence of the metadata corresponding to the song.

[JST1963]

@swizzle its a bug in the 'next' event handler. Already fixed :-)

OK, does this mean I can stop nagging about it?

[JST1963]

Playback History is cool when you want to see what played in the near past.
What I don't like however are the entries of the radiostations. Each time a station changes the RDS info, an entry is written in the playback history. That implies several lines are identical… Pity...

Entries are repeated each RDS Info change

This is an issue where for some reason the broadcaster is re-transmitting duplicate metadata during a song instead of transmitting a single occurrence of the metadata corresponding to the song.

Also understandable, that's why I said "Pity…", meaning you probably can't do much about it

[Tim Curtis]

Saving the MPD settings also changes the ALSA volume settings back to 100%

This can be very painful for my ears

I think that, whatever you put in the ALSA volume, should stay there, no matter what, until you manually change it...

ALSA Volume setting will go back to 100% after saving MPD settings

BTW: restarting MPD service does not change this setting.

When MPD volume is set to "Disabled" i.e., 0dB and the device has a hardware volume controller then ALSA volume is set to 100% to ensure that the overall volume output (MPD + ALSA) is 0dB. This also happens when resuming MPD playback after the renderers.

This is not a new behavior. It's been this way for years.

I understand, but isn't there a possibility that this parameter does not change after saving MDP, or any other renderer setting?
I set it at 80% and if all of a sudden it goes back to 100% it could not only harm my HP, but more importantly my precious ears.
It should be possible to force it always back to the value that was entered in this field, no?

Johan

Of course the code can be modified to behave differently but I'm not seeing the use case for < 0dB output from the player when a downstream volume control is being used.