"windows was unable to play the test tone" dolby digital vista not

  • Thread starter Thread starter markm75
  • Start date Start date
M

markm75

I'm running vista x86 with version 6213 of the realtek apo driver for the
built in realtek sound card on this motherboard (p5n32-sli SE deluxe)..

I had installed the klite mega codec pack at one point.. as well as version
7.3x of PowerDVD.. all was well in the realm of dolby digital (via coax) and
Vista.. i could goto the sounds section of control panel and click on the
dolby digital check box and do a test.. my receiver showed Dolby Digital.. I
also could select spdif in PowerDVD and get dolby digital working fine there
as well..

Now suddenly, i cant get it to work.. its gone from powerdvd and if i do the
test tones section in control panel i get:

"windows was unable to play the test tone"

The only thought i have, is that coax/dolby digital broke after installing
SP1 ? Though i'm not positve.

I'm at a loss.. i've tried removing the 6213 driver completely and
reinstalling.. i've tried other versions of the driver.. i've also tried
reinstalling the codec pack..

I'm not sure if this error message is related to the driver or a codec issue?

One thing i did notice.. if i switched user accounts.. logged in.. for a
split second the test actually worked.. then suddenly it stopped, perhaps
after loading things.. I tried killing every task in taskman that i thought
could be causing an issue, but nothing fixed it..

Any thoughts?

Thanks
 
Chris said:
The only thing I can tell you is that the 1.89 driver from
http://www.realtek.com.tw/downloads/dlhd-2.aspx is working great for me
in Vista 64 with SP1, and the Vista codec pack from
http://shark007.testbox.dk. I'm able to use S/PDIF via toslink to my
receiver. That driver is only a couple days old. Give it a shot.

-Chris
Click to expand...

I found the source of the problem.. this is very odd..

i have a quickcam fusion, which i just recently added.. the quickcam.exe
(quick cam ribbon software) was causing the dolby to not work..

i have no idea why.. but disabling this on startup/not using it, seems to be
the trick.
 
Back
Top