Win XP Pro sound slow to respond

  • Thread starter Thread starter Bill
  • Start date Start date
B

Bill

I have three Win XP Pro machines and all three of them do
the following:

When I do something that prompts the system to throw a
messagebox on the screen, the accompanying sound "ding"
may take up to two/three seconds to happen. Is is as if
the sound driver has unloaded and needs to be reloaded
before giving me the "ding".

Any help?
 
Do you experience this behavior with the 'ding' sound only? If so, that
sound file may have gotten corrupted. Rename the ding.wav file (it's
typically found in c:\windows\media) and replace it with a fresh copy.

Tom Swift
 
NO. All sound files do this. For whatever reason the
system decides to play a sound - this occurs.
 
NO. All sound files do this. For whatever reason the
system decides to play a sound - this occurs.
Click to expand...
Which sound card chipset?

Try this experiment. Open a media file (something with audio)
in media player. Let it play for a few seconds and then pause it.
Minimise the media player.
See if you can create the problem with windows event sounds now.

Dave
 
That is interesting! I can't duplicate the problem on
any of my three computers using your experiment. One has
the Crystal Sound Fusion chipset and the other two have
simple Soundblaster. I wonder if all those updates
Microsoft has been putting out for the Media Player is
goofing up something in the system. It can't be good to
get one or two a day from them.
 
That is interesting! I can't duplicate the problem on
any of my three computers using your experiment. One has
the Crystal Sound Fusion chipset and the other two have
simple Soundblaster. I wonder if all those updates
Microsoft has been putting out for the Media Player is
goofing up something in the system. It can't be good to
get one or two a day from them.
Click to expand...
Bill, it's not actually the WMP's fault.
It has to do with the initialization of the direct sound buffer
and a corresponding, lag . When the WMP is paused there is
no lag, because a buffer is already avaliable.
I know this because, I researched it myself 18 months ago,
and found the very interesting google posts of a gentleman
named David Pochron.
If you do a search in google, using the advanced form
http://groups.google.com/advanced_group_search
you'll unravel the mystery. The posts of interest are dated
towards the end of 2001 and contain the guys name, the search phrases
C-MEDIA and MEDIA PLAYER.
Here is one:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&[email protected]

In my case, I had a c-media sound chipset, that's how I found this
stuff. The fix turned out to be an updated c-media driver...

Dave
 
Back
Top