[nas] [PATCH] changed method of setting the input gain
Paul Fox
pgf at foxharp.boston.ma.us
Mon Jul 24 21:12:18 MDT 2006
jon wrote:
>
> Assuming I were to make MixerInit handle an integers well as
> a bool:
>
> 0 = do not modify mixer characteristics at startup at all.
> Use whatever is there.
in this mode, what happens on re-opens?
>
> 1 = setup all default gains/recording options the
> first time NAS is started, and never again thereafter.
would nas mixers track changes made by non-nas mixers?
>
> 2 = setup all default gains/recording options everytime the
> device is opened (actually, every server 'generation' so
> it would work even if releasedevice == no). This would of
> course ignore any of the last* settings.
just like i believe erik, i guess i'll have to believe you. :-)
i myself don't think i'd want this. but maybe i'd find a use!
so, here's the mode that i think i want:
- i don't particularly care whether nas sets defaults on startup
or not. that's a one-time initialization, and i could do it
in the script that starts nas just as well.
- i want nas to always use *and report* the current mixer settings.
if another app uses and adjusts the mixer, i want nas to notice
that, so that clients can see that it's happened.
it's entirely possible that what you've expressed as a list should
really be a combination of separate booleans:
a) init to default values at startup, or not.
b) reset to default NAS settings on every open, or not.
c) reset to last NAS settings on every open, or not.
d) track other app's changes to the mixer, or not.
i'd just turn on 'd'. i think jon would turn on 'a' and 'b', and
i think erik would turn on 'a' and 'c'. but perhaps this misses
something that you two have been mentioning that i didn't
understand.
paul
=---------------------
paul fox, pgf at foxharp.boston.ma.us (arlington, ma, where it's 66.4 degrees)
More information about the Nas
mailing list