Editing Bypassing Windows Mixer

Jump to: navigation, search

Warning: You are not logged in.

Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 18: Line 18:
 
* Forfeits advantages of modern Windows audio pipeline: audio stream formats that aren't natively supported by your audio hardware will fail to play. You're likely to get errors with:
 
* Forfeits advantages of modern Windows audio pipeline: audio stream formats that aren't natively supported by your audio hardware will fail to play. You're likely to get errors with:
 
** Mono streams.
 
** Mono streams.
** Multichannel (more than two channels) streams on a soundcard with stereo output only.
+
** Multichannel streams on a soundcard with stereo output only.
** Uncommon channel configurations.
+
** Less common multichannel configurations.
** Uncommon sample rates.
+
** Less common sample rates.
 
To workaround these issues, you'll have to use additional DSPs such as resampler or "convert mono to stereo" in foobar2000.
 
To workaround these issues, you'll have to use additional DSPs such as resampler or "convert mono to stereo" in foobar2000.
* Interacting with soundcard drivers directly rather than letting Windows Mixer do it will often expose soundcard driver bugs that can't be triggered otherwise and lead to system-wide instability. There have been countless documented cases of otherwise stable soundcard drivers causing BSODs when using KS, ASIO or WASAPI. This happens because:
+
* Interacting with soundcard drivers directly rather than letting Windows Mixer do it will often expose soundcard driver bugs that can't be triggered otherwise and lead to system-wide instability. There have been countless documented cases of stable otherwise soundcard drivers causing BSODs when using KS, ASIO or WASAPI. This happens because:
 
** KS and WASAPI: while these output methods rely on the same driver code as playing sounds through Windows Mixer, various quirks such as buffer sizes are different; drivers tend to make unsafe assumptions that whoever is invoking them behaves exactly as Windows Mixer does; these drivers would also stop working correctly after OS updates that change these behaviors.
 
** KS and WASAPI: while these output methods rely on the same driver code as playing sounds through Windows Mixer, various quirks such as buffer sizes are different; drivers tend to make unsafe assumptions that whoever is invoking them behaves exactly as Windows Mixer does; these drivers would also stop working correctly after OS updates that change these behaviors.
 
** ASIO: many major hardware vendors release massively buggy ASIO drivers and suspend any work on their drivers as soon as they get some subset of ASIO software working with their product without obvious problem symptoms.
 
** ASIO: many major hardware vendors release massively buggy ASIO drivers and suspend any work on their drivers as soon as they get some subset of ASIO software working with their product without obvious problem symptoms.

Please note that all contributions to Hydrogenaudio Knowledgebase are considered to be released under the GNU Free Documentation License 1.2 (see Hydrogenaudio Knowledgebase:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel | Editing help (opens in new window)