Re: [Bug 623] New: Volume not remembered.

[Matthias Schniedermeyer <ms@citd.de>]

On Wed, Apr 23, 2003 at 10:26:38AM -0700, Martin J. Bligh wrote:
> >> I can only guess why. My buest guess is that not all
> >> sound-configurations are the same, on some systems the "defaults" could
> >> much to loud. (e.g. waking the neigbours when you restart you computer
> >> at night)
> > 
> > This is certainly the case. When I was packaging OSS for Xandros, our initial default was 50 percent. We eventualyl made it about 30, because even that was too loud on a laptop we were testing. There was little coherance between the various soundcards.
> > 
> > Waking the neighbors is the smallest problem. Blowing a speaker or makign the user deaf if quite another.
> > 
> > Yes, it's a distro problem. My Gentoo was build "-alsa" and so the alsa-sound init script does not 'go'. A simple rebuild will solve the problem.
> 
> I agree it's a disto problem to save and restore.
> 
> But I fail to understand how the distro can magically set a sensible 
> default, and yet we're unable to do so inside the kernel ? Setting it
> to something like 10 (or other very quiet setting) would seem reasonable.
> Then at least the poor user would have a clue what the problem was.
> 
> As to "There was little coherance between the various soundcards", yes
> this probably needs to be a per-soundcard setting for sensible defaults.
> I presume this is what the distros do?
> 
> Defaulting to silence seems user-malevolent ... 

The problem is (normaly) a "one time while installing"-problem. So don't
see the point. The "helper" that finds out the soundcard, should also do
a "find out the default volume to use"-round with the user.





Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.