loadingcoder.blogg.se - Windows audio session vs directsound

A move to 32 bit floating point rather than 16 bit, which greatly improves audio quality when dealing with multiple audio streams or effects.The reasons for the new audio engine are: First, Vista has a completely new audio mixing engine, so WASAPI gives you the chance to plug directly into it rather than going through a layer of abstraction.So why has Microsoft added WASAPI to the list? Its one weakness is that you can only use one ASIO driver at a time, which has potential to cause issues in the future as more and more studio equipment such as microphones, sound modules and monitors (that's what speakers are called in the world of pro audio) come with USB interfaces rather than the older model of plugging all your ins and outs into a single audio interface. Pro audio sound card manufacturers provide ASIO drivers. ASIO - This is a Steinberg audio interface model used by virtually all pro audio applications and is usually the best way to work at very low latencies.

Kernel Streaming - this is what most of the pro audio applications use to talk directly to the WDM driver with minimal latency.

DirectSound - has its uses, particularly for game development, but it appears Microsoft is phasing this out too.

Their main limitation is poor latency (its hard to go much below 50ms without dropouts).

WinMM - these are the APIs that have been around for ages (e.g.

And they are still available in Vista, so there is no need to move if you don't want to. Of course, there were always ways of dealing with audio in previous versions of Windows. This includes WASAPI (Windows Audio Session API), a brand new API for capturing and rendering audio. Windows Vista introduced a new series of APIs for audio, called CoreAudio.