Звук в Висте - что вы думаете об этом?
- Автор темы presly
- Дата начала
Ниасилил чётатам на ангийском, мне вот интересно будут ли дрова к моему вейвтерминалу и если да то когда.....
Драйвера на X-Fi под Висту уже вышли (про другие карты не знаю).
А вот, то что теперь музыку и софт будет сложней качать (сидящим на траффике)-в этой статье
http://community.livejournal.com/ru_pcnews...eply&style=mine
А вот, то что теперь музыку и софт будет сложней качать (сидящим на траффике)-в этой статье
http://community.livejournal.com/ru_pcnews...eply&style=mine
Вообще-то там написано "прощай KS/WDM модель дров, здраствуй чЕ-сам не знаю что". Вроде Сонаровцам, да и походу Штейням придется совершенно новые протоколы звука осваивать. Да и не только им... Может, конечно, я ни осилил все в деталях....
читать ниасилил, но по беглому просмотру видно, что флейм идет о компенсации кривостей акустики средствами операционки
- круто, конечно, но нам это ну никаким боком не нужно...
насчет штейней - то ASIO еще долго будет жить, даже если модель дров в самой винде изменится
- круто, конечно, но нам это ну никаким боком не нужно...
насчет штейней - то ASIO еще долго будет жить, даже если модель дров в самой винде изменится
Да-а-а, почитал я - оказывается - я был в танке 
Но вот это мне показалось довольно-таки интересным:
=================
Larry Osterman's WebLog
---snip---
Over the years, we've realized that there three major problem areas with the existing audio infrastructure:
1. The amount of code that runs in the kernel (coupled with buggy device drivers) causes the audio stack to be one of the leading causes of Windows reliability problems.
2. It's also become clear that while the audio quality in Windows is just fine for normal users, pro-audio enthusiasts are less than happy with the native audio infrastructure. We've made a bunch of changes to the infrastructure to support pro-audio apps, but those were mostly focused around providing mechanisms for those apps to bypass the audio infrastructure.
3. We've also come to realize that the tools for troubleshootingaudio problems aren't the greatest - it's just too hard to figure out what's going on, and the UI (much of which comes from Windows 3.1) is flat-out too old to be useful.
Back in 2002, we decided to make a big bet on Audio for Vista and we committed to fixing all three of the problems listed above.
The first (and biggest) change we made was to move the entire audio stack out of the kernel and into user mode. Pre-Vista, the audio stack lived in a bunch of different kernel mode device drivers, including sysaudio.sys, kmixer.sys, wdmaud.sys, redbook.sys, etc. In Vista and beyond, the only kernel mode drivers for audio are the actual audio drivers (and portcls.sys, the high level audio port driver).
The second major change we made was a totally revamped UI for audio. Sndvol32 and mmsys.cpl were completely rewritten (from scratch) to include new, higher quality visuals, and to focus on the common tasks that users actually need to do. All the old functionality is still there, but for the most part, it's been buried deep below the UI.
The infrastructure items I mentioned above are present in Vista Beta1, unfortunately the UI improvements won't be seen by non Microsoft people until Vista Beta2.
Но вот это мне показалось довольно-таки интересным:
=================
Larry Osterman's WebLog
---snip---
Over the years, we've realized that there three major problem areas with the existing audio infrastructure:
1. The amount of code that runs in the kernel (coupled with buggy device drivers) causes the audio stack to be one of the leading causes of Windows reliability problems.
2. It's also become clear that while the audio quality in Windows is just fine for normal users, pro-audio enthusiasts are less than happy with the native audio infrastructure. We've made a bunch of changes to the infrastructure to support pro-audio apps, but those were mostly focused around providing mechanisms for those apps to bypass the audio infrastructure.
3. We've also come to realize that the tools for troubleshootingaudio problems aren't the greatest - it's just too hard to figure out what's going on, and the UI (much of which comes from Windows 3.1) is flat-out too old to be useful.
Back in 2002, we decided to make a big bet on Audio for Vista and we committed to fixing all three of the problems listed above.
The first (and biggest) change we made was to move the entire audio stack out of the kernel and into user mode. Pre-Vista, the audio stack lived in a bunch of different kernel mode device drivers, including sysaudio.sys, kmixer.sys, wdmaud.sys, redbook.sys, etc. In Vista and beyond, the only kernel mode drivers for audio are the actual audio drivers (and portcls.sys, the high level audio port driver).
The second major change we made was a totally revamped UI for audio. Sndvol32 and mmsys.cpl were completely rewritten (from scratch) to include new, higher quality visuals, and to focus on the common tasks that users actually need to do. All the old functionality is still there, but for the most part, it's been buried deep below the UI.
The infrastructure items I mentioned above are present in Vista Beta1, unfortunately the UI improvements won't be seen by non Microsoft people until Vista Beta2.