Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HiFiBerryOS64 alpha7 Initial volumelevel not read after (re)start #543

Open
3Dirkie opened this issue May 7, 2024 · 1 comment
Open

Comments

@3Dirkie
Copy link

3Dirkie commented May 7, 2024

Describe the bug
After (re)start the volumelevel stored in alsactl.store is not read.

HiFiBerryOS version
System software 20240410

HiFiBerry sound card
Beocreate 2.4.5

To Reproduce

  • Check /etc/alsactl.store DSPVolume (see below)
  • run "amixer" to see volumelevels
  • see DSPVolume from amixer output not matching the level in alsactl.store:
# amixer
Simple mixer control 'DSPVolume',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 255
  Front Left: 252 [99%] [-2.00dB]
  Front Right: 252 [99%] [-2.00dB]
Simple mixer control 'Softvol',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 255
  Front Left: 255 [100%] [-0.95dB]
  Front Right: 255 [100%] [-0.95dB]

Expected behavior
In the previous version 20230404 the level in alsactl.store is used as the initial volumelevel. In the current version the level is 252, almost 100%. This is way too loud.

Additional context
/etc/alsactl.store:

state.sndrpihifiberry {
	control.1 {
		iface MIXER
		name Softvol
		value.0 123
		value.1 123
		comment {
			access 'read write user'
			type INTEGER
			count 2
			range '0 - 255'
			tlv '0000000100000008ffffdcc400000023'
			dbmin -9020
			dbmax -95
			dbvalue.0 -95
			dbvalue.1 -95
		}
	}
	control.2 {
		iface MIXER
		name DSPVolume
		value.0 254
		value.1 254
		comment {
			access 'read write user'
			type INTEGER
			count 2
			range '0 - 255'
			tlv '0000000100000008ffffdcc400000023'
			dbmin -9020
			dbmax -95
			dbvalue.0 -130
			dbvalue.1 -130
		}
	}
}
@hifiberry
Copy link
Owner

I can't reproduce this here. However, as every player can change the volume, it's possible that one of the players changed the volume after reboot. Try disabling all players and check if you still see this behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants