Media Player 11 corruption?

  • Thread starter Thread starter Guest
  • Start date Start date
Here are the two registry keys to play DVDs in Media Player and watch TV/DVD
in Media Center using ATI HD 3450 Hardware Decoder. The system DVD in Media
Player and TV in Media Center simultaneously:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media
Center\Decoder
PreferredMPEG2VideoDecoderCLSID = {212690FB-83E5-4526-8FD7-74478B7939CD}

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media
Center\Service\Video
PreferredMPEG2VideoDecoderCLSID = {37A4D808-E76C-11D2-935C-00A024E52661}

To hear both audio streams, uncheck "Allow Applications to take exclusive
control of this device" in the Advanced tab of play back audio device.

Zack said:
I wrote a response to your post, but the system timed out and I could not
send the response.

So quickly, Media Player takes its Preferred MPEG decoder from Media Center.
You set the MPEG decoder in this key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media
Center\Service\Video]
"UsePeakModeVideoEncoderSettings"=dword:00000001
"AudioOutputFormat"="{696E1D33-548F-4036-825F-7026C60011BD}"
"PreferredMPEG2VideoDecoder"="{37A4D808-E76C-11D2-935C-00A024E52661}"

Then you can also designate any decoder in this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media
Center\Decoder

They do not need to be the same. Which gives you two degrees of freedom.
If the first listed decoder is compatible with Media Player, you can watch
DVDs in Media Player. If it is not, you still can play DVDs and watch TV in
Media Center. In that case, you designate Media Center to play all Media
locally, and Media Player for the lower resoultion Internet media.

The Adobe drivers32 was a solution for solving no sound in Flash player. If
it has "dangerous" enteries in two keys, please advice to remove them.

The solution was deduced from a closely related problem addressed by a
person who was on Microsoft's evaluation team of Vista RC1 and RC2, just I
was.

I use ATI's hardware decoder to utilize acceleration of the display card.
Albeit, it is incompatible with Media Player. Therefore, you designate Media
Center to play all local media at HD capacity of the display card, and
relegate Media Player to play the lower resolution Internet media. They will
coexist perfectly.

As of this date ATI has not published decoders for any of their display
cards that are Media Player compatible. But Media Center uses them witrhout
any problems.

My system plays DVDs and streams TV using ATI drivers at 7-8 Mbps from
PCTOGOTV HD Wireless on N band. Utilizing CPU usage of 23% and memory of
34%, while running Outlook 2007 and multitude of other programs.

Just relegate Media Player to lower resoolution media and Media Center for
the Computer's video display, TV, DVD, etc. in HD display by setting it as
the preferred program for all media with permiussion to access Media Player.

Zack
San Francisco


zachd said:
The values you provided are pretty horrible and dangerous, actually. Is
your system really configured like that?

What Adobe "publishing" are you referring to?

These two specific entries:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
"msacm.iac2"="C:\\WINDOWS\\system32\\iac25_32.ax"
"msacm.voxacm160"="vct3216.acm"
are horrible and dangerous and will probably destabilize your system.
Anybody telling you to add those may not understand precisely what they're
doing. Especially the latter setting.

At some point, had you installed a "codec pack"? That could definitely
stymie even multimedia experts: those are typically breathtakingly badly
designed.

Anyways, the data you provided scares me in its badness: where precisely did
it come from?

--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
Zack said:
The Case ID is SRX1083578172 and was closed as not solved on 11/18/2008.
Since then I have made two major corerections which have resolved the
problem
completely;
1. Designating the Preferred MPEG2 decoder.
2. Registration of driver32 key was provided by Adobe:.

The following are the solutions:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media
Center\Service\Video]
"UsePeakModeVideoEncoderSettings"=dword:00000001
"AudioOutputFormat"="{696E1D33-548F-4036-825F-7026C60011BD}"
"PreferredMPEG2VideoDecoder"="{37A4D808-E76C-11D2-935C-00A024E52661}"

The above is for ATI HD 3450 MPEG Hardware Decoder
{37A4D808-E76C-11D2-935C-00A024E52661}. You simply change this value to a
decoder of your choice.

Adobe published the following for drivers32 key:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32]
"midimapper"="midimap.dll"
"msacm.imaadpcm"="imaadp32.acm"
"msacm.msadpcm"="msadp32.acm"
"msacm.msg711"="msg711.acm"
"msacm.msgsm610"="msgsm32.acm"
"msacm.trspch"="tssoft32.acm"
"vidc.cvid"="iccvid.dll"
"VIDC.I420"="i420vfw.dll"
"vidc.iv31"="ir32_32.dll"
"vidc.iv32"="ir32_32.dll"
"vidc.iv41"="ir41_32.ax"
"VIDC.IYUV"="iyuv_32.dll"
"vidc.mrle"="msrle32.dll"
"vidc.msvc"="msvidc32.dll"
"VIDC.YVYU"="msyuv.dll"
"wavemapper"="msacm32.drv"
"msacm.msg723"="msg723.acm"
"vidc.M263"="msh263.drv"
"vidc.M261"="msh261.drv"
"msacm.msaudio1"="msaud32.acm"
"msacm.sl_anet"="sl_anet.acm"
"msacm.iac2"="C:\\WINDOWS\\system32\\iac25_32.ax"
"vidc.iv50"="ir50_32.dll"
"wave"="wdmaud.drv"
"midi"="wdmaud.drv"
"mixer"="wdmaud.drv"
"VIDC.WMV3"="wmv9vcm.dll"
"VIDC.VP40"="vp4vfw.dll"
"msacm.voxacm160"="vct3216.acm"
"MSVideo"="vfwwdm32.dll"
"MSVideo8"="VfWWDM32.dll"
"wave1"="wdmaud.drv"
"midi1"="wdmaud.drv"
"mixer1"="wdmaud.drv"
"aux"="wdmaud.drv"
"vidc.VP70"="vp7vfw.dll"
"vidc.X264"="x264vfw.dll"
"VIDC.FPS1"="frapsvid.dll"
"vidc.VP60"="vp6vfw.dll"
"vidc.VP61"="vp6vfw.dll"
"vidc.VP62"="vp6vfw.dll"
"vidc.DIVX"="DivX.dll"
"VIDC.UYVY"="msyuv.dll"
"VIDC.YUY2"="msyuv.dll"
"VIDC.YVU9"="tsbyuv.dll"
"VIDC.DRAW"="DVIDEO.DLL"
"VIDC.YV12"="yv12vfw.dll"
"wave2"="wdmaud.drv"
"midi2"="wdmaud.drv"
"mixer2"="wdmaud.drv"
"aux1"="wdmaud.drv"
"wave3"="wdmaud.drv"
"midi3"="wdmaud.drv"
"mixer3"="wdmaud.drv"
"aux2"="wdmaud.drv"
"VIDC.MSUD"="msulvc05.dll"
"wave4"="wdmaud.drv"
"midi4"="wdmaud.drv"
"mixer4"="wdmaud.drv"
"aux3"="wdmaud.drv"
 
Zack said:
The Adobe drivers32 was a solution for solving no sound in Flash player.
If
it has "dangerous" enteries in two keys, please advice to remove them.

Where specifically and exactly did this data come from? It is without
question bad. I would very much appreciate the opportunity to help correct
and eliminate noxiously bad information.

Plus, hey, you're dealing with MPEG filters. Editing the drivers32 key for
an MPEG problem is generally nonsensical.
The solution was deduced from a closely related problem addressed by a
person who was on Microsoft's evaluation team of Vista RC1 and RC2, just I
was.

I don't know if you're indicating that that person was on the public beta,
the private beta, or works at Microsoft. Regardless, that data is pretty
bogus. Oftentimes when people strive for solutions they pull in unrelated
or bad data along the way. This is both. =\

Thanks,
-Zach
 
Dear MSFT:
The data for drivers32 is posted on Adobe website.
I am satisfied and pleased with the performance of my system. If you were
interested in solving problems, you would have provided meaningful
information to everyone a long time ago.
Your thought process is typical of a failed technician. The system works as
I posted.
 
Zack said:
The data for drivers32 is posted on Adobe website.

After you referring to the random forums post by Birdynumnum? That
definitely doesn't appear to have any coherent explanation of what it's
supposed to be doing: it's just a random suggestion for things to add to
your registry. This would explain why it doesn't make any sense.

The birdy reference is all I saw in a quick Internet search. If there's
some other URL you're referring to, it'd be helpful to know what the actual
URL is.
I am satisfied and pleased with the performance of my system. If you were
interested in solving problems, you would have provided meaningful
information to everyone a long time ago.

I'm not sure what problem you're referring to that I don't help out with.
As both a hobby on my personal time and in my career I make a lot of
contributions to helping stabilize the computer world. These contributions
are generally company-agnostic: I've done work with and for most major
companies at some point. You can definitely insult me in a variety of ways,
but depicting me as uninterested in solving problems would be an odd choice.
Especially contextually. I thought your comments were of interest because
if you had dealt with XXX within the support chain you probably would have
run through the XXX tool I made in my free time last month that would have
been very applicable to the symptoms as you described them. But you made no
mention of that, so -- my curiousity was piqued.
Your thought process is typical of a failed technician. The system works
as
I posted.

I don't really know what 'failed technician' means contextually. Imagine
that you solve your health problem through a drug cocktail. A doctor might
note that you don't really need all of that junk and points out that you
only need XXX. That's what I'm doing here.

I am very extremely aware that not everybody would develop problems based
upon the information you provided. That's because they're bogus unhelpful
registry entries on most systems. And for those systems where this would be
bad, I work with others within multimedia to try to defang those third party
timebombs. The biggest nastiness those entries would have created is
generally defanged by Service Pack 1 - but that would still leave older
users in horrible untenable states.

And hey, I'm your friend here. =) I merely helped created chunks of what
you're dealing with, helped solve a variety of interesting problems in this
area, and work with teams on better problem-solving in this arena. I think
it would be unethical of me *not* to point out that those entries are bogus.

But truthfully, anybody who understands what those registry entries could do
could have told you that. If you want to doubt me, I would encourage you to
have anyone else inspect them. =)

Regards,
-Zach
 
Dear MSFT:
http://www.hdtvtunerinfo.com/vistahdtvinstall.html
There are two separate issues here that you are confusing. The Adobe
drivers32 was intended to solve a problem with the sound in their Flash
player. I stated that clearly.
The second is Media Player's inability to play many supported file formats
either of "Not Registered Class" error or any other generic error message.
This forum is to address all Media Player's "corruptions" and errors.
I have shared my experience with addressing some of its endless errors,
including MPEG formats and decoders.
I have identified where Media Player gets its entry for the preferred MPEG
decoder, which is from Media Center.
Furthermore, TV decoding is another fundemental feature of Media Center
which can be assigned independently from the system general MPEG decoder.
Media Player gets its designated decoder from this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media
Center\Decoder
and Media Center can be assigned an independent MPEG decoder in this key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media
Center\Service\Video]
"UsePeakModeVideoEncoderSettings"=dword:00000001
"AudioOutputFormat"="{696E1D33-548F-4036-825F-7026C60011BD}"
"PreferredMPEG2VideoDecoder"="{37A4D808-E76C-11D2-935C-00A024E52661}"

That is all what I wanted to share. The above two keys can, and should have
independent decoders in my opinion.
The system functions perfectly.
Thanks

Zack, PE
San Francisco
 
I'm solely interested right now in the URL on the Adobe site whereby they
said that registering the MetaSound codec was a good plan. You have not
provided any specific reference as regards how nor where the "Adobe"
drivers32 information came from.

The MPEG information you're referring to would only be meaningful within the
actual multiple-filter problem context, which has never been discussed in
full. As such, I'm not interested in that: and since it sounds like you're
up and running, you're not either.

Thus all we're left with is whether or not Adobe is giving out bad
information. From what you've hinted at, this was just a random Adobe forum
comment by somebody who didn't know what they were doing. If this was
actually "Adobe", I'd love more information, since that person really
doesn't understand VfW at all.

Cheers,
-Zach
 
Thank you very much. I very much appreciate that information. =]

Yeah, that's what I thought you were pointing to. The moral of this story
is to be really careful about making registry edits based upon random
suggestions from people that you don't know and don't show area expertise.
VFW can easily be polluted and there's really no great way for the average
user to decorrupt themselves. (Given that it's a deliberately exensible
system, it'd be hard to establish what was good and what was bad.)

Cheers and thanks,
-Zach
 
Dear zach:
It has been a pleasure reading your responses. The goal is to have Vista
and Media Player to be user friendly. Media Player's demeanor has to improve.
Having said that, I found the following drivers32 list is justifiable and
achievable.
The Credit goes to a utility found at:
http://www.am-softhome.com/avidiag.html

I hope that this thread would help seekers of knowledge about the great
operating systems by Microsoft.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
"midimapper"="midimap.dll"
"msacm.imaadpcm"="imaadp32.acm"
"msacm.msadpcm"="msadp32.acm"
"msacm.msg711"="msg711.acm"
"msacm.msgsm610"="msgsm32.acm"
"vidc.cvid"="iccvid.dll"
"vidc.iv31"="ir32_32.dll"
"vidc.iv32"="ir32_32.dll"
"vidc.iv41"="ir41_32.dll"
"VIDC.IYUV"="iyuv_32.dll"
"vidc.mrle"="msrle32.dll"
"vidc.msvc"="msvidc32.dll"
"VIDC.YVYU"="msyuv.dll"
"wavemapper"="msacm32.drv"
"msacm.msaudio1"="msaud32.acm"
"msacm.sl_anet"="sl_anet.acm"
"msacm.iac2"="C:\\WINDOWS\\system32\\iac25_32.ax"
"vidc.iv50"="ir50_32.dll"
"wave"="wdmaud.drv"
"midi"="wdmaud.drv"
"mixer"="wdmaud.drv"
"VIDC.WMV3"="wmv9vcm.dll"
"msacm.voxacm160"="vct3216.acm"
"MSVideo"="mciavi32.dll"
"MSVideo8"="VfWWDM32.dll"
"wave1"="wdmaud.drv"
"midi1"="wdmaud.drv"
"mixer1"="wdmaud.drv"
"aux"="wdmaud.drv"
"VIDC.UYVY"="msyuv.dll"
"VIDC.YUY2"="msyuv.dll"
"VIDC.YVU9"="iyvu9_32.dll"
"wave2"="wdmaud.drv"
"midi2"="wdmaud.drv"
"mixer2"="wdmaud.drv"
"aux1"="wdmaud.drv"
"wave3"="wdmaud.drv"
"midi3"="wdmaud.drv"
"mixer3"="wdmaud.drv"
"aux2"="wdmaud.drv"
"wave4"="wdmaud.drv"
"midi4"="wdmaud.drv"
"mixer4"="wdmaud.drv"
"aux3"="wdmaud.drv"
"wave5"="wdmaud.drv"
"midi5"="wdmaud.drv"
"mixer5"="wdmaud.drv"
"aux4"="wdmaud.drv"
"wave6"="wdmaud.drv"
"midi6"="wdmaud.drv"
"mixer6"="wdmaud.drv"
"aux5"="wdmaud.drv"
"msacm.l3acm"="C:\\WINDOWS\\system32\\l3codeca.acm"
"msacm.siren"="sirenacm.dll"
"wave8"="wdmaud.drv"
"midi7"="wdmaud.drv"
"mixer8"="wdmaud.drv"
"wave9"="wdmaud.drv"
"midi8"="wdmaud.drv"
"mixer9"="wdmaud.drv"
"wave7"="wdmaud.drv"
"mixer7"="wdmaud.drv"
"midi9"="wdmaud.drv"
"vids.mjpg"="mciavi32.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server\RDP]
"wave"="rdpsnd.dll"
"mixer"="rdpsnd.dll"
"MaxBandwidth"=dword:000056b9
"wavemapper"="msacm32.drv"
"EnableMP3Codec"=dword:00000001
"midimapper"="midimap.dll"



zachd said:
Thank you very much. I very much appreciate that information. =]

Yeah, that's what I thought you were pointing to. The moral of this story
is to be really careful about making registry edits based upon random
suggestions from people that you don't know and don't show area expertise.
VFW can easily be polluted and there's really no great way for the average
user to decorrupt themselves. (Given that it's a deliberately exensible
system, it'd be hard to establish what was good and what was bad.)

Cheers and thanks,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
Zack said:
Here are two links of the source of Adobe information for "No Sound"
Problem
in Flash Player. Again this part of discussion is regarding SOUND only
and
does not affect any other discussion topic of this thread!

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y
 
I guarantee you that the information you just presented is bad, corrupt, and
incompetent. Much of the information you are referring to directly refers
to items I either worked on or have had some level of development
responsibility or have a high level of knowledge on, usually far beyond what
anyone not directly involved with the companies in question would have. It
is extremely doubtful that anyone you can possibly refer to knows more about
this particular area than I do. That's stated as a matter of fact and not a
matter of opinion.

I will repeat that any advice that tells someone to add the registry value
"msacm.voxacm160"="vct3216.acm"
to their Vista system is abjectly and utterly indefensibly incompetent.

That's really it. That can't be defended.

I appreciate that peoples have different levels of knowledge in different
fields. This particular field happens to be an area I am an expert in. I
thank you for understanding the limits of your own understanding of this
field and not propagating bad advice.

I can not see anyone in good faith continuing this conversation. If this
does continue, I'm going to assume that you're simply trolling. The Voxware
entry (and other entries you're referring to) were created in part by me
personally way back when, so again: this isn't conjecture nor debatable.
The data you're suggesting is simply and flatly wrong.

Thank you,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
Zack said:
Dear zach:
It has been a pleasure reading your responses. The goal is to have Vista
and Media Player to be user friendly. Media Player's demeanor has to
improve.
Having said that, I found the following drivers32 list is justifiable and
achievable.
The Credit goes to a utility found at:
http://www.am-softhome.com/avidiag.html

I hope that this thread would help seekers of knowledge about the great
operating systems by Microsoft.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32]
"midimapper"="midimap.dll"
"msacm.imaadpcm"="imaadp32.acm"
"msacm.msadpcm"="msadp32.acm"
"msacm.msg711"="msg711.acm"
"msacm.msgsm610"="msgsm32.acm"
"vidc.cvid"="iccvid.dll"
"vidc.iv31"="ir32_32.dll"
"vidc.iv32"="ir32_32.dll"
"vidc.iv41"="ir41_32.dll"
"VIDC.IYUV"="iyuv_32.dll"
"vidc.mrle"="msrle32.dll"
"vidc.msvc"="msvidc32.dll"
"VIDC.YVYU"="msyuv.dll"
"wavemapper"="msacm32.drv"
"msacm.msaudio1"="msaud32.acm"
"msacm.sl_anet"="sl_anet.acm"
"msacm.iac2"="C:\\WINDOWS\\system32\\iac25_32.ax"
"vidc.iv50"="ir50_32.dll"
"wave"="wdmaud.drv"
"midi"="wdmaud.drv"
"mixer"="wdmaud.drv"
"VIDC.WMV3"="wmv9vcm.dll"
"msacm.voxacm160"="vct3216.acm"
"MSVideo"="mciavi32.dll"
"MSVideo8"="VfWWDM32.dll"
"wave1"="wdmaud.drv"
"midi1"="wdmaud.drv"
"mixer1"="wdmaud.drv"
"aux"="wdmaud.drv"
"VIDC.UYVY"="msyuv.dll"
"VIDC.YUY2"="msyuv.dll"
"VIDC.YVU9"="iyvu9_32.dll"
"wave2"="wdmaud.drv"
"midi2"="wdmaud.drv"
"mixer2"="wdmaud.drv"
"aux1"="wdmaud.drv"
"wave3"="wdmaud.drv"
"midi3"="wdmaud.drv"
"mixer3"="wdmaud.drv"
"aux2"="wdmaud.drv"
"wave4"="wdmaud.drv"
"midi4"="wdmaud.drv"
"mixer4"="wdmaud.drv"
"aux3"="wdmaud.drv"
"wave5"="wdmaud.drv"
"midi5"="wdmaud.drv"
"mixer5"="wdmaud.drv"
"aux4"="wdmaud.drv"
"wave6"="wdmaud.drv"
"midi6"="wdmaud.drv"
"mixer6"="wdmaud.drv"
"aux5"="wdmaud.drv"
"msacm.l3acm"="C:\\WINDOWS\\system32\\l3codeca.acm"
"msacm.siren"="sirenacm.dll"
"wave8"="wdmaud.drv"
"midi7"="wdmaud.drv"
"mixer8"="wdmaud.drv"
"wave9"="wdmaud.drv"
"midi8"="wdmaud.drv"
"mixer9"="wdmaud.drv"
"wave7"="wdmaud.drv"
"mixer7"="wdmaud.drv"
"midi9"="wdmaud.drv"
"vids.mjpg"="mciavi32.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server\RDP]
"wave"="rdpsnd.dll"
"mixer"="rdpsnd.dll"
"MaxBandwidth"=dword:000056b9
"wavemapper"="msacm32.drv"
"EnableMP3Codec"=dword:00000001
"midimapper"="midimap.dll"



zachd said:
Thank you very much. I very much appreciate that information. =]

Yeah, that's what I thought you were pointing to. The moral of this
story
is to be really careful about making registry edits based upon random
suggestions from people that you don't know and don't show area
expertise.
VFW can easily be polluted and there's really no great way for the
average
user to decorrupt themselves. (Given that it's a deliberately exensible
system, it'd be hard to establish what was good and what was bad.)

Cheers and thanks,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
--
Zack said:
Here are two links of the source of Adobe information for "No Sound"
Problem
in Flash Player. Again this part of discussion is regarding SOUND only
and
does not affect any other discussion topic of this thread!

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y

:


I'm solely interested right now in the URL on the Adobe site whereby
they
said that registering the MetaSound codec was a good plan. You have
not
provided any specific reference as regards how nor where the "Adobe"
drivers32 information came from.

The MPEG information you're referring to would only be meaningful
within
the
actual multiple-filter problem context, which has never been discussed
in
full. As such, I'm not interested in that: and since it sounds like
you're
up and running, you're not either.

Thus all we're left with is whether or not Adobe is giving out bad
information. From what you've hinted at, this was just a random Adobe
forum
comment by somebody who didn't know what they were doing. If this was
actually "Adobe", I'd love more information, since that person really
doesn't understand VfW at all.

Cheers,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
 
Dear Zach:
If the entry for msacm.voxacm160 is wrong, then just state so.
WMPLugins.com offers it as a remedy for all ills of Media Player without any
reservation about Vista.
http://www.wmplugins.com/ItemDetail.aspx?ItemID=723
I was directed there by Media Player's web help, which is useless to start
with.
Thank you for your passion for Vista.



zachd said:
I guarantee you that the information you just presented is bad, corrupt, and
incompetent. Much of the information you are referring to directly refers
to items I either worked on or have had some level of development
responsibility or have a high level of knowledge on, usually far beyond what
anyone not directly involved with the companies in question would have. It
is extremely doubtful that anyone you can possibly refer to knows more about
this particular area than I do. That's stated as a matter of fact and not a
matter of opinion.

I will repeat that any advice that tells someone to add the registry value
"msacm.voxacm160"="vct3216.acm"
to their Vista system is abjectly and utterly indefensibly incompetent.

That's really it. That can't be defended.

I appreciate that peoples have different levels of knowledge in different
fields. This particular field happens to be an area I am an expert in. I
thank you for understanding the limits of your own understanding of this
field and not propagating bad advice.

I can not see anyone in good faith continuing this conversation. If this
does continue, I'm going to assume that you're simply trolling. The Voxware
entry (and other entries you're referring to) were created in part by me
personally way back when, so again: this isn't conjecture nor debatable.
The data you're suggesting is simply and flatly wrong.

Thank you,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
Zack said:
Dear zach:
It has been a pleasure reading your responses. The goal is to have Vista
and Media Player to be user friendly. Media Player's demeanor has to
improve.
Having said that, I found the following drivers32 list is justifiable and
achievable.
The Credit goes to a utility found at:
http://www.am-softhome.com/avidiag.html

I hope that this thread would help seekers of knowledge about the great
operating systems by Microsoft.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32]
"midimapper"="midimap.dll"
"msacm.imaadpcm"="imaadp32.acm"
"msacm.msadpcm"="msadp32.acm"
"msacm.msg711"="msg711.acm"
"msacm.msgsm610"="msgsm32.acm"
"vidc.cvid"="iccvid.dll"
"vidc.iv31"="ir32_32.dll"
"vidc.iv32"="ir32_32.dll"
"vidc.iv41"="ir41_32.dll"
"VIDC.IYUV"="iyuv_32.dll"
"vidc.mrle"="msrle32.dll"
"vidc.msvc"="msvidc32.dll"
"VIDC.YVYU"="msyuv.dll"
"wavemapper"="msacm32.drv"
"msacm.msaudio1"="msaud32.acm"
"msacm.sl_anet"="sl_anet.acm"
"msacm.iac2"="C:\\WINDOWS\\system32\\iac25_32.ax"
"vidc.iv50"="ir50_32.dll"
"wave"="wdmaud.drv"
"midi"="wdmaud.drv"
"mixer"="wdmaud.drv"
"VIDC.WMV3"="wmv9vcm.dll"
"msacm.voxacm160"="vct3216.acm"
"MSVideo"="mciavi32.dll"
"MSVideo8"="VfWWDM32.dll"
"wave1"="wdmaud.drv"
"midi1"="wdmaud.drv"
"mixer1"="wdmaud.drv"
"aux"="wdmaud.drv"
"VIDC.UYVY"="msyuv.dll"
"VIDC.YUY2"="msyuv.dll"
"VIDC.YVU9"="iyvu9_32.dll"
"wave2"="wdmaud.drv"
"midi2"="wdmaud.drv"
"mixer2"="wdmaud.drv"
"aux1"="wdmaud.drv"
"wave3"="wdmaud.drv"
"midi3"="wdmaud.drv"
"mixer3"="wdmaud.drv"
"aux2"="wdmaud.drv"
"wave4"="wdmaud.drv"
"midi4"="wdmaud.drv"
"mixer4"="wdmaud.drv"
"aux3"="wdmaud.drv"
"wave5"="wdmaud.drv"
"midi5"="wdmaud.drv"
"mixer5"="wdmaud.drv"
"aux4"="wdmaud.drv"
"wave6"="wdmaud.drv"
"midi6"="wdmaud.drv"
"mixer6"="wdmaud.drv"
"aux5"="wdmaud.drv"
"msacm.l3acm"="C:\\WINDOWS\\system32\\l3codeca.acm"
"msacm.siren"="sirenacm.dll"
"wave8"="wdmaud.drv"
"midi7"="wdmaud.drv"
"mixer8"="wdmaud.drv"
"wave9"="wdmaud.drv"
"midi8"="wdmaud.drv"
"mixer9"="wdmaud.drv"
"wave7"="wdmaud.drv"
"mixer7"="wdmaud.drv"
"midi9"="wdmaud.drv"
"vids.mjpg"="mciavi32.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server\RDP]
"wave"="rdpsnd.dll"
"mixer"="rdpsnd.dll"
"MaxBandwidth"=dword:000056b9
"wavemapper"="msacm32.drv"
"EnableMP3Codec"=dword:00000001
"midimapper"="midimap.dll"



zachd said:
Thank you very much. I very much appreciate that information. =]

Yeah, that's what I thought you were pointing to. The moral of this
story
is to be really careful about making registry edits based upon random
suggestions from people that you don't know and don't show area
expertise.
VFW can easily be polluted and there's really no great way for the
average
user to decorrupt themselves. (Given that it's a deliberately exensible
system, it'd be hard to establish what was good and what was bad.)

Cheers and thanks,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
--
Here are two links of the source of Adobe information for "No Sound"
Problem
in Flash Player. Again this part of discussion is regarding SOUND only
and
does not affect any other discussion topic of this thread!

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y

:


I'm solely interested right now in the URL on the Adobe site whereby
they
said that registering the MetaSound codec was a good plan. You have
not
provided any specific reference as regards how nor where the "Adobe"
drivers32 information came from.

The MPEG information you're referring to would only be meaningful
within
the
actual multiple-filter problem context, which has never been discussed
in
full. As such, I'm not interested in that: and since it sounds like
you're
up and running, you're not either.

Thus all we're left with is whether or not Adobe is giving out bad
information. From what you've hinted at, this was just a random Adobe
forum
comment by somebody who didn't know what they were doing. If this was
actually "Adobe", I'd love more information, since that person really
doesn't understand VfW at all.

Cheers,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
 
There are numerous errors in the data you mention, including another system
crippling error. Voxware is simply one specific and exact example. If you
actually care about the data, I would suggest you investigate it to
understand what it does, because it doesn't do nearly what you think it
does. Given that you pasted that data verbatim, you seemingly don't have
any understanding of the specifics of what you're referring to. This isn't
some Rain Dance here - this is precise technical information, and what
you've quoted is utter bollocks. I apologize that there's such abjectly
utterly incompetent people wasting your and other's times. I would love it
if you would not waste my time too.

That WMPlugins.com page is in error here. The right person to fix that up
is doing much more important stuff right now, but it's on the radar to get
fixed up.
The Web Help for codecs is actually pretty good. It's an exceedingly
complex problem, compounded by the fact that the AVI land is lorded over by
a lot of truly incompetent people propagating bad methodologies, bad ethics,
and bad code. AVI is rather a joke at this time in my opinion.

Are you really trying to play Voxware MetaSound on Windows Vista? That will
either not work or it will cripple your system AND not work. You cannot do
this. You should convert the content to use an audio codec that is
supported and doesn't contain serious bugs.

Anyways, I can only take so much bloody-mindedness surrounding an issue.
The data you're parroting was put together by incompetent hacks who never
understood a fraction of what I do. Because you're simply reiterating their
tripe, it's not possible to have a meaningful and smart conversation about
the subject. The discussion fails at face value because you don't seem to
understand that most of those settings won't even do anything: they're just
noise.

I love you and I'm one of the people trying to help rescue AVI from the
abject morass it's been led into. As part of that, I need to avoid getting
engaged in conversations that aren't going anywhere. The data you've
provided is wrong and dangerously wrong, end of story. =)

Kind regards and signing off from this conversation,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
Zack said:
Dear Zach:
If the entry for msacm.voxacm160 is wrong, then just state so.
WMPLugins.com offers it as a remedy for all ills of Media Player without
any
reservation about Vista.
http://www.wmplugins.com/ItemDetail.aspx?ItemID=723
I was directed there by Media Player's web help, which is useless to start
with.
Thank you for your passion for Vista.



zachd said:
I guarantee you that the information you just presented is bad, corrupt,
and
incompetent. Much of the information you are referring to directly
refers
to items I either worked on or have had some level of development
responsibility or have a high level of knowledge on, usually far beyond
what
anyone not directly involved with the companies in question would have.
It
is extremely doubtful that anyone you can possibly refer to knows more
about
this particular area than I do. That's stated as a matter of fact and
not a
matter of opinion.

I will repeat that any advice that tells someone to add the registry
value
"msacm.voxacm160"="vct3216.acm"
to their Vista system is abjectly and utterly indefensibly incompetent.

That's really it. That can't be defended.

I appreciate that peoples have different levels of knowledge in different
fields. This particular field happens to be an area I am an expert in.
I
thank you for understanding the limits of your own understanding of this
field and not propagating bad advice.

I can not see anyone in good faith continuing this conversation. If this
does continue, I'm going to assume that you're simply trolling. The
Voxware
entry (and other entries you're referring to) were created in part by me
personally way back when, so again: this isn't conjecture nor debatable.
The data you're suggesting is simply and flatly wrong.

Thank you,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
--
Zack said:
Dear zach:
It has been a pleasure reading your responses. The goal is to have
Vista
and Media Player to be user friendly. Media Player's demeanor has to
improve.
Having said that, I found the following drivers32 list is justifiable
and
achievable.
The Credit goes to a utility found at:
http://www.am-softhome.com/avidiag.html

I hope that this thread would help seekers of knowledge about the great
operating systems by Microsoft.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32]
"midimapper"="midimap.dll"
"msacm.imaadpcm"="imaadp32.acm"
"msacm.msadpcm"="msadp32.acm"
"msacm.msg711"="msg711.acm"
"msacm.msgsm610"="msgsm32.acm"
"vidc.cvid"="iccvid.dll"
"vidc.iv31"="ir32_32.dll"
"vidc.iv32"="ir32_32.dll"
"vidc.iv41"="ir41_32.dll"
"VIDC.IYUV"="iyuv_32.dll"
"vidc.mrle"="msrle32.dll"
"vidc.msvc"="msvidc32.dll"
"VIDC.YVYU"="msyuv.dll"
"wavemapper"="msacm32.drv"
"msacm.msaudio1"="msaud32.acm"
"msacm.sl_anet"="sl_anet.acm"
"msacm.iac2"="C:\\WINDOWS\\system32\\iac25_32.ax"
"vidc.iv50"="ir50_32.dll"
"wave"="wdmaud.drv"
"midi"="wdmaud.drv"
"mixer"="wdmaud.drv"
"VIDC.WMV3"="wmv9vcm.dll"
"msacm.voxacm160"="vct3216.acm"
"MSVideo"="mciavi32.dll"
"MSVideo8"="VfWWDM32.dll"
"wave1"="wdmaud.drv"
"midi1"="wdmaud.drv"
"mixer1"="wdmaud.drv"
"aux"="wdmaud.drv"
"VIDC.UYVY"="msyuv.dll"
"VIDC.YUY2"="msyuv.dll"
"VIDC.YVU9"="iyvu9_32.dll"
"wave2"="wdmaud.drv"
"midi2"="wdmaud.drv"
"mixer2"="wdmaud.drv"
"aux1"="wdmaud.drv"
"wave3"="wdmaud.drv"
"midi3"="wdmaud.drv"
"mixer3"="wdmaud.drv"
"aux2"="wdmaud.drv"
"wave4"="wdmaud.drv"
"midi4"="wdmaud.drv"
"mixer4"="wdmaud.drv"
"aux3"="wdmaud.drv"
"wave5"="wdmaud.drv"
"midi5"="wdmaud.drv"
"mixer5"="wdmaud.drv"
"aux4"="wdmaud.drv"
"wave6"="wdmaud.drv"
"midi6"="wdmaud.drv"
"mixer6"="wdmaud.drv"
"aux5"="wdmaud.drv"
"msacm.l3acm"="C:\\WINDOWS\\system32\\l3codeca.acm"
"msacm.siren"="sirenacm.dll"
"wave8"="wdmaud.drv"
"midi7"="wdmaud.drv"
"mixer8"="wdmaud.drv"
"wave9"="wdmaud.drv"
"midi8"="wdmaud.drv"
"mixer9"="wdmaud.drv"
"wave7"="wdmaud.drv"
"mixer7"="wdmaud.drv"
"midi9"="wdmaud.drv"
"vids.mjpg"="mciavi32.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server\RDP]
"wave"="rdpsnd.dll"
"mixer"="rdpsnd.dll"
"MaxBandwidth"=dword:000056b9
"wavemapper"="msacm32.drv"
"EnableMP3Codec"=dword:00000001
"midimapper"="midimap.dll"



:


Thank you very much. I very much appreciate that information. =]

Yeah, that's what I thought you were pointing to. The moral of this
story
is to be really careful about making registry edits based upon random
suggestions from people that you don't know and don't show area
expertise.
VFW can easily be polluted and there's really no great way for the
average
user to decorrupt themselves. (Given that it's a deliberately
exensible
system, it'd be hard to establish what was good and what was bad.)

Cheers and thanks,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
--
Here are two links of the source of Adobe information for "No Sound"
Problem
in Flash Player. Again this part of discussion is regarding SOUND
only
and
does not affect any other discussion topic of this thread!

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y

:


I'm solely interested right now in the URL on the Adobe site
whereby
they
said that registering the MetaSound codec was a good plan. You
have
not
provided any specific reference as regards how nor where the
"Adobe"
drivers32 information came from.

The MPEG information you're referring to would only be meaningful
within
the
actual multiple-filter problem context, which has never been
discussed
in
full. As such, I'm not interested in that: and since it sounds
like
you're
up and running, you're not either.

Thus all we're left with is whether or not Adobe is giving out bad
information. From what you've hinted at, this was just a random
Adobe
forum
comment by somebody who didn't know what they were doing. If this
was
actually "Adobe", I'd love more information, since that person
really
doesn't understand VfW at all.

Cheers,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
 
Dear Zack:
I was inspired by your use of the "noise". Here is my current
configuration, and the system works great without all that "noise"

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers]
"timer"="timer.drv"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers.desc]
"wdmaud.drv"="Microsoft 1.1 UAA Function Driver for High Definition Audio"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
"wavemapper"="msacm32.drv"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\IniFileMapping]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\IniFileMapping\system.ini]
"boot.description"="SYS:Microsoft\\Windows
NT\\CurrentVersion\\WOW\\boot.description"
"keyboard"="SYS:Microsoft\\Windows NT\\CurrentVersion\\WOW\\keyboard"
"NonWindowsApp"="SYS:Microsoft\\Windows
NT\\CurrentVersion\\WOW\\NonWindowsApp"
"standard"="SYS:Microsoft\\Windows NT\\CurrentVersion\\WOW\\standard"
"Drivers"="SYS:Microsoft\\Windows NT\\CurrentVersion\\Drivers"
"drivers32"="SYS:Microsoft\\Windows NT\\CurrentVersion\\Drivers32"
"MCI32"="SYS:Microsoft\\Windows NT\\CurrentVersion\\MCI32"
"msacm32.drv"="USR:Software\\Microsoft\\Multimedia\\Sound Mapper"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\IniFileMapping\system.ini\Shell]
@="SHELL32.DLL"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\MCI32]
"WaveAudio"="wdmaud.drv"


Zack
San Francisco
Where the Men are Beautiful and the Womyn are Strong

zachd said:
There are numerous errors in the data you mention, including another system
crippling error. Voxware is simply one specific and exact example. If you
actually care about the data, I would suggest you investigate it to
understand what it does, because it doesn't do nearly what you think it
does. Given that you pasted that data verbatim, you seemingly don't have
any understanding of the specifics of what you're referring to. This isn't
some Rain Dance here - this is precise technical information, and what
you've quoted is utter bollocks. I apologize that there's such abjectly
utterly incompetent people wasting your and other's times. I would love it
if you would not waste my time too.

That WMPlugins.com page is in error here. The right person to fix that up
is doing much more important stuff right now, but it's on the radar to get
fixed up.
The Web Help for codecs is actually pretty good. It's an exceedingly
complex problem, compounded by the fact that the AVI land is lorded over by
a lot of truly incompetent people propagating bad methodologies, bad ethics,
and bad code. AVI is rather a joke at this time in my opinion.

Are you really trying to play Voxware MetaSound on Windows Vista? That will
either not work or it will cripple your system AND not work. You cannot do
this. You should convert the content to use an audio codec that is
supported and doesn't contain serious bugs.

Anyways, I can only take so much bloody-mindedness surrounding an issue.
The data you're parroting was put together by incompetent hacks who never
understood a fraction of what I do. Because you're simply reiterating their
tripe, it's not possible to have a meaningful and smart conversation about
the subject. The discussion fails at face value because you don't seem to
understand that most of those settings won't even do anything: they're just
noise.

I love you and I'm one of the people trying to help rescue AVI from the
abject morass it's been led into. As part of that, I need to avoid getting
engaged in conversations that aren't going anywhere. The data you've
provided is wrong and dangerously wrong, end of story. =)

Kind regards and signing off from this conversation,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
Zack said:
Dear Zach:
If the entry for msacm.voxacm160 is wrong, then just state so.
WMPLugins.com offers it as a remedy for all ills of Media Player without
any
reservation about Vista.
http://www.wmplugins.com/ItemDetail.aspx?ItemID=723
I was directed there by Media Player's web help, which is useless to start
with.
Thank you for your passion for Vista.



zachd said:
I guarantee you that the information you just presented is bad, corrupt,
and
incompetent. Much of the information you are referring to directly
refers
to items I either worked on or have had some level of development
responsibility or have a high level of knowledge on, usually far beyond
what
anyone not directly involved with the companies in question would have.
It
is extremely doubtful that anyone you can possibly refer to knows more
about
this particular area than I do. That's stated as a matter of fact and
not a
matter of opinion.

I will repeat that any advice that tells someone to add the registry
value
"msacm.voxacm160"="vct3216.acm"
to their Vista system is abjectly and utterly indefensibly incompetent.

That's really it. That can't be defended.

I appreciate that peoples have different levels of knowledge in different
fields. This particular field happens to be an area I am an expert in.
I
thank you for understanding the limits of your own understanding of this
field and not propagating bad advice.

I can not see anyone in good faith continuing this conversation. If this
does continue, I'm going to assume that you're simply trolling. The
Voxware
entry (and other entries you're referring to) were created in part by me
personally way back when, so again: this isn't conjecture nor debatable.
The data you're suggesting is simply and flatly wrong.

Thank you,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
--
Dear zach:
It has been a pleasure reading your responses. The goal is to have
Vista
and Media Player to be user friendly. Media Player's demeanor has to
improve.
Having said that, I found the following drivers32 list is justifiable
and
achievable.
The Credit goes to a utility found at:
http://www.am-softhome.com/avidiag.html

I hope that this thread would help seekers of knowledge about the great
operating systems by Microsoft.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32]
"midimapper"="midimap.dll"
"msacm.imaadpcm"="imaadp32.acm"
"msacm.msadpcm"="msadp32.acm"
"msacm.msg711"="msg711.acm"
"msacm.msgsm610"="msgsm32.acm"
"vidc.cvid"="iccvid.dll"
"vidc.iv31"="ir32_32.dll"
"vidc.iv32"="ir32_32.dll"
"vidc.iv41"="ir41_32.dll"
"VIDC.IYUV"="iyuv_32.dll"
"vidc.mrle"="msrle32.dll"
"vidc.msvc"="msvidc32.dll"
"VIDC.YVYU"="msyuv.dll"
"wavemapper"="msacm32.drv"
"msacm.msaudio1"="msaud32.acm"
"msacm.sl_anet"="sl_anet.acm"
"msacm.iac2"="C:\\WINDOWS\\system32\\iac25_32.ax"
"vidc.iv50"="ir50_32.dll"
"wave"="wdmaud.drv"
"midi"="wdmaud.drv"
"mixer"="wdmaud.drv"
"VIDC.WMV3"="wmv9vcm.dll"
"msacm.voxacm160"="vct3216.acm"
"MSVideo"="mciavi32.dll"
"MSVideo8"="VfWWDM32.dll"
"wave1"="wdmaud.drv"
"midi1"="wdmaud.drv"
"mixer1"="wdmaud.drv"
"aux"="wdmaud.drv"
"VIDC.UYVY"="msyuv.dll"
"VIDC.YUY2"="msyuv.dll"
"VIDC.YVU9"="iyvu9_32.dll"
"wave2"="wdmaud.drv"
"midi2"="wdmaud.drv"
"mixer2"="wdmaud.drv"
"aux1"="wdmaud.drv"
"wave3"="wdmaud.drv"
"midi3"="wdmaud.drv"
"mixer3"="wdmaud.drv"
"aux2"="wdmaud.drv"
"wave4"="wdmaud.drv"
"midi4"="wdmaud.drv"
"mixer4"="wdmaud.drv"
"aux3"="wdmaud.drv"
"wave5"="wdmaud.drv"
"midi5"="wdmaud.drv"
"mixer5"="wdmaud.drv"
"aux4"="wdmaud.drv"
"wave6"="wdmaud.drv"
"midi6"="wdmaud.drv"
"mixer6"="wdmaud.drv"
"aux5"="wdmaud.drv"
"msacm.l3acm"="C:\\WINDOWS\\system32\\l3codeca.acm"
"msacm.siren"="sirenacm.dll"
"wave8"="wdmaud.drv"
"midi7"="wdmaud.drv"
"mixer8"="wdmaud.drv"
"wave9"="wdmaud.drv"
"midi8"="wdmaud.drv"
"mixer9"="wdmaud.drv"
"wave7"="wdmaud.drv"
"mixer7"="wdmaud.drv"
"midi9"="wdmaud.drv"
"vids.mjpg"="mciavi32.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server\RDP]
"wave"="rdpsnd.dll"
"mixer"="rdpsnd.dll"
"MaxBandwidth"=dword:000056b9
"wavemapper"="msacm32.drv"
"EnableMP3Codec"=dword:00000001
"midimapper"="midimap.dll"



:


Thank you very much. I very much appreciate that information. =]

Yeah, that's what I thought you were pointing to. The moral of this
story
is to be really careful about making registry edits based upon random
suggestions from people that you don't know and don't show area
expertise.
VFW can easily be polluted and there's really no great way for the
average
user to decorrupt themselves. (Given that it's a deliberately
exensible
system, it'd be hard to establish what was good and what was bad.)

Cheers and thanks,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
--
Here are two links of the source of Adobe information for "No Sound"
Problem
in Flash Player. Again this part of discussion is regarding SOUND
only
and
does not affect any other discussion topic of this thread!

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y

:


I'm solely interested right now in the URL on the Adobe site
whereby
they
said that registering the MetaSound codec was a good plan. You
have
not
provided any specific reference as regards how nor where the
"Adobe"
drivers32 information came from.

The MPEG information you're referring to would only be meaningful
within
the
actual multiple-filter problem context, which has never been
discussed
in
full. As such, I'm not interested in that: and since it sounds
like
you're
up and running, you're not either.

Thus all we're left with is whether or not Adobe is giving out bad
information. From what you've hinted at, this was just a random
Adobe
forum
comment by somebody who didn't know what they were doing. If this
was
actually "Adobe", I'd love more information, since that person
really
doesn't understand VfW at all.

Cheers,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
 
For complete configuration please see:
http://zshahin.spaces.live.com/

Zack said:
Dear Zack:
I was inspired by your use of the "noise". Here is my current
configuration, and the system works great without all that "noise"

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers]
"timer"="timer.drv"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers.desc]
"wdmaud.drv"="Microsoft 1.1 UAA Function Driver for High Definition Audio"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32]
"wavemapper"="msacm32.drv"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\IniFileMapping]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\IniFileMapping\system.ini]
"boot.description"="SYS:Microsoft\\Windows
NT\\CurrentVersion\\WOW\\boot.description"
"keyboard"="SYS:Microsoft\\Windows NT\\CurrentVersion\\WOW\\keyboard"
"NonWindowsApp"="SYS:Microsoft\\Windows
NT\\CurrentVersion\\WOW\\NonWindowsApp"
"standard"="SYS:Microsoft\\Windows NT\\CurrentVersion\\WOW\\standard"
"Drivers"="SYS:Microsoft\\Windows NT\\CurrentVersion\\Drivers"
"drivers32"="SYS:Microsoft\\Windows NT\\CurrentVersion\\Drivers32"
"MCI32"="SYS:Microsoft\\Windows NT\\CurrentVersion\\MCI32"
"msacm32.drv"="USR:Software\\Microsoft\\Multimedia\\Sound Mapper"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\IniFileMapping\system.ini\Shell]
@="SHELL32.DLL"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\MCI32]
"WaveAudio"="wdmaud.drv"


Zack
San Francisco
Where the Men are Beautiful and the Womyn are Strong

zachd said:
There are numerous errors in the data you mention, including another system
crippling error. Voxware is simply one specific and exact example. If you
actually care about the data, I would suggest you investigate it to
understand what it does, because it doesn't do nearly what you think it
does. Given that you pasted that data verbatim, you seemingly don't have
any understanding of the specifics of what you're referring to. This isn't
some Rain Dance here - this is precise technical information, and what
you've quoted is utter bollocks. I apologize that there's such abjectly
utterly incompetent people wasting your and other's times. I would love it
if you would not waste my time too.

That WMPlugins.com page is in error here. The right person to fix that up
is doing much more important stuff right now, but it's on the radar to get
fixed up.
The Web Help for codecs is actually pretty good. It's an exceedingly
complex problem, compounded by the fact that the AVI land is lorded over by
a lot of truly incompetent people propagating bad methodologies, bad ethics,
and bad code. AVI is rather a joke at this time in my opinion.

Are you really trying to play Voxware MetaSound on Windows Vista? That will
either not work or it will cripple your system AND not work. You cannot do
this. You should convert the content to use an audio codec that is
supported and doesn't contain serious bugs.

Anyways, I can only take so much bloody-mindedness surrounding an issue.
The data you're parroting was put together by incompetent hacks who never
understood a fraction of what I do. Because you're simply reiterating their
tripe, it's not possible to have a meaningful and smart conversation about
the subject. The discussion fails at face value because you don't seem to
understand that most of those settings won't even do anything: they're just
noise.

I love you and I'm one of the people trying to help rescue AVI from the
abject morass it's been led into. As part of that, I need to avoid getting
engaged in conversations that aren't going anywhere. The data you've
provided is wrong and dangerously wrong, end of story. =)

Kind regards and signing off from this conversation,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no rights.
--
Zack said:
Dear Zach:
If the entry for msacm.voxacm160 is wrong, then just state so.
WMPLugins.com offers it as a remedy for all ills of Media Player without
any
reservation about Vista.
http://www.wmplugins.com/ItemDetail.aspx?ItemID=723
I was directed there by Media Player's web help, which is useless to start
with.
Thank you for your passion for Vista.



:


I guarantee you that the information you just presented is bad, corrupt,
and
incompetent. Much of the information you are referring to directly
refers
to items I either worked on or have had some level of development
responsibility or have a high level of knowledge on, usually far beyond
what
anyone not directly involved with the companies in question would have.
It
is extremely doubtful that anyone you can possibly refer to knows more
about
this particular area than I do. That's stated as a matter of fact and
not a
matter of opinion.

I will repeat that any advice that tells someone to add the registry
value
"msacm.voxacm160"="vct3216.acm"
to their Vista system is abjectly and utterly indefensibly incompetent.

That's really it. That can't be defended.

I appreciate that peoples have different levels of knowledge in different
fields. This particular field happens to be an area I am an expert in.
I
thank you for understanding the limits of your own understanding of this
field and not propagating bad advice.

I can not see anyone in good faith continuing this conversation. If this
does continue, I'm going to assume that you're simply trolling. The
Voxware
entry (and other entries you're referring to) were created in part by me
personally way back when, so again: this isn't conjecture nor debatable.
The data you're suggesting is simply and flatly wrong.

Thank you,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
--
Dear zach:
It has been a pleasure reading your responses. The goal is to have
Vista
and Media Player to be user friendly. Media Player's demeanor has to
improve.
Having said that, I found the following drivers32 list is justifiable
and
achievable.
The Credit goes to a utility found at:
http://www.am-softhome.com/avidiag.html

I hope that this thread would help seekers of knowledge about the great
operating systems by Microsoft.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32]
"midimapper"="midimap.dll"
"msacm.imaadpcm"="imaadp32.acm"
"msacm.msadpcm"="msadp32.acm"
"msacm.msg711"="msg711.acm"
"msacm.msgsm610"="msgsm32.acm"
"vidc.cvid"="iccvid.dll"
"vidc.iv31"="ir32_32.dll"
"vidc.iv32"="ir32_32.dll"
"vidc.iv41"="ir41_32.dll"
"VIDC.IYUV"="iyuv_32.dll"
"vidc.mrle"="msrle32.dll"
"vidc.msvc"="msvidc32.dll"
"VIDC.YVYU"="msyuv.dll"
"wavemapper"="msacm32.drv"
"msacm.msaudio1"="msaud32.acm"
"msacm.sl_anet"="sl_anet.acm"
"msacm.iac2"="C:\\WINDOWS\\system32\\iac25_32.ax"
"vidc.iv50"="ir50_32.dll"
"wave"="wdmaud.drv"
"midi"="wdmaud.drv"
"mixer"="wdmaud.drv"
"VIDC.WMV3"="wmv9vcm.dll"
"msacm.voxacm160"="vct3216.acm"
"MSVideo"="mciavi32.dll"
"MSVideo8"="VfWWDM32.dll"
"wave1"="wdmaud.drv"
"midi1"="wdmaud.drv"
"mixer1"="wdmaud.drv"
"aux"="wdmaud.drv"
"VIDC.UYVY"="msyuv.dll"
"VIDC.YUY2"="msyuv.dll"
"VIDC.YVU9"="iyvu9_32.dll"
"wave2"="wdmaud.drv"
"midi2"="wdmaud.drv"
"mixer2"="wdmaud.drv"
"aux1"="wdmaud.drv"
"wave3"="wdmaud.drv"
"midi3"="wdmaud.drv"
"mixer3"="wdmaud.drv"
"aux2"="wdmaud.drv"
"wave4"="wdmaud.drv"
"midi4"="wdmaud.drv"
"mixer4"="wdmaud.drv"
"aux3"="wdmaud.drv"
"wave5"="wdmaud.drv"
"midi5"="wdmaud.drv"
"mixer5"="wdmaud.drv"
"aux4"="wdmaud.drv"
"wave6"="wdmaud.drv"
"midi6"="wdmaud.drv"
"mixer6"="wdmaud.drv"
"aux5"="wdmaud.drv"
"msacm.l3acm"="C:\\WINDOWS\\system32\\l3codeca.acm"
"msacm.siren"="sirenacm.dll"
"wave8"="wdmaud.drv"
"midi7"="wdmaud.drv"
"mixer8"="wdmaud.drv"
"wave9"="wdmaud.drv"
"midi8"="wdmaud.drv"
"mixer9"="wdmaud.drv"
"wave7"="wdmaud.drv"
"mixer7"="wdmaud.drv"
"midi9"="wdmaud.drv"
"vids.mjpg"="mciavi32.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Drivers32\Terminal Server\RDP]
"wave"="rdpsnd.dll"
"mixer"="rdpsnd.dll"
"MaxBandwidth"=dword:000056b9
"wavemapper"="msacm32.drv"
"EnableMP3Codec"=dword:00000001
"midimapper"="midimap.dll"



:


Thank you very much. I very much appreciate that information. =]

Yeah, that's what I thought you were pointing to. The moral of this
story
is to be really careful about making registry edits based upon random
suggestions from people that you don't know and don't show area
expertise.
VFW can easily be polluted and there's really no great way for the
average
user to decorrupt themselves. (Given that it's a deliberately
exensible
system, it'd be hard to establish what was good and what was bad.)

Cheers and thanks,
-Zach
--
Speaking for myself only.
See http://zachd.com/pss/pss.html for some helpful WMP info.
This posting is provided "AS IS" with no warranties, and confers no
rights.
--
Here are two links of the source of Adobe information for "No Sound"
Problem
in Flash Player. Again this part of discussion is regarding SOUND
only
and
does not affect any other discussion topic of this thread!

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y

http://www.adobe.com/cfusion/webfor...d=44&catid=184&threadid=1175007&enterthread=y

:


I'm solely interested right now in the URL on the Adobe site
whereby
they
said that registering the MetaSound codec was a good plan. You
have
not
provided any specific reference as regards how nor where the
"Adobe"
drivers32 information came from.

The MPEG information you're referring to would only be meaningful
 
Back
Top