Great, yet another feature that should be being implemented by the OS VENDOR, intead being implemented in a non-standardized manner by an APP DEVELOPER.
See kids, this is what happens when your OS vendors decide that its more important to add shiny to their products than it is to fix deep architectural problems. In this case, that problem is that the AUDIO API's do not already have a native way to add this indicator, anywhere in the OS ..
IF there were a real Digital Audio Mixer implemented in your average Consumer OS, then we'd have per-app audio controls natively being included in such a Mixer interface .. however, the OS vendors have decided its more fun to make shiny things than actually .. you know .. provide valuable OS services.
Color me grumpy. It sucks that the Google Chrome team are having to implement this..
Actually, Windows 7 audio DOES do this - I see separate volume controls for applications if I click on the volume control tray icon. Likely requires driver support for the feature.
Yeah so this is what I mean exactly: use the OS features instead of hacking the App up to do what, should be in my opinion, something just provided to the App by the OS..
Every audio stream in the OS should be backed up with an OS-based Mixer control, is my point. We had it in BeOS and now it seems .. its finally possible in Win7 .. but yeah .. these aren't the only OS's around to run Chrome on ..
So if you have 50 tabs open, the OS should expose 50 audio sliders somewhere??? How will you know which one is for which tab? Also, isn't it better to be able to CLOSE that tab rather than letting it continue play audio and just mute it?
If you have one channel in the system audio mixer for every channel that the system is playing then yes: you can just see what channel is active and mute it. Like on any old mixing desk.
See kids, this is what happens when your OS vendors decide that its more important to add shiny to their products than it is to fix deep architectural problems. In this case, that problem is that the AUDIO API's do not already have a native way to add this indicator, anywhere in the OS ..
IF there were a real Digital Audio Mixer implemented in your average Consumer OS, then we'd have per-app audio controls natively being included in such a Mixer interface .. however, the OS vendors have decided its more fun to make shiny things than actually .. you know .. provide valuable OS services.
Color me grumpy. It sucks that the Google Chrome team are having to implement this..