Can you please point us to the specific clip that you've tried? Or is it happening with any H.264 L4.1 clip? Which demuxer/parser does the player (which player) use when it crashes?
Please let us know these details.
Hi Sankaranarayanan, Thanks for replying.
1. it is happening with every H.264 L4.1 clip we tested.
if you need a sample, here is one:
2. demuxers tested are latest haali media splitter and MPC-HC matroska splitter.
3. players tested are MPC-HC, GraphEdit and GraphStudio.
we even tested video only streams.
it's not related to a specific player / demuxer / H.264 file.
My thanks too Sankaranarayanan V.
I am the originator of the bug as reported as #233 on Sourceforge MPC-HC project and confirmed by another GMA500 XP user. I have run the tests under Tal's guidance on this hardware to trace the point of failure which has been consistent.
I am available to run and report any tests on this hardware thatyou may require.
as you may know, it's possible to get DXVA 2.0 working under Win XP for VC-1 decoding. (.Net Framework 3 installs the necessary components)
at this mode of operation, DXVA 2.0 calls are translated by the microsoft components to DXVA 1.0 driver calls.
since we know our DXVA 2.0 code works well under Win 7, we assumed that if that issue was a result of DXVA 1.0 bug in our code, the translated driver calls (which are not done by us) would result in perfect playback, just like on windows 7.
however, we received error 0x80004005 (unexpected error) when calling IDirectXVideoDecoder::BeginFrame for the decoding of the first frame.
I think it confirms that this is an issue with the current drivers.
I'm glad you're able to reproduce the issue.
the H.264 sample indeed have L5.1 header, but it complies with all L4.1 specs (3 ref frames are used, you can examine the encoding parameters with MediaInfo).
the VC-1 issue is not a seperate issue, it's the same driver issue with windows XP.
decoding of any DXVA compliant content (H264 L4.1 / VC-1) using DXVA 1.0 under XP will cause a BSOD.
we utilized DXVA 2.0 under XP only to demonstrate that it's a driver issue and nothing is wrong with our DXVA 1.0 code.
Yes, I confirm that my issue is the inability to utilize DXVA with the GMA500in playing H.264 videos under XP because it always BSOD's with an error message identifying the video driver at fault.
Thisleaves netbook systems, unable to decode H.264 video without artifacts due to their low cpupower, and essentially useless, since the whole purpose of including the GMA500 with these systemswas to provide DXVA support and enable these low power systems to play these videos.
"I am able to reproduce the H.264 issue. I will analyze and let you know.
Hi Sankar. How is this proceeding? Should we check daily or will this take some time?
There is a lot of interest in this XP support so thank you for your help.
Sankar: The following will confirm that the BSOD playing any H264 video using the GMA500 XP driver is indeed a bug in the driver, and not in the calling code.
Using the IEGD 10.3 driver for the chipset, which is supported on XP, playing the same X264 videos, activates and plays these videos accelerated without any BSOD failure.
You should also be aware that the DXVA performance of the IEGD driver is 8 times! greater than that of the GMA500 XP driver. On the ATOM Z520, my test 1080P 4mbps X264 video plays at 4 frames per second but with the IEGD driver the frame rate jumps 8 times to 24 frames per second at the same CPU loading!
I would expect that Intel would improve the preformance of the GMA500 driver to be at least equivalent to that of the IEGD driver, but at a minimum the BSOD failure would be corrected, since every XP GMA500 user playing HD video with MPC-HC will experience it. Hardly a positive user experience with Intel amongst a rapidly growing netbook segment.
I trust your analysis has/will confirm these facts. Can you confirm that these problems have been reported to the GMA500 driver development team, or advise what different path we need to follow to report them?
Thank you for your help.