Hi Jack & Robert,

Good News! I've found both the solution and cause of our problem, but not
the "why did it happen":

It seems as though regardless of what you are doing with it, a
MediaPlayer/MediaElement object is going to go out and make a call to the
function:
DXVA2CreateDirect3DDeviceManager9
contained in the DLL: DXVA2.dll (DirectX Video Acceleration 2?)

OK, but Jack and I kept getting Procedure Not Found exceptions at exactly
that point in the execution and with good reason: using depends.exe i was
able to investigate the DLL and that function was simply not present.

I had a friend send me over his working copy of the dll
(C:\Windows\System32\DXVA2.dll), i switched the two and now the
MediaPlayer/MediaElement are able to initialize without problem! (His copy
does have the function, amongst others)

So Jack, if you swap the working version (desktop) to you laptop, you should
be good to go! Hopefully without anything goign haywire...



I know this is a long post, but an additional intresting factor in this is
that while both files have a file version stamp of 5.0.1.1 - the non working
version has a Link Time Stamp of 3/26/2005 whereas the working version (which
is also about 10kb larger) has a Link Time Stamp of 10/20/2005. But how did
Jack and I end up with this old version? DirectX is up to date, as are
Graphics Card drivers...mystery...

Phew! All this to avoid studying for a Calc 2 Final!

Regards,
Avery Z

Thats wonderful that you found the solution to the problem (It's been
bothering me too). My problem is, I'm away for the holidays, and dont have
access to a computer with a valid dxva2.dll. Can somone email theirs to me?
(blackgold9@gmail.com) I'd really appreciate it.

"Avery Z" wrote:

> Hi Jack & Robert,
>
> Good News! I've found both the solution and cause of our problem, but not
> the "why did it happen":
>
> It seems as though regardless of what you are doing with it, a
> MediaPlayer/MediaElement object is going to go out and make a call to the
> function:
> DXVA2CreateDirect3DDeviceManager9
> contained in the DLL: DXVA2.dll (DirectX Video Acceleration 2?)
>
> OK, but Jack and I kept getting Procedure Not Found exceptions at exactly
> that point in the execution and with good reason: using depends.exe i was
> able to investigate the DLL and that function was simply not present.
>
> I had a friend send me over his working copy of the dll
> (C:\Windows\System32\DXVA2.dll), i switched the two and now the
> MediaPlayer/MediaElement are able to initialize without problem! (His copy
> does have the function, amongst others)
>
> So Jack, if you swap the working version (desktop) to you laptop, you should
> be good to go! Hopefully without anything goign haywire...
>
> I know this is a long post, but an additional intresting factor in this is
> that while both files have a file version stamp of 5.0.1.1 - the non working
> version has a Link Time Stamp of 3/26/2005 whereas the working version (which
> is also about 10kb larger) has a Link Time Stamp of 10/20/2005. But how did
> Jack and I end up with this old version? DirectX is up to date, as are
> Graphics Card drivers...mystery...
>
> Phew! All this to avoid studying for a Calc 2 Final!
>
> Regards,
> Avery Z
>
>

New Avalon build, new set of complaints that media doesn't work. When
are they going to get this right? This is ridiculous. I hope no one is
planning on using media in released apps, just imagine the support
calls.

I'm getting the same now...Maybe our hardware simply doesn't support it.
(Like the avalon team has said all along...)

Avery

"Midas" wrote:

> This ALMOST worked for me. I deleted my dxva2.dll, repaired my winfx
> installation and now media elements dont CRASH. However, they also don't
> display Anything at all. I did a debug and uppon catching the mediafailed
> event, it reports,
> "An unknown media error has occurred"
>
> Any Ideas?
>
> "Avery Z" wrote:
>
> > Hi Jack & Robert,
> >
> > Good News! I've found both the solution and cause of our problem, but not
> > the "why did it happen":
> >
> > It seems as though regardless of what you are doing with it, a
> > MediaPlayer/MediaElement object is going to go out and make a call to the
> > function:
> > DXVA2CreateDirect3DDeviceManager9
> > contained in the DLL: DXVA2.dll (DirectX Video Acceleration 2?)
> >
> > OK, but Jack and I kept getting Procedure Not Found exceptions at exactly
> > that point in the execution and with good reason: using depends.exe i was
> > able to investigate the DLL and that function was simply not present.
> >
> > I had a friend send me over his working copy of the dll
> > (C:\Windows\System32\DXVA2.dll), i switched the two and now the
> > MediaPlayer/MediaElement are able to initialize without problem! (His copy
> > does have the function, amongst others)
> >
> > So Jack, if you swap the working version (desktop) to you laptop, you should
> > be good to go! Hopefully without anything goign haywire...
> >
> > I know this is a long post, but an additional intresting factor in this is
> > that while both files have a file version stamp of 5.0.1.1 - the non working
> > version has a Link Time Stamp of 3/26/2005 whereas the working version (which
> > is also about 10kb larger) has a Link Time Stamp of 10/20/2005. But how did
> > Jack and I end up with this old version? DirectX is up to date, as are
> > Graphics Card drivers...mystery...
> >
> > Phew! All this to avoid studying for a Calc 2 Final!
> >
> > Regards,
> > Avery Z
> >
> >

Here's how i fixed that. Along with the dxva2.dll with the wrong date was a
file evr.dll with the SAME date. So.... I erased both of them and reinstalled
the WPF Runtime. Problem Solved. The correct versions were installed and
everything is great.

Midas,

You are a brilliant genius. I erased both and installed the Dec. CTP (I
figured if I was re-installing I might as well upgrade as well) - Both files
have a date of Nov. 3 now and work beautifully.

You are the man.

-Avery

"Midas" wrote:

> Here's how i fixed that. Along with the dxva2.dll with the wrong date was a
> file evr.dll with the SAME date. So.... I erased both of them and reinstalled
> the WPF Runtime. Problem Solved. The correct versions were installed and
> everything is great.