> Making the global volume a scaling factor for each output sounds like
> a good approach to that.
This has the downside that there are now several different equivalent
settings (e.g. global=50%, output1=50, output2=100 vs global=100%,
output1=25, output2=50). Also you get into these situations such as
when you have global=50% and output1=100, but you want output1 to be
even louder, so you have to increase the global volume and decrease
correspondingly all the other outputs, which sucks.
The "global is the output's average" approach is simpler for the user,
so I think this should be the exposed semantics. But internally it
should use a different representation (e.g. each output's volume is
stored as a floating-point scaling factor and computed by multiplying
the global volume by this factor and then clipping the result to
0..100).
Stefan
_______________________________________________
mpd-devel mailing list
[email protected]
http://mailman.blarg.de/listinfo/mpd-devel
