#602887 alsa-utils: only stores levels for current system instead of supporting booting on multiple systems

Package:
alsa-utils
Source:
alsa-utils
Description:
Utilities for configuring and using ALSA
Submitter:
Paul Wise
Date:
2021-09-22 04:41:18 UTC
Severity:
wishlist
#602887#5
Date:
2010-11-09 06:44:41 UTC
From:
To:
One of my Debian installs is booted on different machines, I frequently
move the disk between my laptop and desktop. One of the issues I
encountered is that the audio levels are reset when I move between
machines. Specifically the Master Front level is set to zero. I also get
warnings about cards about being present during bootup.

The ideal situation would be:

Store the mixer settings in a per-system or per-audio-device file.

Have a cron job delete mixer settings for cards that haven't been used
in 6 months or so.

This would help roaming folks who boot Debian from a USB key on various
machines, including Internet cafes.

Ideally pulseaudio would take over this job (since it is per-user) but
alsa-utils needs to also do it for those who don't use pulseaudio.

#602887#10
Date:
2010-11-09 18:15:24 UTC
From:
To:
Hello Paul or should I say Paps?

first: your gpg key has been expired ;-)

* Paul Wise [101109 14:44 +0800]:

Well, just an idea:

I am using netenv in such cases. You can define a per hostname
dependend /var/lib/alsa. This is the place where the soundcontrols
are stored. As well you can define a asoundrc (etc or $home) per
hostname for the diffrent sound devices and you're done.

Isn't that to complicated?

Nice idea, but you know unixes are providing many solutions and are
always a challenge. If one uses a stick or hd for more than one
machine we can expect that user can handle those comfortable ideas
with provided tools by himself, isn't it?

Elimar

#602887#15
Date:
2010-11-10 01:35:57 UTC
From:
To:
Per-hostname is insufficient since it is the same Debian install on one
hard drive, but I am booting it on different hardware.

It would meet my needs and the needs of other roaming Debian users. I
think it would be exactly enough flexibility to support all users.

It would be almost trivial to support this within alsa-utils and there
are zero to minimal downsides for non-roaming users so I don't see why
it couldn't be implemented within alsa-utils (apart from lack of time).

#602887#20
Date:
2021-09-22 04:23:55 UTC
From:
To:
Hello,

Good morning,

We have gone through your samples from a partner and Here is our  Order
List. Please do bear in mind that we are very much in  need of this
order, quote your competitive prices.

Kindly send the Order confirmation.

Your early reply will be much appreciated.

Best Regards,

Maryanah Erwin.

PT FINDORA INTERNUSA

Jln Pahlawan 66 Kec. Arjawinangun

45162 CIREBON West-Java INDONESIA

tel : +62 231 357334

fax: +62 231 357260

email: marketing@findora.com