Originally Posted by Hisma
read the kb
we're not just talking about strobing (which for me wasn't a dynamic contrast issue, it was only strobing with certain bright colors), it causes judder as well. It's not "hiding the symptoms" if the problems aren't prevalent in other pvr programs. That's just a poor excuse to make when the show you may want to watch isn't "properly encoded".
Microsoft's solution is to try new video drivers, or a new video card altogether.
I've read the KB article. It doesn't say anything I haven't already told you.
It is an encoding problem. That isn't an excuse. It's reality. Regardless of what the symptoms might be, Microsoft is simply following the standards set forth by other organizations. Give WMC a proper video stream, and you get proper output. Give it an improperly encoded video stream and... What do you really expect to happen? What do you expect it to fix? If the video stream was encoded with the wrong AR, would you expect it to display properly anyway? Would MPC-HC or XBMC display it in the proper AR? Of course not. Would you say that either has a bug because it doesn't display that video properly? Of course not. Because it isn't a problem with the software it's a problem with the video stream.
Furthermore, just because MPC-HC and XBMC ignore the frame encoding flag in the video stream, and it displays some content in a better manner than what WMC does, that doesn't mean that it displays everything right. It's either forcing everything to be displayed as progressive, which means that interlaced content isn't displayed properly, or it is using some other means for detecting if content is interlaced, so it's anybody's guess if/when it will display interlaced content properly.
The reason that MS suggests getting a new video card or updating drivers, is because that is the only thing a user can do to remedy the problem. Unless you're working in the control room at CBS or whatever network is displaying the 29/59 issue, there is nothing else you can do about it.
If I have a letter delivered via US Mail vs Fed-Ex they will go about delivering that letter two different ways. Say I want to send a letter to my friend. But I know my friend is housesitting for a neighbor and he will be at the neighbor's house all week. If I send that letter via US mail, and address it to my friend, and put his neighbor's adress on it, Fed Ex will deliver it to the neighbor's house and my friend will get the letter. If I send it via US Mail they assume they know better than I do and ignore the address I put on the envelope and they deliver it to my friend's house instead of where I addressed it, and my friend won't get the letter in a timely fashion.
Fed Ex is WMC. They're just doing what they're told. Delivering the envelope where they were told. US Mail is MPC-HC. They're ignoring the explicit information I included on the envelope and instead they're trying to interpret where they think, I wanted it to go.
So now let's look at the flip side of the coin... Let's say I
put the wrong address on the envelope. Let's say my friend was home, but I accidentally addressed it to his neighbor's house number. US Mail will recognize that the name and address don't match and deliver it to the right location anyway. Fed Ex will try and deliver it to the neighbors, because that's what the envelope says. If the neighbor isn't home to say "oh, that should go next door" Fed Ex will eventually stop trying to deliver it.
So now you're thinking A-hah! See... the US Mail (MPC-HC) has triumphed and that proves the point that MPC-HC is best! Well, that's all well and good, but is it Fed Ex's fault that the envelope didn't get delivered in the 2nd scenario? No. Of course not. I'm the one that put the wrong address on the envelope. That's my
fault, not theirs. Blaming them would be ludicrous. Regardless of the blame, using the 2nd example as a reason to do it the way the US Mail (MPC-HC) completely ignores the first example. In the first example, you don't ever really know if anyone is ever going to get their mail, because the US Mail is basically ignoring the address and just going by the name.
Point being it is not a WMC problem. It is a content problem combined with a hardware/driver issue. The only
way you will see issues is if the content is encoded improperly and
your hardware can't cope with it. Complaining about MS not fixing it shows a complete lack of understanding of the problem as there is nothing for MS to fix. They're already following the standard.
Originally Posted by Charles Babbage
On two occasions I have been asked, 'Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question.
I am not able to rightly apprehend the kind of confusion of ideas that would lead a person to think that feeding a video player a broken video stream should result in proper video playback.