2010/5/3 Martín Soto
<donsoto@xxxxxxxxx>
What I conclude from this is that putting a mixer-style interface in the sound menu, as proposed originally is not a good idea, even for more or less advanced use cases like this. What would be interesting is a mechanism for pausing playback automatically when more urgent sources need to take over.
so before i go back into making useless audio indicator mockups, i'll ask a few questions about the ideas presented here..
a) how about listing mute toggle and play/pause for relevant apps?
a buttoned interface with columns or rows for the respective apps..with little 3 Bit digital volume meters (2 for stereo/surround, 1 for mono) attached to each app icon
b) do we really need "main volume"?
IMO, main volume will never require changing.
In a digital audio system 0dB is the overall total maximum of possible amplitude.
everything else will never exceed this fixed value.
either remove the fader, or call it "all" and use it to toggle all single application volumes, is my opinion.
c) do we need a global mute button?
personally, i think so, yes.
would that be the default action on audio indicator middle click?
d) are indicators going to be obviously clickable buttons in the end?
so far, indicators are dynamic informative icons, informing with the option of interaction onClick. onRelease is only losely defined, onDrag not at all as far as implementation is concerned. i would enjoy an audio indicator button/applet icon capable of muting all volumes or regulating them on basis of a pointer dragging gesture
this would be especially helpful with touchscreen enabled devices