unity-design team mailing list archive

[Chris <cyber.druif@xxxxxxxxx>]

Alright, I've got another corner case: You've got some awesome music on
your touch device (smartphone or tablet) and you've got an always-on media
centre or server with speakers attached. I know that PulseAudio (or how our
audio stack it's called) is divided in a server and client software
configuration. It would be very dandy if those speakers would be
discoverable when you're on the network.

However that would make your situation sketch not true for touch devices,
they'd need to change their audio output to one of the server's.

Thoughts?

With metta, Chris
On Mar 21, 2012 4:17 PM, "Gustav Sony" <sony-qs@xxxxxxx> wrote:

>  (a&b) One or zero input sources
>      -> Hide if there are no or only one input devices. Grey out
> disconnected devices.
> (c) The previously selected output source is not available (eg. remove
> speakers)
>     -> Grey out! Use device which was used before plugged in.
> (d) Zero input or output devices - would it be shown at all
>     -> No ... if not needed ... don't show
> (e) Incompatible options (eg. a single jack either Mic OR Output)
>      -> Like Ubuntu does it now? ... don't have an computer to test.
>
> I think there is enough space ... "Input device" and "Output device" can
> link to input and output tab in audio configuration. Also you can indent
> the devices ...
>
> (1) direct touch (no hover)
>     -> Users of touch-screens do not often change there audio device! Do
> not show!
> (2) mouse (with hover)
>     -> Like every normal submenu ... I think it would not deflect using
> the volume slider!
> (3) keyboard (rightwards arrow key already used for volume)
>     -> With keyboard down arrow-key goes in ... and out.
>     -> Mute ▼ Volume ▼ Output devices ▼ Device1 ▼...▼ Input devices ▼...
> ▼Player▼Audio-configuration
>
> Am 21.03.2012 13:49, schrieb Paul Sladen:
>
> On Wed, 21 Mar 2012, Gustav Sony wrote:
>
>  Am 21.03.2012 11:46, schrieb Mark Shuttleworth:
>
>  please refine the proposal.
>
>  http://img51.imageshack.us/img51/5207/auswahlsoundindicatorde.png
>
>
> That is an intriguing proposal (to use the volume slider as a
> menu-parent for the input/output devices).
>
> How would be work for the following corner cases (they aren't shown by
> the mockup):
>
>   (a) Only one input source
>   (b) Zero input sources
>   (c) The previously selected output source is not available
>       (eg. remove speakers)
>   (d) Zero input or output devices - would it be shown at all
>   (e) Incompatible options (eg. a single jack either Mic OR Output)
>
> Can you think of ways to express "input" and "output" in any other
> ways (perhaps visually), that might be better than having two
> subheadings that might clutter the menu.
>
> Normally with a submenu a mouse click or using the keyboard rightwards
> arrow key activates the submenu.
>
> How would that work if the user was just trying to use the slider and
> wanting to increase the volume (by clicking or using the rightwards
> arrow) without actually opening the submenu aswell?
>
> How would be work with:
>
>   (1) direct touch (no hover)
>   (2) mouse (with hover)
>   (3) keyboard (rightwards arrow key already used for volume)
>
> Would you be able to investigate and expand the proposal to cover some
> of the points highlighted above?  (And any other pinchpoints that you
> can think of).
>
> Once again, thank you for working on it, it does look an interesting
> proposal but needs fleshing out into a more complete and defined
> concept.
>
> 	-Paul
>
>
>
>
> --
> Mailing list: https://launchpad.net/~unity-design
> Post to     : unity-design@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~unity-design
> More help   : https://help.launchpad.net/ListHelp
>
>