A few of my favorite Win7 Sound features – UI refinements

Well, we shipped Windows 7, and now I’d like to talk about a few of my favorite features that were added by the Sound team.  Most of them fit in the “make it just work the way it’s supposed to”, but a few are just cool.

I also want to call out some stuff that people probably are going to miss in the various Windows 7 reviews.

One of the areas I want to call out is the volume UI.  There’s actually been a ton of work done on the volume UI in Windows 7, although most of it exists under the covers.  For instance, the simple volume control (the one you get to with a single click from the volume notification area) uses what we call “flat buttons”.

Windows 7 Simple Volume UI:      

Windows Vista Simple Volume UI:

Win7 Simple Volume Vista Simple Volume

Both the mute control and the device button are “flat buttons” – when you mouse over the buttons, the button surfaces:

simple volume with "flat button" enabled

By using the “flat buttons”, the UI continues to have the old functionality, but it visually appears cleaner.  There have been a number of other changes to the simple volume UI.  First off, we will now show more than one slider if you have more than one audio solution on your machine and you’re using both of them at the same time.  This behavior is controlled by the new volume control options dialog:


As I mentioned above, the device icon is also a “flat button” – this enables one click access to the hardware properties for you audio solution.


The volume mixer has also changed slightly.  You’ll notice the flat buttons for the device and mute immediately.  We also added a flat button for the System Sounds which launches the system sounds applet.


Another subtle change to the volume mixer is that there are now meters for individual applications as well as for the master volume:


And finally, the volume mixer no longer flickers when resizing (yay!).  Fixing the flicker was a problem that took a ton of effort (and I needed to ask the User team for help figuring out the problem) – the solution turned out to be simple but it took some serious digging to figure it out.

Comments (64)
  1. Anonymous says:

    "Flat" buttons that show up when you mouse over them are like door handles that don’t appear until your hand is on them.  While it may look cool, it doesn’t exactly make the door any easier to open.

  2. Nathan – how do you discover toolbar buttons?  They behave exactly the same way.  Or the butons on the tiles in the mobility center?  Or all the controls in Windows Media Player?  There are a number of buttons that fade into the background in Windows for exactly the same reason – the button visuals clutter up the display when they’re present but inactive.

    You’re right that the flat buttons are missing the normal button affordances (raised 3d effect) but those affordances appear when you mouse over the control.

  3. Anonymous says:

    How did you guys manage to fix the volume mixer flickering during re-sizing? Would be glad to hear how that was fixed.

  4. Toukarin – it’s on my queue of Win7 posts.  

    Here’s a hint: Group boxes are buttons.

  5. Anonymous says:

    Love the new functionality, thanks for that! 🙂

    I do, however, prefer vista’s "real" button for the mute functionality (speaker icon) – i think that it’s now less intuitive to understand what’s an interactive element and what’s not.

    also, a feature that i really wanted is the ability to selectively switch audio output to a specific channel, e.g. (based on the images in the post) after the "Windows Media Player" channel has been established to output to the "Speakers" device, switch it to output to the "Headphones" device. i’ve seen in a channel 9 vid that this happens when a device becomes disabled, but can i do selectively without disabling any devices?

  6. Fernando, that’s a post for a couple of days from now – the answer is a qualified "yes" – you can do that by changing the default output device in the playback tab on mmsys.cpl (assuming that the app is rendering to the default output device).

  7. Anonymous says:

    I second (third?) what Nathan said — flat buttons aren’t particularly user-friendly.

    It’s not really a problem when toolbar buttons go "flat", because they’re arranged in a bar of similar command buttons, and they usually live just below the menu bar or caption, so they’re normally pretty obvious.

    When you start to have flat buttons on their own in the middle of the window, though, that’s getting very non-discoverable.  Not everybody mouses over every random icon just to see if it’s an interactive element in disguise.

    (It’s almost as annoying as websites that turn off the styling of hyperlinks, such that unless you mouse over them they’re indistinguishable from normal text.)

  8. Anonymous says:

    >"Nathan – how do you discover toolbar buttons?  They behave exactly the same way. "

    But toolbar buttons are in a place where I expect buttons to be.

    There is no indication that you can press the flat mute button what so ever. I would only discover it if I happened to move the mouse over it.

    It is clearly a step back with regard to user friendliness.

    What happens when you press the speaker?

  9. Anonymous says:

    I completely agree with Nathan that the flat buttons offer no visual cue that they’re clickable. Having to mouse over the button to find out that it’s a button makes its discoverabilty accidental. In a toolbar, a user knows to click the icons by virtue of the fact that *it’s a toolbar*! The context implies that the widgets are clickable. A flat button that’s islanded on a dialog offers no such context.

    As for toolbars, the first thing I do on any application that offers them is disable them. I guess that makes me too weird to offer UI advice.

  10. Anonymous says:

    Larry, you used flat toolbar buttons and Windows Media Player as if they were examples of good UI. An affordance that only appears when you mouse over is a second-rate affordance. I’m not buying the "clutter up the display" argument. A door handle does not clutter up the display of a door, it shows you how to open it.

  11. Anonymous says:

    Some new UI bugs also came to life during the rewrite/update.

    If you in the Volume Mixer press ALT key, you get a redundant line under Device GroupBox label.

    Also, in the same dialog, if you have multiple speaker endpoints to choose from, the fading effect on the "speaker" selection button is broken.

  12. Anonymous says:

    So Windows is slowly becoming a Lucas Arts adventure, you have to mouse over the whole picture to tell what’s clickable 😀

    Kidding aside, I’m really not sure if the cleaner look outweights the lack of affordances. I expect a lot of "Ah, I didn’t know you could to THAT" sentences in the future, as so often seen in the comments to some of Raymond Chen’s blog posts.

  13. Anonymous says:

    My problem with flat buttons is when they don’t make themselves apparent as a button.

    Case in point: I have been using Vista since Beta 1 and never once noticed the speaker icon was a button. The win 7 mute button is somewhat discoverable based on the fact it was a clear button in the past and it has the icon you would expect on a mute button (though I wouldn’t be suprised if I was asked by a non-techie what happened to the mute button)

    This is not to say flat buttons are bad, they just need to be used carefully and in a way that makes them self-evident as a button. The speaker icon in this example does not, in my opinion, because unless you mouse over it there is no indication it is not just a decoration that indicated the current output device.

  14. Anonymous says:

    My problem with flat buttons is when they don’t make themselves apparent as a button.

    Case in point: I have been using Vista since Beta 1 and never once noticed the speaker icon was a button. The win 7 mute button is somewhat discoverable based on the fact it was a clear button in the past and it has the icon you would expect on a mute button (though I wouldn’t be suprised if I was asked by a non-techie what happened to the mute button)

    This is not to say flat buttons are bad, they just need to be used carefully and in a way that makes them self-evident as a button. The speaker icon in this example does not, in my opinion, because unless you mouse over it there is no indication it is not just a decoration that indicated the current output device.

  15. Anonymous says:

    IMHO, the per app volume control sucks. Why is the per app volume slider "linked" to the master volume?

    Take http://blogs.msdn.com/blogfiles/larryosterman/WindowsLiveWriter/AfewofmyfavoriteWin7SoundfeaturesUIrefin_E2E9/image_thumb_1.png for example, there is very little room to "slide". It would be better if the per app volume starts @ 50% (middle of the slider, unrelated to where the master slider is)

    A somewhat related question: Is there a way to somehow change the sensitivity of the master volume? Meaning, I have a laptop (Vista) where for normal use, the master volume is at 12 (That’s what the tooltip says) This makes it very hard to make small adjustments to the volume (20+ is very loud, <5 is almost muted)

  16. Anonymous says:

    As far as the groupbox flicker goes, the taskmanager has been using a custom groupbox for years (the classname is DavesGroupbox or something like that)

  17. Anonymous says:

    Yes this is stuff people are probably going to miss in reviews, but that’s because it’s not obvious. If it’s clickable, it should look like it’s clickable. Imagine if those graphics were put into a web page, would you know they were clickable there?

    Flatness works for toolbars because the arrangement of icons in the toolbar suggests they are clickable. It works for Media Player because the icons are well-known action symbols (play, stop, pause). The graphics in those sound dialogs look like adornments, not functional additions.

    I’m glad you mentioned this in a blog though, now I can look wizardly by pointing out these hidden features to friends. 🙂

  18. asf: The per app slider is linked to the master volume slider because our usability tests showed that it helped to resolve the issues users had dealing with serial volumes.  

    Alexei: The alt g is because it’s there’s an accelerator that allows you to navigate to the device group – this is how all accelerators work.

  19. Anonymous says:

    Larry/Nathan: We’ve been conditioned since 1991 (or whenever Word 2 or WordPerfect 5.1 for Windows came out, choose word processor as appropriate) to look for toolbar icons, and the playback controls on WMP are also pretty obvious. In general, though, requiring a user to mouse over every picture on a window in the hope that the cursor or picture will suddenly change is pretty obnoxious. I’ve hated it since Office 97/IE 3, because there’s an ever-growing list of crap 3rd-party apps that decided that pixel-hunt adventure gaming circa 1990 was the perfect UI metaphor. I’d rather have a one- or two-pixel bevel on everything active than a spoiled graphic designer.

  20. Anonymous says:

    I’m going to join the flat-button bashing. I personally was bitten by the lack of affordances in them. Specifically, like it’s been said in previous comments, if the flat-button looks just like an adornment (i.e. device graphic – speakers) as opposed to a well-known action icon (i.e. mute), it is very hard (even for an advanced user like myself) to discover the fact that it’s a button, not just a graphic.

    I agree that the interface looks cleaner, simpler, but I don’t think that justifies the lack of usability and user-friendliness.

  21. Anonymous says:

    Nathan is absolutely right.  Flat buttons have no affordance.  There’s very little indication that it’s a useful, clickable gadget.

    I’m often finding controls in applications that I’ve used for long periods of time because it never occurred to me that what looked like a decoration or status indicator was actually a dynamic control.

    The mute control at the bottom of the new volume control is a perfect example.  It appears to be a visual indicator that sound is on.  I’d assume that to mute, I’d have to drag the slider all the way down, at which point I’d expect the radiating soundwaves in the icon to disappear.  I don’t think it would ever have occurred to me that it was a clickable thing.

    I really don’t think recognizable button borders add that much visual clutter.  What’s worse is that the dynamic affordances that flicker when I’m pushing the mouse out of the way are very, very distracting.

    It this fuzzy thinking that led to the annoyingly unpredictable disappearance of the underlined letters that indicate keyboard mnemonics.

    UI should be obvious and unassuming, not "discoverable".

  22. Anonymous says:

    Flat button suck.  I mean, they really suck.  

  23. Anonymous says:

    I agree with the common sentiment that flat buttons which aren’t in toolbars are bad UI.  I must be a curmudgeon – I don’t like how desktop apps are taking on the appearance of web 2.0 browser apps.  Usability takes a dive inside a browser – why emulate that on the desktop?

  24. Anonymous says:

    I’m going to have to join in on the flat button bashfest; you really should not have to move your mouse around the screen to find out what you can click on. I’ll add, though, that you don’t have to "clutter up" the design to make buttons apparent. A very subtle one-pixel shadow does as well as glass and beveling.

  25. Anonymous says:

    I bet Larry wishes the comment box wasn’t so discoverable…

  26. Anonymous says:

    I’m generally not against flat buttons, but I’d have never guessed that the speaker is a button – I always thought it was just a decoration. The mute button is somewhat discoverable, because you see it pop out when you move the mouse from the notification area icon to the slider, but I never moused over the speaker icon.

  27. Paul: Nah, I’ve got a thick skin. But the feedback has been "interesting".

    If you look throughout windows, you’ll find literally dozens of clickable entities whose affordances only show up when you mouse over them – the little chevrons in drop downs, the group arrows, the breadcrumb bar, tree control elements, etc.  I recognize the concerns about the "flat buttons" but we’ve not yet received feedback that customers in neutral environments have difficulty discovering them (this group unfortunately isn’t neutral because I pointed out he behavior – when testing discoverability of a feature, you need to present the feature in a context neutral environment (for instance, you show the user the volume control and ask them to perform a task: "Mute windows media player from the volume control")).

  28. Anonymous says:

    FWIW, I’ve got a Mac and I find it’s flat buttons terrible. I’ve been on it for about a year now. I still find myself mousing over random widgets to see if hovering turns on a tool-tip or if clicking means its active. I’ve since learned that yes, just about anything might be clickable but I get lost in apps like iMovie because the bits I really want are often hard to identify.

    You’d think I’d be an expert in it by now. I think I’m just an expert now in knowing that a) button hunting is important because buttons are camoflaged, b) not all buttons have tool-tips so hovering is a good first-effort search but not definitive, c) clicking on the thing to see if it clicks is the best strategy to discover buttons, d) some buttons are just inactive and won’t click anyway. Inactive buttons tend to look greyed out though so that’s a hint that it’s both a button and not available now.

    I never found a good strategy to find out /why/ a button was visible and unavailable.

  29. Anonymous says:

    I’ve been poking around in Win7 trying to discover more UI, and looking at other non-MS apps in the process. Apparently there are a lot of things that we users have been conditioned to click purely out of context. For example, toolbars weren’t always flat, but once we got used to clicking them then we knew what to do with them when the flatness craze started to take off.

    I’m also looking at the tab navigation chevrons in IE8. Just like flat buttons and flat toolbars, I think this is a bad idea, but it’s something that I intuitively know to click. In the case of chevrons, plus signs, minus signs, and arrows, however, there’s another level of contextual information besides just location that’s at work. I think users know that this class of symbols indicates action. Another example would be the now-ubiquitous symbols on CD players and tape decks (remember those)? We know what those symbols mean now, so almost nobody bothers to put "Play," "Rewind," and "Stop" text on media controls.

    The mute button and the device button, on the other hand, don’t say "Action" in the same way that the class of symbols I just described does. They’re just kind of sitting their waiting for me to accidentally hover the mouse over them. I suppose in a few years I might learn what those symbols mean, but I don’t think so right now.

    One more thing: flat UI widgets just feel like a solution in search of a problem. There wasn’t anything wrong with the obvious buttons in Vista, so why take away the obvious affordance? I think that’s what bugging most of us.


  30. > Why is the per app volume slider "linked" to the master volume?

    100% agree with asf here.  The per-app sliders are totally useless with the device volume turned down, the usability studies notwithstanding.  Maybe the usability studies were done on hardware that didn’t expose this problem?

    Suggested alternate design:


  31. Anonymous says:

    "you need to present the feature in a context neutral environment (for instance, you show the user the volume control and ask them to perform a task: "Mute windows media player from the volume control"))."

    That provides the context that muting the volume is possible from the volume control.  Even just asking for a list of tasks the volume control can perform invites an unusually thorough hunt. How many would miss mute?  How many would miss speaker configuration? How many would miss opening the mixer?  All of those are things that could easily be mistaken as simply adornments (like "Volume" in the XP volume control.)

    I can only answer this from my own experience: I did not know either speaker was clickable.  I thought the top was just identifying the device the slider controlled, and I glossed over the bottom one.  (I hadn’t gone looking for it yet, though, since I’ve been muting from the keyboard.)  The lack of discovery is compounded by the fade-in; you have to hover over the button to see the effect (unlike toolbars.)  Otherwise, I’m certain I would have found it as my mouse moved to the slider.

    Not to be all negative: I went from XP to Win 7, and I really like the audio changes.  Per-app sliders is pretty slick!  I’m interested to see what other feature’s you’ll call out 🙂

  32. Anonymous says:

    > If you look throughout windows, you’ll find literally dozens of clickable entities whose affordances only show up when you mouse over them

    It shouldn’t be a surprise to anybody that there is bad UI design in literally dozens of places in Windows.  Most of the problem areas you list were introduced in Vista, and sadly they seem to have been carried over to Win7.

    > when testing discoverability of a feature, you need to present the feature in a context neutral environment (for instance, you show the user the volume control and ask them to perform a task: "Mute windows media player from the volume control")

    This also is not a context neutral environment.  In this example, you’re telling the user that the volume control allows them to mute WMP.  The whole problem with flat buttons is you can’t discover that functionality is available in the first place, so telling the user that it exists is cheating.  To do it right, you’d have to put them at the desktop and tell them to mute WMP.

  33. Anonymous says:

    In the meantime I read all comments, so repeating it doesn’t really help anyone. However when I read the blog post I also immediately thought "What? You can click on the device icon?! Never bothered moving the mouse up that far."

    The per app volume slider being linked to the master volume doesn’t bother me much. There’s only one thing that I trap into every time I use it:

    1. Set all sliders to 50%.

    2. Move an application specific slider up.

    Expected behavior: Clearly the intention is to leave all apps at the same volume but have just one of them a bit louder.

    Actual behavior: All apps get louder. Notice though that the sliders of the other apps are not moving up and as soon as you just click one of them the corresponding volume returns to the correct loudness.

  34. Anonymous says:

    There is a good reason that this sort of thing is known as "mystery meat navigation" (http://en.wikipedia.org/wiki/Mystery_meat_navigation). Down with flat buttons!

  35. Anonymous says:

    > "mystery meat navigation"

    beautiful!  That’s exactly what I had in mind when I wrote my comment – now I don’t feel such a curmudgeon.  Thanks for the link.

  36. Anonymous says:

    I have to agree that you’re using the word "refinement" for what the rest of the world calls a "regression".

    The mute and mixer flat buttons — users will survive, because enough people will remember seeing a button in Vista and others will learn by watching them.  This isn’t to say that the flatness is good, it just isn’t extraordinarily bad.

    On the other hand, you wasted your time on the "System Sounds" as a shortcut bit, because no one who doesn’t read your blog will ever use it (and probably even most of us will forget by the end of the week).  Congratulations, you spent however many hours are needed for that feature (just a couple to implement, and many many more to test?) that will be used by a grand total of 5 users.

    Can there please be a setting in Windows Control Panel to disable button flatness globally?

    PS  You can’t use toolbars as justification — they’re well known to be inferior UI because MS wouldn’t have given us ribbons if toolbars were good, would you?

  37. Anonymous says:

    I’d seen those graphics in the W7 volume UI and had never clicked (pun intended) that they were buttons until I read your blog.

    Whoever is designing the Windows UI at Microsoft these days is making it beautiful, but underlying improvements are often undiscoverable. It’s a beautiful looking UI that I’d prefer not to use long term because it’s tiring on the eyes and things are no longer obvious.

  38. Anonymous says:


    Have you (MS in general) been able to beat IHVs into using a reasonable curve for volume setting? Linear characteristic which many are using is no good, you need something like quasi-logarithmic.

  39. Alexandre: Actually the hardware specification is that the volume curve is linear and we have WHQL tests that confirm that.

    The endpoint volume APIs have a volume taper that is applied to create a more natural volume curve.

  40. Anonymous says:

    I realize the horse is pretty well beat at this point, but I figured I’d throw out that I also didn’t have any idea that the speaker icon was a button.  Never had a reason to hover my mouse over it.  It _really_ makes me wonder just how many people would think the speaker is a button without outright asking them (and giving the answer away).

    I’m not sure why a raised border or simple 3D look is so frowned upon lately.  Flat might be "clean" but clean also means lacking detail and while I’m certainly no UI designer, small details were how I always thought you exposed UI functionality to the user (such as the underlined character for ALT shortcuts).

    In any case, I’m looking forward to the rest of your posts about Win7!

  41. Anonymous says:

    "The endpoint volume APIs have a volume taper"

    OK, but it would be great if earlier (XP) API and volume control had that volume taper. So far, on my laptop it seems completely linear.

  42. Alexandre: Windows XP is a 9 year old operating system and is in extended support.  That means that there aren’t going to be significant new features added to it.

    The support for the volume taper was added in Vista and continued in Win7 unchanged.  If you don’t like the volume taper in XP, upgrade.

  43. Anonymous says:

    Just one more point to throw into the mix here, as no-one else seems to have mentioned it – you talk about exposing the nature of these ‘buttons’ on mouse-over, but what about those of us who don’t have a mouse?

    One of the big marketing things for Win7 is touch input – with touch, there is often no hover-detection, so these ‘buttons’ are even less discoverable! Users with active digitisers have a slightly better chance, but still not great.

    (I’m a long-time reader of your blog, and really enjoy your posts – it is the UI guidelines and concept I disagree with here, which I know is out of your control, not your implementation of them).

  44. Anonymous says:

    @Chris Smith,

    The touch screens sense your finger in proximity to the glass, like my HP SmartTouch, and will follow the cursor after it. I don’t use the touch input, anyway, it’s too awkward to lift your hands all the time, when you can just move the mouse instead.

  45. Anonymous says:

    "If you look throughout windows, you’ll find literally dozens of clickable entities whose affordances only show up when you mouse over them – the little chevrons in drop downs, the group arrows, the breadcrumb bar, tree control elements, etc."

    Not the same thing.

    Once you discovered one of them, you discovered all of them.

    You figure out that a little chevron is a button, you know how to use all combo-boxes

    (not to mention that the chevron used to look like a button; the current behavior is worse than the old one).

    Overall, the Vista/Win7 UI goes one step forward and two backward (improves one area and damages two others)

    Don’t get me started on the Start "menu" 🙂

  46. Anonymous says:

    I’m sorry to see wise people like you thrilled by that "flat buttons" fashion. A flat "button" and even more – without a visible margin – makes hard for the user to guess if that region is a dumb picture or it is clickable. The user should go and check with the mouse if there is something there to be done. IMO one lamentable trends in dumbing UI.

  47. Anonymous says:

    Is it wrong to think there should be a checkbox with the word "Mute" next to it? I can’t imagine a more obvious and intuitive way to both mute the audio and see at a glance that the audio is muted.

  48. Anonymous says:


    Is it possible to configure windows to have an application (any app, eg. media player) play sound using multiple devices simultaneously. For example, I have a sound card built into my laptop, and I have a USB headset. I thought I would be able to watch a DVD using a regular set of headphones and the USB headset, but I could only do one or the other, not both at the same time.

    If this is a limitation of windows, why is it there?

    Thank you!


  49. Michael, you’ve described a feature we call "broadcast mode".  There are some serious technical challenges to implementing broadcast mode, not the least of which is that different audio solutions have different latencies – in the scenario you’re describing, you’d be quite upset if the sound in the headphones is out-of-sync from the sound coming from the speakers.

  50. > Is it wrong to think there should be a checkbox with the word "Mute" next to it?

    You have just described Windows XP’s UI.

  51. Anonymous says:

    Given XP is still the most popular version of Windows by a country mile (or even 7 miles) perhaps Microsoft should be heeding the lesson, rather than re-invent this particular wheel for no particularly good reason.

    It is well within Microsoft’s capabilities to afford us buttons with affordances in case like this one where it would make things appreciably more obvious from the get-go.  

  52. Alex: We had a GREAT deal of feedback on XP’s UI model, almost all of it negative.

    The UI design (which dates from Vista) was carefully usability tested to ensure that it was more discoverable and more intuitive than the XP design (there were staggering amounts of PSS calls resulting from the "wave" and "master volume" sliders for example).

  53. Anonymous says:


    Intuitive is good, but that doesn’t mean that just because part of your UI is not intuitive that you should change the whole thing.  Doesn’t it ever occur to you guys that only fixing the broken parts might be easier on users?

    I know it violates MS doctrine to leave well enough alone, but seriously, how can you possibly imagine that this new eye candy is more intuitive than a checkbox labelled "Mute"?

  54. I don’t see a problem with a button that changes state between a mute icon and an unmute icon – the visuals for mute and unmute are similar throughout windows and 3rd party applications.

    It turns out that there IS a minor accessibility issue in the Vista control panel, I’m actually planning on writing about that in the future (and more importantly how I solved the issue).

  55. Anonymous says:

    I have a few points to make here:

    1. Flat buttons are evil

    Rationale: They are not as easily discoverable, they suggest that click area is non-rectangular because they lack border, and that you have to aim and hit the part of an image to activate them thus putting an unneccessary strain on the user, and they don’t provide adequate feedback when clicked.

    2. Pictograms are evil

    Rationale: How a visually-impaired person or a color-blind person preceives those pictograms? I often find myself staring for several minutes at a button with an image of "something colorfull" trying to figure out what it is. Small size makes this daunting task even harder, and if there is no text or tooltip you can only click on it hoping that it will show you what it does without deleting some important files or electrocuting your dog.

    3. Ribbons are evil


    a) The only way to navigate a ribbon is using a mouse. Try doing it using only a keyboard then compare that "user experience" with the menu bar — standard menu bar was something millions of people have been accustomed to over the last ~40 years. Taking it away means tremendous loss of productivity for them (me included).

    b) Having so many rows and columns looks cramped — it takes too much vertical space especially considering 16:10 and 16:9 LCD monitors which are common nowadays, not to mention need for left-to-right, top-to-bottom scanning when you are looking for an option.

    c) Pictograms do not have universal meaning (for example, an open envelope can mean "Open the email to read it" or "You already opened this" or "Put something into this envelope to send it"?) depending on the context. Pictograms are always out of context in a ribbon (and even on a toolbar).

    d) Too much pictograms and colors make it hard for the visually impaired or color blind people, and I can’t even imagine using Narrator with those awkward ribbons — it is like Microsoft doesn’t follow their own rules on accessibility.

    I would really like to see flat interface and its elements dead and gone — it reminds me too much of poorly designed UI we see in the majority of linux applications.

  56. Igor, use a screen reader and see how the "flat buttons" appear :).  That’s how a visually impaired person sees the button.  And color blind people can see the fact that the shape of the glyphs changes dramatically between "Mute" and "Unmute".  You’re right that the 16×16 icon in the tray is a bit small, but the 28×28 icon in the flyout is quite reasonably sized.

    Yes, we thought about accessibility when we designed the feature – we actually went to a fair amount of effort to ensure that it was accessible.

    Having said that, the mute buttons in mmsys.cpl’s "Levels" page were NOT accessible in Vista, for Win7 I changed them to be accessible.

  57. Anonymous says:

    Speaking of "(there were staggering amounts of PSS calls resulting from the "wave" and "master volume" sliders for example)" is there any way to get this functionality back?

    I have a lot of inputs on my computer and I use them to pass several different devices through to my speakers (a TV, a 2nd computer, a synth, etc).  I like the option to control a "wave out" and a "master" separately so I can control the sounds being generated from THIS computer (using "wave out"), and my inputs (which will pass through to "master").  That way I can turn ALL of my software up and down and not effect the volume of my TV (for example).

    This is something that is VERY important to me, and I haven’t been able to figure out a work around.  If this could be done in some way (a registry key, command line, etc), I’d be a very happy person.

  58. John: The functionality never went away.  The sliders are now present on the "Levels" tab for each audio output.

    Each of the inputs should have their own volume control so you should be able to control the volume for each of the inputs independantly (but of course that depends on the driver implementation of your outputs)

  59. Anonymous says:

    Thanks for the response!

    I see and completely appreciate the control that it gives over the output of each piece of software.  It’s very nice.

    Also, the inputs are fine.  I’m cool there.  I can set them out exactly how I want them.

    What I want is the old "wave out" OUTPUT accessible again.  Essentially a "bus" of all software outputs on one slider, but SEPERATE from the global output slider.  The global output slider also controls the volume of my inputs, which I don’t want.  I want them to continue "passing through" and I’ll control those volumes on a per device basis on the devices themselves.

    Some way to regain that functionality would mean a lot to me.  Possibly the difference between upgrading to Win7 and not (if you can believe that).

    Again, I really appreciate you taking the time!

  60. The old "wave out" control was a side effect of the old sysaudio.sys audio architecture.   The only scenario where that would have value is on audio solutions that supported hardware loopback for audio inputs.  

    There are vanishingly few machines shipped today that have audio hardware which supports this functionality (largely because of cost).  Given that most (all?) audio hardware vendors aren’t supporting this in their current hardware, it’s unlikely that an analog of the old wave out control would be added back (since the only value of the old wave out control was to differentiate the volume of the Windows audio subsystem from that of hardware loopback functionality and most machines don’t provide support for hardware loopback).

  61. Anonymous says:

    Thanks again!

    I’m not explaining myself correctly it seems and I apologize for that.  I’ll try to explain this as succinctly as I can as to not waste any more of your time.

    In Windows XP when you opened up sndvol32 it showed you your volume levels for playback.  The left-most option was "Volume Control" which controlled ALL of your sound (as in, anything being generated by your computer as well as anything coming through any inputs).  If you had a TV plugged into your line-in (and the line-in unmuted and the volume set appropriately), moving this "Volume Control" slider would affect not only any software making sound on the computer (lets say an MP3 playing), but also the line-in.  It’s the master volume control of everything.

    In Windows 7 (in sndvol), the left most slider is called "Speakers" and performs the exact same function as what I outlined above in Windows XP.  It’s ALSO the master volume control of everything.

    Now, in Windows XP, the next volume slider to the right from "Volume Control" was "Wave".  Using the example above, if I moved this slider up and down, it’d change the volume of the MP3 but NOT the TV coming through the line-in.

    In Windows 7, this slider has been replaced by the per-application sliders.  If I am playing an MP3 in WMP and I move the WMP slider up and down, it changes the volume of the MP3 but NOT the TV coming through the line-in.

    The average person would simply set their volumes how they like them and most likely not touch them too often.  If they need to change volume, they’ll probably simply reach for the volume nob on their speakers.  Here is where the rub comes in for MY business.  I’m primarily an audio/video professional.  I have a few sets of speakers (some connected through an A/B switcher and some come off the line to go to a subwoofer and a seat transducer).  I don’t have the luxury of reaching for 1 single volume knob.  Everything is balanced around the idea that I can manipulate the volume in windows and keep all of my speakers in balance.

    If I am recording something, it comes in on an input.  Sometimes I’m running multiple pieces of software.  I *NEED* a single master slider that ONLY affects the volume of software and NOT any of my inputs.  Again, in Windows XP this was done using the "Wave" slider.  Because this was broken down into multiple applications instead of a single slider in Vista/7, I can’t do this.  This is a major work-flow issue for my business.  Is there any way to get a master slider for ONLY the software volume output and NOT *ALL* volume output in Windows 7.

    I have searched the internet high and low for the past 5 days looking for a solution.  This isn’t an easy topic to search for.  I always end up finding some site with people talking about the "wave out" recording feature.  

    In short (or long), I’m hoping this functionality is just hidden or accessible in some other way.  The only other option I can think of is writing a custom mixer application that allows me to shortcut-key the movement of ALL applications sliders relatively at the same time.  This just seems a little kloogy to me.

    Sorry for writing you a phone-book worth of stuff here.  Again, any help on this topic would be GREATLY appreciated as I’m at my wits end for how to deal with this.  I do understand that this isn’t how 99.999% of people would choose to control things, but this is what I have come to depend deeply upon and constantly opening up the mixer to adjust dozens of volumes up and down all day with the mouse is simply not an option.

    If you can think of anywhere else I can look or anyone else I can talk to for a solution, that would also be an immense help!  Thank you again!

  62. John, I fully understand what you’re talking about.  

    My point is that on current hardware (essentially anything made since 2006) the hardware loopback capability that enabled your TV to play through your speakers automatically was removed by the audio hardware vendors.  There are very few if any machines sold today that support this functionality – it was simply too expensive for PC manufacturers to continue supporting this feature.

    The only value of the Wave slider was to allow you to control the volume of the PC audio subsystem independantly of the hardware loopback controls.  But on modern PC audio subsystems there aren’t any hardware loopback controls.  So the wave slider doesn’t have any real effect.

    Because of this, we removed support for the wave slider.  The presence of the slider would only confuse customers since it had no practical effect (and we had a significant amount of feedback that it was a major pain point for customers (they’d accidentally turn down the Wave slider (or an app would turn it down for them) and then they wouldn’t be able to fix the problem).

    Having said all that, there is a new feature in Windows 7 called the "Capture Monitor" or "Listen To" that replaces the old hardware loopback functionality.  When the capture monitor is enabled, the volume for the capture monitor shows up in the volume mixer along with the volume of all the other applications.

  63. Anonymous says:

    Wow.  I was not aware that this was a "special" feature of the hardware.  I’ve always had it so I’ve taken it for granted.

    I’m going to try to code up a workaround that moves every application slider together.

    Thanks again for taking the time!

  64. Anonymous says:

    I’m a broadcast pro who uses the audio functions of windows constantly. If you ask me, the new UI in 7 isn’t a refinement, it’s a reduction in functionality to accommodate incompetents. The more you guys try to make computers easy for people who are too <expletive deleted> lazy to learn how to use them, the more difficult you make it for people aren’t. Where I used to be able to have a persistent mixer in the tray that had every control, both record & play available to me one-click away, I now have to click 1, 2, 3, scroll to get to a control. Not only that but the fact that popup you guys call a mixer won’t even remember where you left it on the screen.

    I understand that you have make things easy enough for a monkey to use it to sell a product. On the other hand, there actually are people out there who know what they’re doing and don’t feel like wading through 8 idiot dialogs to get to what they want to do. You need a dialog with a checkbox that asks two questions:

    1) My computing experience consists of Outlook Express and Internet Explorer, and 2) I know what I’m doing

    Then provide an advanced interface with instant access to whatever controls are available. Right now, I would stick to xp for my audio boxes on this basis alone if I can’t find a 3rd party mixer app that isn’t written for morons.

Comments are closed.

Skip to main content