Hi guys J.river 13 comes with the WASAPI plug in New Features in MC13 . Semi J.River is feature packed..it will play all formats. It gives you so many more options than Itunes without the restrictions or needs for added plugins. Once you try it I doubt you'd ever seriously consider Itunes again.
Using WASAPI by way Vista or Windows 7 in exclusive mode gives you bit perfect output up to 24 bit/ 192Khz.
Foobar also has a WASAPI plugin..it works well without a hitch!
Here's a quote from a web page on WASAPI
Why Yet Another Audio API?
So why has Microsoft added WASAPI to the list?
* 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. The reasons for the new audio engine are:
o A move to 32 bit floating point rather than 16 bit, which greatly improves audio quality when dealing with multiple audio streams or effects.
o A move from kernel mode into user mode in a bid to increase system stability (bad drivers can't take the system down).
o The concept of endpoints rather than audio devices - making it easier for Windows users to send sounds to "headphones" or record sound from "microphone" rather than requiring them to know technical details about the soundcards installed on their system
o Grouping audio streams. In Vista, you can group together all audio streams out of a single application and control their volume separately. In other words, a per-application volume control. This is a bit more involved than might be at first thought, because some applications such as IE host all kinds of processes and plugins that all play sound in their own way.
* Second, the intention was to support pro audio applications which needed to be as close to the metal as possible, and keep latency to a bare minimum. (see Larry Osterman's Where does WASAPI fit in the big multimedia API picture?)"
Using WASAPI by way Vista or Windows 7 in exclusive mode gives you bit perfect output up to 24 bit/ 192Khz.
Foobar also has a WASAPI plugin..it works well without a hitch!
Here's a quote from a web page on WASAPI
Why Yet Another Audio API?
So why has Microsoft added WASAPI to the list?
* 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. The reasons for the new audio engine are:
o A move to 32 bit floating point rather than 16 bit, which greatly improves audio quality when dealing with multiple audio streams or effects.
o A move from kernel mode into user mode in a bid to increase system stability (bad drivers can't take the system down).
o The concept of endpoints rather than audio devices - making it easier for Windows users to send sounds to "headphones" or record sound from "microphone" rather than requiring them to know technical details about the soundcards installed on their system
o Grouping audio streams. In Vista, you can group together all audio streams out of a single application and control their volume separately. In other words, a per-application volume control. This is a bit more involved than might be at first thought, because some applications such as IE host all kinds of processes and plugins that all play sound in their own way.
* Second, the intention was to support pro audio applications which needed to be as close to the metal as possible, and keep latency to a bare minimum. (see Larry Osterman's Where does WASAPI fit in the big multimedia API picture?)"