Slackmaster2K
Gone
Well, some people have sort of hinted that they've seen the problem with other cards, but I haven't heard anything concrete yet. I also remember at least one person say that they couldn't repeat the problem with another card, but it's hard for people to understand this problem for some reason so who knows. All we'd need is concrete proof that at least one card does not exhibit this behavior and we'd know that either a) WDM is not flawed or b) WDM is flawed but it is possible to work around the problem in the drivers or software (hence other cards or combinations of cards and software might be fine).
I not sure that it will ever be fixed. It will probably be up to the soundcard manufacturers to fix it no matter where the blame lies. A few ms won't matter to microsoft
Actually, if it is WDM, then we very well might have to turn to the application developers to work around this, because the problem might not be solvable at the driver level.
Slackmaster 2000
I not sure that it will ever be fixed. It will probably be up to the soundcard manufacturers to fix it no matter where the blame lies. A few ms won't matter to microsoft
Actually, if it is WDM, then we very well might have to turn to the application developers to work around this, because the problem might not be solvable at the driver level.
Slackmaster 2000