EDIT: this may have been caused by unloading the Terratec driver as you mention in the documentation.
Probably caused by : ntkrpamp.exe ( nt!PnpUnlinkDeviceRemovalRelations+d2 )
BTW, will a future version of the control panel be usable to manage two CMI cards in the same machine...?
- In the Vista control panel, under the "Supported Formats" tab, there is a "test" button where you can check if the soundcard will pass through DD, DTS and WMA Pro. This works perfectly for DD and DTS, but for WMA Pro I get an error message "Windows was unable to play the test tone". But if I enable it anyway, WMA Pro passthrough works perfectly. Only the "Test" feature is broken.
- If I'm running Media Center and put the PC into standby, sound doesn't work correctly when resuming from standby. Sometimes I get silence, and sometimes I get really loud crackly static. If I close and reopen Media Center, it normally starts working properly again (I'm using the latest 1.1.2 drivers with the power management stuff included).
Now, since I have to change it to 2 channel to get spdif out working, but need it on 5.1 to be able to use the analog outs, is there any way to do this from the commandline?
Thanks for the report - I don't have a receiver which can decode WMA Pro so testing is a bit difficult
- I'm guessing that the playback software passes through the WMA Pro stream as AC3/dolby.
You shouldn't need a receiver to test this. The "Test" button simply outputs the WMA Pro signal via SPDIF if the soundcard will allow it, regardless of whether your receiver can decode it.If you get the message "Windows was unable to play the test tone", this means it was rejected by the soundcard. If you get the message "Did you hear the test tone?" this means it was sent successfully, even if your receiver couldn't decode it.
I believe WMA Pro is a completely separate codec from Dolby Digital or DTS. I've had a quick Google, and this link looks relevant:
In any case, WMA Pro passthrough seems to work well with your latest drivers, even though you haven't implemented explicit support.
Hey! I have the Diamond XtremeSound 7.1 and I installed the latest version of these CMI drivers. They installed fine and the output runs fine, but nothing is detecting the analog input. I triple checked to make sure that S/PDIF-in is disabled. It still doesn't seem to be working. Any idea what the problem may be?
... u can turn off the digital interface by selecting a multi channel configuration in your "sounds and audio devices" control panel applet (number of channels >=4).The problem you will run into is that the driver "forgets" the channel configuration after each restart.
Quote from: landsome on 18 March, 2007, 02:39:38 PMHi! PC keeps locking up when I try your drivers; everything works fine until the installation - whether manual or with the installer - tries to copy the control panel file. Then it locks. Tried several driver versions (including 1.0.9) and the behavior is identical. Works fine on my htpc though. Any suggestions anyone?I'd like to ask you for the minidumps for further analysis - Windows creates a minidump in C:\windows\minidump each time it crashes with a BSOD.
Hi! PC keeps locking up when I try your drivers; everything works fine until the installation - whether manual or with the installer - tries to copy the control panel file. Then it locks. Tried several driver versions (including 1.0.9) and the behavior is identical. Works fine on my htpc though. Any suggestions anyone?
Same problem here, with Asrock 939Dual-SATA2 motherboard, a cmi 8768, and Athlon X2 4400. No BSOD but a freeze which corrupt system and need a winXP reinstall. Win is a SP2.
Without reinstall, other device drivers like DVD-reader are corrupted / not activated with an IRQ problem.
No, motherboard's gameport is disabled. There's no gameport on the soundcard.
In fact, to avoid reinstall of my XP, I've reserved an old hd with fresh install for my different tries.Then no problem to test different solutions.
System restore _should_ work if you create a restore point, reboot, try to install the driver and go back to this restore point if it doesn't work.
It doesn't work always. Sometimes, files are corrupted in Windows\system32 directory after reboot, and system can't be restored as it was before.But that's not a problem for me to have a clean directory to restore. It's pretty fast.
Quote from: Koji_kabuto on 15 July, 2007, 04:55:31 PMIt doesn't work always. Sometimes, files are corrupted in Windows\system32 directory after reboot, and system can't be restored as it was before.But that's not a problem for me to have a clean directory to restore. It's pretty fast.have you already tried the debug version I sent you?
Can you give me some advice ?