[PATCH] Re: KMix

[Frans Englich]

On Saturday 13 December 2003 10:29, Andras Mantia wrote:
> On Saturday 13 December 2003 11:09, Aaron J. Seigo wrote:
> > On Saturday 13 December 2003 01:50, Christian Esken wrote:
> > > Saving volumes automatically is out-of-question because any application
> > > can change the volumes - for example video players often manipulate the
> > > volumes. If by accident any MM application sets high volume on exit,
> > > KMix would auto-save those volumes: On the next boot KMix will help
> > > blasting your ears or speakers. This is a NO NO.
> >
> > in this case, wouldn't the volume already be blasting in their ears, even
> > before a reboot? and how often/likely is such a scenario?
>
> Imagine a movie/music file which was not normalized so you have to turn the

Yes, very annoying. Especially when someone sleeps in the room.

> volume up. On restart the KDE welcome sound will blast your ears...

But. My patch increases the likelyness for getting blasted by so little it 
actually is ignorable. If you have a miss-behaving app, a non-normalized 
sound file or whatever the reason to increase the volume to a abnormal level 
AND then *immediately* exits your KDE session _with_ logout sound disabled 
you will get blasted. Does it sound likely? No, because it is *not* likely - 
one out of all the total nnumber of times you play a sound. Considering how 
often it anyway will happen(with or without new behavior) the user is and 
must be hardened so who cares? ;-)
In other words, if you lever the sound to the level you can feel the 50Hz 
vibrating in your chest you will get fried when you start KMail, a popup or 
whatever - *If* you don't remember to lower the volume. In either case it is 
up to the user to protect his/hers ears. And the case when the user is ready 
to be blown away and immediately exits is _so_ unlikely that it is not worth 
implementing Christian's 'make save-on-quit configurable' proposal. 

And if you argue with me I will just turn up the volume and save it with my 
excellent save-on-quit behavior! Thank you very much!

>
> > and am i correct in understanding that the alternative is: the user has
> > to reset the volumes after every boot if they aren't saved? if so, that
> > would imply readjusting the settings all the time, versus just once in
> > the (how likely?) case of an application somewhere misbehaving, correct?
> >
> > (questions, questions =)
>
> I think the ideal way is that you configure some acceptable values, save it
> and they are always restored. 

In my opinion, we agree(referring to my save-on-quit suggestion). It has its 
roots in the observation that the user fails to save its changes by believing 
they're already saved. And the new behavior makes the GUI behave as the user 
expects.

			Frans