Messed Up "Audio Codecs Properties" Entries

[Eric]

I'm trying to track down a problem where WMP version 10 can play a wav file,
but other players, such was WinAmp and WMP 6.4, can't. WMP 6.4 keeps trying
to reinstall the Windows Media Audio codec, but that doesn't do any good.

There are a couple of problems I see with my audio codecs, but I'm not sure
how important they are.

1) Voxware Compression Toolkit
When I open "Audio Codecs Properties" from the "Sounds and Audio Devices"
control panel, I see an entry for "Voxware Compression Toolkit", but only
when the "Audio Codecs Properties" window first opens. If I select any
other codec, and look at it's properties, the entry for the "Voxware
Compression Toolkit" just disappears. If, instead, I select the "Voxware
Compression Toolkit" entry first, and hit properties, the "Voxware
Compression Toolkit Properties" window opens, but it's corrupted. Neither
the "Use this audio codec" or "Do not use this audio codec" buttons will
work, and there is no priority, etc. If I click OK, the entry disappears
from "Audio Codecs Properties" window, just as it does if I looked at the
properties for another codec. If I close the "Audio Codecs Properties"
window, and reopen it, the entry is back. If I select the entry and click
on "Remove", I get a warning that it is required by the system. If I remove
it anyway, nothing changes. Rebooting doesn't help.

I've figured out that vct3216.acm and vct3216.dll are part of the Voxware
toolkit, and they may be installed by Office 2000 (which I have) (Ref:
http://support.microsoft.com/default.aspx?scid=kb;en-us;219423). They also
seem to be installed by WME version 7, which I installed, then removed. I
don't have vct3216.dll on my hard drive, but I'm not aware of manually
removing it, either. I did have vct3216.acm, which I renamed. That stopped
msinfo32 from listing the "Voxware Compression Toolkit" (with a condition of
"OK"!!!), but didn't affect the "Audio Codecs Properties" window.

2) Microsoft PCM Converter
This is also listed in the "Audio Codecs Properties" window, with the
highest priority, but not by msinfo32. It's properties box looks
reasonable. I don't know why it would be listed in one place, but not the
other, though.

This all might be a red herring, but I'd like suggestions as to how to clear
up these problems, and even if it is normal to have the Microsoft PCM
converter listed in one list of codecs, but not the other.

Thanks

Eric

 

[zachd [ms]]

I'm trying to track down a problem where WMP version 10 can play a wav
file, but other players, such was WinAmp and WMP 6.4, can't. WMP 6.4
keeps trying to reinstall the Windows Media Audio codec, but that doesn't
do any good.

What file format? If you're trying to play WMA in WAV... I think you might
be out of luck. I know there's a WMV for VCM codec, but I don't recall an
unkeyed WMA for WAV code being generally available. So I think if that that
is your goal, you'd need to convert the file or get it from source using a
different codec for use in WAV...

1) Voxware Compression Toolkit
When I open "Audio Codecs Properties" from the "Sounds and Audio Devices"
control panel, I see an entry for "Voxware Compression Toolkit", but only
when the "Audio Codecs Properties" window first opens. If I select any
other codec, and look at it's properties, the entry for the "Voxware
Compression Toolkit" just disappears. If, instead, I select the "Voxware
Compression Toolkit" entry first, and hit properties, the "Voxware
Compression Toolkit Properties" window opens, but it's corrupted. Neither
the "Use this audio codec" or "Do not use this audio codec" buttons will
work, and there is no priority, etc. If I click OK, the entry disappears
from "Audio Codecs Properties" window, just as it does if I looked at the
properties for another codec. If I close the "Audio Codecs Properties"
window, and reopen it, the entry is back. If I select the entry and click
on "Remove", I get a warning that it is required by the system. If I
remove it anyway, nothing changes. Rebooting doesn't help.

Yes, once you use the "remove" entry, things get screwy and don't really
come back to normal. You can manually change what you see here by editing
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Drivers32 ,
but that control panel you're referring to does NOT work as expected.

-Z