Linked by Thom Holwerda on Mon 27th Aug 2007 22:21 UTC
Windows A curious network performance reduction noticed by many Windows Vista users of the 2CPU forum that became the talk of Slashdot last week has been identified as having been caused not by DRM, as Slashdot users expected, but by a curious prioritization 'feature' of Vista that's intentionally biased toward Media Player at the expense of network and system resources.
Thread beginning with comment 266206
To read all comments associated with this story, please click here.
Good and Bad
by Obscurus on Tue 28th Aug 2007 03:07 UTC
Member since:

As a computer musician, the high thread priority given to audio streams is great - it means that I will be able to get much better latency in my sequencer and run more tracks and plugins. However, it is pretty piss poor that they didn't consider gigabit networks and that network performance suffers so badly - if I am using a gigabit networked drive with my audio apps, this could be a problem. Interested to see what sort of fix is made.

Reply Score: 2

RE: Good and Bad
by google_ninja on Tue 28th Aug 2007 03:31 in reply to "Good and Bad"
google_ninja Member since:

The big thing for audio guys on vista is WaveRT, which is a different way of doing sound. Unfortunately, it requires hardware support, so we aren't seeing much of it yet (I'm stuck using the ASIO4All shim driver for my stupid embedded sound card on my laptop). But once the cards start coming out, Vista will be giving OSX with coreaudio a run for its money.

Reply Parent Score: 4

RE[2]: Good and Bad
by Kroc on Tue 28th Aug 2007 10:34 in reply to "RE: Good and Bad"
Kroc Member since:

Yes, but CoreAudio works here, now, on just about any Mac, since 10.2

It's quaint that Vista could give CoreAudio a run for it's money, but that money has long been earnt / spent in audio production based on Macs for years now.

All Vista's new audio stack is going to do for end users is maybe prevent the startup sound from stuttering.

Reply Parent Score: 2