Originally posted by: Sureshot324
Not that I'm opposed to it, but historically MS has always pushed their own propriety standards instead of using open standards. Apps written using open standards are easy to port to other operating systems, which is precisely what MS wants to avoid. There must be a business reason for this but I don't see it, unless they just didn't want to invest the money in developing Dsound anymore.
vista removed both graphics and audio from kernal level. this was done for 2 main reasons:
1) drm
2) stability/security (drivers can't bring down the whole system)
msft still cares about graphics so they took this as opportunity to do drastic changes to graphics model and set path for future (gpu task scheduler, virtual memory) and drop older legacy directx.
so for graphics, after old model was abandoned msft stepped in with new api.
but for audio msft abandoned old model and left audio community (hardware, games) to fend for themselves. it's not that msft is supporting or pushing for an open standard, it's that the community is moving towards it since msft stopped caring.
any changes msft did make for audio is geared towards drm, htpc, and hd-dvd/blu-ray
in a year or 2 everything will be like it is now with xp, direct sound, and eax. except on vista people will be using openal and eax 7,8,9 and still be stuck with creative as only choice for surround sound in gaming (because they'll sue any alternatives).
also, hardware acceleration isn't really needed anymore. computers just need a dac
1) optimistically it might provide 10% boost, but that mattered more in the quake2/3 days when 40-50fps was high.
2) dual cores are common now. it's perfectly reasonable to do sound in software. and with quad cores becoming more mainstream this year, any hit from software audio will matter even less or not matter at all