Posts: 48
Threads: 7
Joined: Jan 2021
Reputation:
0
(01-10-2023, 07:48 PM)Tim Curtis Wrote: I don't see anything suspicious in the startup log and a brief look through the code doesn't show anything that could directly cause the volume to be set to zero even though the knob slider and level are greater than zero.
If I get the chance I'll put some debug logging in a few spots in the code and if the issue occurs on my end I might be able to get some insight into what might be going on, otherwise maybe another dev that experiences the issue can poke around the code.
Thank you very much Tim.
Posts: 17
Threads: 2
Joined: Oct 2021
Reputation:
0
I also have a similar problem - either completely muting when increasing the volume, or muting one channel. another volume step restores both channels.
Posts: 13,426
Threads: 304
Joined: Mar 2018
Reputation:
545
What DAC?
Does the issue occur after refreshing the Browser?
Posts: 48
Threads: 7
Joined: Jan 2021
Reputation:
0
01-16-2023, 09:22 AM
(This post was last modified: 01-16-2023, 10:24 AM by dad33.)
(01-11-2023, 10:39 PM)Tim Curtis Wrote: What DAC?
Does the issue occur after refreshing the Browser?
Hello Tim,
i use the ALLOBOSS2. I have identical the same problem described by ARCZAR. Refreshing doens´t matter in this case.
Same problem using Firefox or Chrome browser on Android 12 or Safari on Apple IPad Air.
ARCZAR: Which DAC do you use?
Posts: 48
Threads: 7
Joined: Jan 2021
Reputation:
0
Hello Tim,
Volume works now fine with AlloBoss2 with the new 8.2.5 Version.
Thank you very much!!!
Posts: 48
Threads: 7
Joined: Jan 2021
Reputation:
0
(01-27-2023, 08:02 AM)dad33 Wrote: Hello Tim,
Volume works now fine with AlloBoss2 with the new 8.2.5 Version.
Thank you very much!!!
Hello Tim,
after a swapped to blutooth output connected to a speaker, the volume just is going to zero on change.
After switched back to AlloBoss2 Dac output still the problem exist, volume goes to zero on change.
The problem still exist.
Posts: 13,426
Threads: 304
Joined: Mar 2018
Reputation:
545
(01-31-2023, 04:07 PM)dad33 Wrote: (01-27-2023, 08:02 AM)dad33 Wrote: Hello Tim,
Volume works now fine with AlloBoss2 with the new 8.2.5 Version.
Thank you very much!!!
Hello Tim,
after a swapped to blutooth output connected to a speaker, the volume just is going to zero on change.
After switched back to AlloBoss2 Dac output still the problem exist, volume goes to zero on change.
The problem still exist.
Unfortunately I've not been able to repro this in testing but I recall seeing one or two occurrences a while back on one of my systems running an Audiophonics DAC. Its a very rare IME.
Basically someone is going to have to create a consistent repro in order to troubleshoot or alternatively be able to capture some debug info for example errors in the Browser Javascript console or some other key information.
Posts: 2
Threads: 0
Joined: Feb 2023
Reputation:
0
02-02-2023, 12:56 PM
Hi,
I have an ES9038Q2M based DAC, and the problem occur on my end as well.
I use a slightly custom driver; based on i-sabre-codec/i-sabre-q2m.
The interesting phenomenon on my config is:
- When I'm using either the vol.sh script or the 'mpc volume' command, or the GUI interface: I always have a problem with volume going to -127dB. (zero in this case). It's somehow random, which GUI setting is responsible for going to Zero, but if I click GUI volume up multiple times, sometimes the HW volume goes back to normal.
Stange thing: If I control the volume from the ALSA interface directly from console using 'amixer sset', then the hardware volume is always correct.
---
I tracked it down on the I2C bus using a logic analyzer, and found, that ALSA commands perform the following actions (as normal):
Vol1Reg : Read old value / Write new value
Vol2Reg : Read old value / Write new value
example logic analyzer log:
2023-01-23 15:02:36.416874+00:00: R, Volume 1 (0xf) DATA:0x20
2023-01-23 15:02:36.417320+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.417777+00:00: R, Volume 1 (0xf) DATA:0x20
2023-01-23 15:02:36.418205+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.418641+00:00: R, Volume 1 (0xf) DATA:0x20
2023-01-23 15:02:36.419069+00:00: W, Volume 1 (0xf) DATA:0x10
2023-01-23 15:02:36.419385+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.419837+00:00: R, Volume 1 (0xf) DATA:0x10
2023-01-23 15:02:36.420267+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.420707+00:00: R, Volume 1 (0xf) DATA:0x10
2023-01-23 15:02:36.421133+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.421578+00:00: R, Volume 1 (0xf) DATA:0x10
2023-01-23 15:02:36.422353+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.422788+00:00: W, Volume 2 (0x10) DATA:0x10
2023-01-23 15:02:36.423219+00:00: R, Volume 1 (0xf) DATA:0x10
2023-01-23 15:02:36.423655+00:00: R, Volume 2 (0x10) DATA:0x10
However, mpc console and GUI of moode sends the following actions on I2C:
Vol1Reg : Read old value / Write new value / Read new value / Write '0xff'
Vol2Reg: Read old value / Write new value / Read new value / Write '0xff'.
example logic analyzer log:
2023-02-02 08:13:19.268154+00:00: R, Volume 1 (0xf) DATA:0xff
2023-02-02 08:13:19.268590+00:00: R, Volume 2 (0x10) DATA:0xff
2023-02-02 08:13:19.269034+00:00: R, Volume 1 (0xf) DATA:0xff
2023-02-02 08:13:19.269464+00:00: W, Volume 1 (0xf) DATA:0x2
2023-02-02 08:13:19.269782+00:00: R, Volume 2 (0x10) DATA:0xff
2023-02-02 08:13:19.270235+00:00: R, Volume 1 (0xf) DATA:0x2
2023-02-02 08:13:19.270673+00:00: R, Volume 2 (0x10) DATA:0xff
2023-02-02 08:13:19.271191+00:00: R, Volume 1 (0xf) DATA:0x2
2023-02-02 08:13:19.271617+00:00: R, Volume 2 (0x10) DATA:0xff
2023-02-02 08:13:19.272066+00:00: R, Volume 1 (0xf) DATA:0x2
2023-02-02 08:13:19.272492+00:00: W, Volume 1 (0xf) DATA:0xff
2023-02-02 08:13:19.272809+00:00: R, Volume 2 (0x10) DATA:0xff
2023-02-02 08:13:19.273273+00:00: R, Volume 1 (0xf) DATA:0xff
2023-02-02 08:13:19.273720+00:00: R, Volume 2 (0x10) DATA:0xff
However, I was not successful tracking down the source of the problem. But I can reproduce it on moode 8.2.5.
My assumption : it's not based on ALSA driver level. Either some configuration is bad, or the MPD volume control has some strange setting, and this MPD volume control invalidates somehow immediately a newly written volume value in the HW register.
At my setup, the problem occurs ONLY with hardware volume control. (Software volume works perfectly).
I use ALSA in 'direct hw' output mode.
Posts: 13,426
Threads: 304
Joined: Mar 2018
Reputation:
545
(02-02-2023, 12:56 PM)meszarosa Wrote: Hi,
I have an ES9038Q2M based DAC, and the problem occur on my end as well.
I use a slightly custom driver; based on i-sabre-codec/i-sabre-q2m.
The interesting phenomenon on my config is:
- When I'm using either the vol.sh script or the 'mpc volume' command, or the GUI interface: I always have a problem with volume going to -127dB. (zero in this case). It's somehow random, which GUI setting is responsible for going to Zero, but if I click GUI volume up multiple times, sometimes the HW volume goes back to normal.
Stange thing: If I control the volume from the ALSA interface directly from console using 'amixer sset', then the hardware volume is always correct.
---
I tracked it down on the I2C bus using a logic analyzer, and found, that ALSA commands perform the following actions (as normal):
Vol1Reg : Read old value / Write new value
Vol2Reg : Read old value / Write new value
example logic analyzer log:
2023-01-23 15:02:36.416874+00:00: R, Volume 1 (0xf) DATA:0x20
2023-01-23 15:02:36.417320+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.417777+00:00: R, Volume 1 (0xf) DATA:0x20
2023-01-23 15:02:36.418205+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.418641+00:00: R, Volume 1 (0xf) DATA:0x20
2023-01-23 15:02:36.419069+00:00: W, Volume 1 (0xf) DATA:0x10
2023-01-23 15:02:36.419385+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.419837+00:00: R, Volume 1 (0xf) DATA:0x10
2023-01-23 15:02:36.420267+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.420707+00:00: R, Volume 1 (0xf) DATA:0x10
2023-01-23 15:02:36.421133+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.421578+00:00: R, Volume 1 (0xf) DATA:0x10
2023-01-23 15:02:36.422353+00:00: R, Volume 2 (0x10) DATA:0x20
2023-01-23 15:02:36.422788+00:00: W, Volume 2 (0x10) DATA:0x10
2023-01-23 15:02:36.423219+00:00: R, Volume 1 (0xf) DATA:0x10
2023-01-23 15:02:36.423655+00:00: R, Volume 2 (0x10) DATA:0x10
However, mpc console and GUI of moode sends the following actions on I2C:
Vol1Reg : Read old value / Write new value / Read new value / Write '0xff'
Vol2Reg: Read old value / Write new value / Read new value / Write '0xff'.
example logic analyzer log:
2023-02-02 08:13:19.268154+00:00: R, Volume 1 (0xf) DATA:0xff
2023-02-02 08:13:19.268590+00:00: R, Volume 2 (0x10) DATA:0xff
2023-02-02 08:13:19.269034+00:00: R, Volume 1 (0xf) DATA:0xff
2023-02-02 08:13:19.269464+00:00: W, Volume 1 (0xf) DATA:0x2
2023-02-02 08:13:19.269782+00:00: R, Volume 2 (0x10) DATA:0xff
2023-02-02 08:13:19.270235+00:00: R, Volume 1 (0xf) DATA:0x2
2023-02-02 08:13:19.270673+00:00: R, Volume 2 (0x10) DATA:0xff
2023-02-02 08:13:19.271191+00:00: R, Volume 1 (0xf) DATA:0x2
2023-02-02 08:13:19.271617+00:00: R, Volume 2 (0x10) DATA:0xff
2023-02-02 08:13:19.272066+00:00: R, Volume 1 (0xf) DATA:0x2
2023-02-02 08:13:19.272492+00:00: W, Volume 1 (0xf) DATA:0xff
2023-02-02 08:13:19.272809+00:00: R, Volume 2 (0x10) DATA:0xff
2023-02-02 08:13:19.273273+00:00: R, Volume 1 (0xf) DATA:0xff
2023-02-02 08:13:19.273720+00:00: R, Volume 2 (0x10) DATA:0xff
However, I was not successful tracking down the source of the problem. But I can reproduce it on moode 8.2.5.
My assumption : it's not based on ALSA driver level. Either some configuration is bad, or the MPD volume control has some strange setting, and this MPD volume control invalidates somehow immediately a newly written volume value in the HW register.
At my setup, the problem occurs ONLY with hardware volume control. (Software volume works perfectly).
I use ALSA in 'direct hw' output mode.
Nice debug :-)
The results suggest a bug in MPD itself but ideally we will need a generic repro using stock RaspiOS and MPD to confirm this theory.
Here is an issue describing essentially the same problem using a different DAC.
https://github.com/MusicPlayerDaemon/MPD/issues/1579
Btw I experienced the 0-volume issue a couple of times last night on Audiophionics ES9038 system.
-Tim
Posts: 48
Threads: 7
Joined: Jan 2021
Reputation:
0
02-04-2023, 04:32 PM
(This post was last modified: 02-04-2023, 04:36 PM by dad33.)
Hello,
the bug must be in the MPD or the bluetooth control.
Fresh 8.2.5. installation - works fine without bug as long as i switched to a bluetooth speaker in ´Audio Output´
After i connect to a bluetooth speaker - the bug exist, switching back to ˋlocal audio´ the bug still exist.
After that i made a fresh installation and the bug disappears as long as i swap the audio output to blutooth.
|
