On Thu, Apr 08, 2010 at 09:29:55PM +0000, Jacob Meuser wrote: > On Thu, Apr 08, 2010 at 02:14:40PM +0200, Alexandre Ratchov wrote: > > > It's a aucat "feature" (limitation), trivial to change though. > > Should we allow the volume of not-yet-created streams to be > > changed? > > > > I see no drawback of doing so > > hmm. maybe I'm misunderstanding something. the description of > the '-v' option in aucat(1) says "In server mode, clients inherit > this paramter." so, if I start aucat with 'aucat -l -v 90', then > each client's initial volume will be 90, but it can still be set > to 127, and it would be the same overall volume as if I had started > aucat with 'aucat -l' and then set a client's volume to 127?
There are two volume settings: - the ``weight'' which is recalculated when streams are created and destroyed (to share the dynamic range). - the MIDI knob which is to adjust the volume within the allocated dynamic range (the weight), once the stream is attached. -v defines the maximum weight a stream can get, which is roughly the volume when the MIDI knob is set to 127. Both are necessary. The -v option is mainly to avoid the ``volume jumps when new streams are created'' problem. > in other words, this patch lets you set the initial volume of > each client separately, as opposed to, or actually, in addition > to, setting the initial volume of all clients at server startup, > correct? the diff is to allow to start with a initial volume knob other than 127. > I could definitely see uses for this. > ok I put it in. -- Alexandre
