[nas] [PATCH] changed method of setting the input gain

[Jon Trulson]

On Tue, 25 Jul 2006, Erik Auerswald wrote:

> Hi,
>
> On Mon, Jul 24, 2006 at 07:16:18PM -0600, Jon Trulson wrote:
>> On Tue, 25 Jul 2006, Erik Auerswald wrote:
>>> On Mon, Jul 24, 2006 at 02:59:06PM -0400, Paul Fox wrote:
>>>> i wrote:
>>>>> erik wrote:
>>>>>> On Sun, Jul 23, 2006 at 10:29:07PM -0600, Jon Trulson wrote:
[...]

>>> settings and never change them.
>>>
>>
>>         So NAS clients would not be able to alter their gains for
>>         instance?
>
> That's the idea. NAS would not use the mixer at all as if there was no
> mixer.
>

         Hmm.. I can see the bug reports now :) I'm not sure that's
         wise.  I can understand not touching them unless specifically
         asked to by a client, but ignoring a client's legitimate
         request seems unwise.

>>> My "consistent gain setting" patches had the reason that I wanted to be
>>> able to control the NAS settings even if the device is currently
>>> released. This is very useful if the last NAS user left the gain at 100
>>> from watching a DVD and my music should be played with gain 30. If the
>>> NAS server did not change the settings of a reopened device I would have
>>> to endure some much too loud music for the time I need to react to the
>>> starting playback.
>>
>>   You mean non-nas application setting the gain at 100, right?
>
> I mean a NAS application setting the gain to 100. I wanted to be able to
> change this setting without first starting the way too loud playback.
>

         Ahh...

[...]

>>   across the living room, after I've used NAS xmms at too loud a
>>   volume :)
>
> The RestoreMixer option could indeed help here. ;-)
>

         Might be preferable for some... But can be handled
         independantly of any mixer init changes.

[...]

>>>> reading the device.
>>>
>>> As stated above I would not like this.
>>
>>   Yeah, lets discuss the mixer init stuff and find something we can
>>   all be happy with :)
>
> I've attached a patch that does what I think "mixerinit = no" should do
> (and keeps the current behaviour for "mixerinit = yes").
>

         I've applied this.. it seems to make sense.

> At startup the mixer settings are queried and the server values set to
> them if "mixerinit" is set to "no". Any NAS client can change the mixer
> settings later.
>

         Good :)


-- 
Jon Trulson
mailto:jon at radscan.com http://radscan.com/~jon
#include <std/disclaimer.h>
"No Kill I" -Horta