<p>I have a problem (and have been having it for some time now) -- the new sound mixer stack in Vista features new cool things, but also re-invents the wheel. Many applications that used to use Volume Mixer on a Windows system to mix different voiced outputs into one input (for example Wave-out + Line-in --> Stereo Mix) have since stopped working. The prime example of this behavior is the Shoutcast DSP plugin (could be useful for solution testing).</p>

<p>How Can I re-enable XP-mixer controls, or maybe emulate this behavior somehow, so that the program (SC DSP) can properly manage Microphone/Line-In playback volume along with Wave-out playback volume?</p>

<p>My thinking would be to emulate a program hooked-in into the Vista Mixer for Wave-Out and Line-out (or Mic speaker volume -- all playback, shown as separate adjustable "programs" so that the Vista Mixer could refer to it) and 'hook' it into the system under some emulation representing itself as the old volume mixer control interface for the program, but I frankly have no idea how to do that.</p>

<p>To clarify: this is not my PC (it is a HP Pavilion laptop). The problem seems to exist mostly due to the fact that Vista mixer controls separate programs, not separate inputs/outputs. The hardware is fully capable of doing what is needed when using Windows XP. I am well aware of the fact that this is a driver issue, but the driver is simply prepared for what Vista presents to the programmer through interfaces. The mixer device - as seen in the operating system, however it might look in software - is based on the mixer APIs for Windows Audio control.</p>

<p>Search using Google on Vista and line-in playback volume control for more info on the problem (and the sheer amount of users affected by it). Of course, a re-write of the Shoutcast Source DSP plug-in for WinAMP would do the trick, but that is not likely to happen...</p>

[{'answer_id': 71392, 'author': 'CL.', 'author_id': 11654, 'author_profile': 'https://Stackoverflow.com/users/11654', 'pm_score': 2, 'selected': False, 'text': "<p>The audio driver controls which mixer controls are available, and this will depend largely on the capabilities of the hardware.</p>\n\n<p>If the Vista driver doesn't have certain controls, then it's likely to be a shortcoming of that driver and not of Vista.</p>\n\n<p>(Please tell us which sound card/device you are using.)</p>\n\n<p>It would be possible to write a program to create your own mixer controls (this would be a software-only driver for a virtual sound card), but this program wouldn't be able to affect the audio routing inside the device if the actual driver doesn't have some mixer control for this.</p>\n"}, {'answer_id': 139736, 'author': 'Nick Haddad', 'author_id': 2813, 'author_profile': 'https://Stackoverflow.com/users/2813', 'pm_score': 3, 'selected': True, 'text': '<p>Controlling the volume levels of a soundcards indivudual input/output levels in Windows Vista mixer is possible using the audio <a href="http://msdn.microsoft.com/en-us/library/ms679162(VS.85).aspx" rel="nofollow noreferrer">EndPoint API</a></p>\n\n<p>This should allow you to adjust the main volume, and the volume of and <strong>connected</strong> audio inputs.  One wrinkle about this that when you enumerate the end points, if there isn\'t a microphone plugged into your soundcard, then nothing will be enumerated.  This means you\'ll need to change your application to respond to "microphone plugged in" events, and notify the user appropriately.  </p>\n\n<p>Another option is to dip below the Microsoft Core Audio and access the <a href="http://www.microsoft.com/whdc/device/audio/wavertport.mspx" rel="nofollow noreferrer">WaveRT</a> driver directly. This is a lot more work than using the WASAPI/Endpoint APIs, but will give you the most control over access to the inputs/outputs of the soundcard.    </p>\n'}, {'answer_id': 1185768, 'author': 'Larry Osterman', 'author_id': 761503, 'author_profile': 'https://Stackoverflow.com/users/761503', 'pm_score': 2, 'selected': False, 'text': '<p>If you mark your app as running in Windows XP compatibility, then all the old controls and behaviors will come back.</p>\n'}, {'answer_id': 1297432, 'author': 'Community', 'author_id': -1, 'author_profile': 'https://Stackoverflow.com/users/-1', 'pm_score': 1, 'selected': False, 'text': "<blockquote>\n  <p>If you mark your app as running in Windows XP compatibility, then all the old controls and behaviors will come back.</p>\n</blockquote>\n\n<p>This is true, but as of Vista SP1 patch KB957388, included in SP2, and with some soundcard drivers, the old mixer API (winmm.dll) functions can hang when the app is in XP compatibility mode.  In particular, mixerGetNumDevs and less often mixerOpen will not return on some computers.</p>\n\n<p>I've got reports from 5 Vista users out of around 200 Vista users in total where my app hangs when starting up, and I have tracked it down to these functions hanging.</p>\n\n<p>I would like to report this to Microsoft but cannot find anywhere to do so.</p>\n\n<p>All I can do now is release my software without compatibility mode enabled, but this loses functionality in my app, and the software cannot control the line-in or microphone mixers.</p>\n\n<p>I don't have time to work with low level API functions directly.  I rely on high level components, and I cannot find any for the new audio API's for my development system (Delphi).</p>\n\n<p>I would be interested in paying someone to write a DLL for me!!!\ne mail ross att stationplaylist dott com</p>\n"}]
['https://Stackoverflow.com/questions/71198', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/456146/']