Jump to content
Posted 27 December 2007 - 03:00 PM
Posted 27 December 2007 - 03:30 PM
Posted 28 December 2007 - 09:02 AM
Go to the following registry folder:
double click on 'Auto Insert" on the right side of the box.
Change the Value from "1" to "0" and click OK.
You should be set.
I checked my registry. Apparently I did NOT use this. I'm still set on "1".
So, if you have no sound or no audio when using windows media player for streaming, but it works fine for regular files (video and audio), try the above fix. It worked! (you do have to restart WMP for the change to take place.)
If you do not want to change the registry do this. The registry fix is the best solution but the fix below will work for the faint at heart.
Open Windows Media Player, Click on the "Now Playing Tab" and select
"More Options" select the "DVD Tab" click on the "Advanced Box"
under the Out Put Box "click the down arrow" beside (AS is (no change)
select "1/0 mono" click "Apply & OK" and "OK" again. Exit Media Player.
The Cure? A new Codec!
To get around the problem, you need to install a new codec.
The best one I have found is called codec all-in-one - it is free, and it seems to work well, but a google search may turn up other alternatives that work equally as well.
All I know is, this codec pack has finally fixed the chipmunks and super fast video at cnn and msnbc video links in IE using WMP9. I've spent months, off and on, trying to figure this one out, including upgrading to WMP 10 and 11 and trying just about every "manual" adjustments I found on the web.
It also fixed cnn in Firefox. The video window came up but just did nothing. I had managed to get msnbc to work in FF but nothing I tried would get cnn to work. Until now.
I do get a false positive HTML/Feebs.Gen warning with AntiVir in IE ONLY at cnn ONLY when the video starts to load, but since I primarily use FF, I can put up with that inconvenience. AntiVir said they'd fixed that, but the fix isn't working for me.I no longer get the warning, so it must be fixed now.
So far everything else on my system is working normally. Judging from all the negative comments, maybe I've just been lucky. But I don't have a lot of other codec packs, separate media players, etc installed to cause conflicts. That might be the difference.
0 members, 0 guests, 0 anonymous users