WTH, MS? That's just not nice | The Coffeehouse

LeoDavidson

I think you're right.

I remembered a viewer I've written which hosts Flash out-of-process (for crash isolation and so Flash works even though the main process is 64-bit and Adobe are useless, ahem). When playing a Flash video via that, the mixer shows the icon + description of the out-of-process host exe (description from the exe's resources), rather than the icon/title of the top-level window.

If I switch to another viewer that's in-process and plays sounds, the mixer attributes it to the main top-level window.

All makes sense!

Also makes me realise I should give my out-of-process exe a nice icon. I didn't think it would be shown to the user anywhere until now. Smiley

fknight

It's obviously Photoshopped because the picture of this volume mixer window doesn't have random application volume sliders covered with black pixels and an inaccessible slider or sliders sitting on top of each other.

Bass
Channel 9, best used in moderation

I can tell by the pixels.

Larry Osterman

In reply to Ion Todirel

#Nov 3rd @ 11:14 AM

Ion's basically right. If the application hasn't explicitly set the title for a session, the volume mixer attempts to deduce the title from the evidence it has. In this case it knows the PID of the process, if it can find a top level window associated with that process, it'll use that window, otherwise it will use the resources embedded in the binaries executable to find the session title.