Hi, Most concerns are 'library' issues, where you don't want to make noise, whatever the source. That does call for master volume controlled by the 'oh shit i'm way too loud' hardware buttons. Audio apps can choose as output either one (or multiple) of output types music, alarms&ringtones, notification, game, which can be controlled from indicator menu. (also quickly accessible if you press the hardware master buttons?) That means that in-game you can, at most, control that game's volume from the game menu, all games' volume from the notifications, and master volume by hardware buttons (or notification). The type of volume adjusted should of course be shown in the volume indicator bar.
Some concerns with a master volume: If you do this while listening to music with earplugs, and max the volume, does that mean that when you get home and unplug the phone, the ring/callvolume should stay maximum? Maybe if earphones or bluetooth audio are connected that device is a different device not controlled by master? (so you can drop the mastervolume in the library while listening to loud music on earplugs) But maybe it's fine under master control. I'm not sure how to handle low volume music listening in bed with loud wakeup alarms. Maybe alarms should be excepted from the master. Or there's one clock alarm that has an exception, otherwise your 'flip the page' alarm in the library will be way too loud. It's a complex matter that asks for lots of exceptions... Cheers, Maarten On 2 October 2015 at 09:50, Alberto Mardegan <alberto.marde...@canonical.com > wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 01.10.2015 19:50, Matthew Paul Thomas wrote: > > It seems like a weird thing to allow, sure. But consider the > > consequence if we forced all app volume sliders to be > > app-specific. Instead of having two, or three, or four audio output > > roles, we would now have, effectively, at least one role for each > > app that outputs audio. You have ten apps installed that can output > > audio? You'd now have at least ten roles. > [...] > > I'd propose to take one step back and look at another approach: let > the hardware volume keys control the master volume only, and make all > apps' volume a fraction of the master volume (as it is in Ubuntu > desktop). That is, if the phone has been set to silent mode, no app > should ever be able to play a sound (OK, with one exception: clock > alarms). > > An app can have its own volume control, but with the understanding > that 100% only means "play at the system volume level", never louder > than that. > > This would have the consequence that apps might not even need to > implement their volume control (except for a "mute" button), and that > the hardware volume buttons would always do the right thing. > > Ciao, > Alberto > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iEYEARECAAYFAlYON08ACgkQVLQegMXeCFIZDACcCAvW+C5yZ2ZIjY+zGEK48N0k > 3DAAnA5cBFNu8jE0Dzn6x8n6MfZ2Iwcv > =5aWS > -----END PGP SIGNATURE----- > > -- > Mailing list: https://launchpad.net/~ubuntu-phone > Post to : ubuntu-phone@lists.launchpad.net > Unsubscribe : https://launchpad.net/~ubuntu-phone > More help : https://help.launchpad.net/ListHelp >
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
