Windows 7 x64 WMP 12 has it's own DXVA decoders ?

[St Devious]

Trying to play a 1920x1080 .m2ts file output by Cyberlink Powerdirector. The file playback is horrible in MPC-HC. Only sound with no video sometimes, other times video is hung at one screen with audio playing.

But WMP plays video better and doesn't use any CPU at all. The CPU usage is like 3-4%.

I have set everything to libavcodec in ffdshow, but WMP doesn't seem to be using ffdshow. Any way to disable WMP's default decoders and make it use ffdshow.

[LoRd_MuldeR]

It seems you missed all the discussion about that topic :rolleyes:

In short: Yes, WMP12 has its own decoders. No, WMP12 doesn't allow you to use "third party" decoders (M$ decoders are now forced in whenever possible). Yes, there are "workarounds".

More info:
* http://forum.doom9.org/showthread.php?t=145906
* http://forum.doom9.org/showthread.php?t=146910

[St Devious]

It seems you missed all the discussion about that topic :rolleyes:

In short: Yes, WMP12 has its own decoders. No, WMP12 doesn't allow you to use "third party" decoders (M$ decoders are now forced in whenever possible). Yes, there are "workarounds".

More info:
* http://forum.doom9.org/showthread.php?t=145906
* http://forum.doom9.org/showthread.php?t=146910

Thanks, I'm aware of the second topic. I used that tool.

But I didn't see any option under 64-bits for decoders other than MS's in that soft.

I'm guessing since I have 64-bit Win 7 RC, the WMP is using 64-bit decoders. And I have 32-bit ffdshow installed. So I cannot override MS's decoders with 32-bit ffdshow decoder ?

Would ffshow 64-bit allow me to override MS's decoders ?

[LoRd_MuldeR]

If WMP12 is a 64-Bit process (you can check that easily via ProcessExplorer), then you will need 64-Bit decoders indeed. 64-Bit processes can't load 32-Bit DLL's.

http://www.xvidvideo.ru/content/view/828/5/


But then it should work with CLSID's tool:

Currently supported third party filters (64-bit):
* ffdshow
* MPCVideoDec
* Xvid MPEG-4 decoder
* Gabest MPEG-2 decoder

[St Devious]

If WMP12 is a 64-Bit process (you can check that easily via ProcessExplorer), then you will need 64-Bit decoders indeed. 64-Bit processes can't load 32-Bit DLL's.

http://www.xvidvideo.ru/content/view/828/5/

there are some 64-bit builds available here too

http://ffdshow-tryout.sourceforge.net/download.php

What's is the difference between all these different builds ?

Also I just checked in the taskmanager. WMP is a 32-bit process.

It says wmplayer.exe*32. Now what to do ?

[LoRd_MuldeR]

What's is the difference between all these different builds ?

Different revisions of ffdshow, different architectures (x86 vs. x64), made by different people using different compilers.

It says wmplayer.exe*32. Now what to do ?

Then it would need a 32-Bit build of ffdshow.

[St Devious]

Different revisions of ffdshow, different architectures (x86 vs. x64), made by different people using different compilers.


any advantage of one over another ?

Then it would need a 32-Bit build of ffdshow.

I already have a 32-bit build. And set ffdshow as the default decoder with clsid's software.

[LoRd_MuldeR]

any advantage of one over another ?

I'd usually go with the latest build I can get. And only fall back to an older build, if problems occur.

Also ICL (Intel C Compiler) builds should be a bit faster than MSVC (M$ C Compiler) builds, at least when certain filters are used.

I already have a 32-bit build. And set ffdshow as the default decoder with clsid's software.

Not sure. Maybe CLSID can comment on this.

[Snowknight26]

I already have a 32-bit build. And set ffdshow as the default decoder with clsid's software.

WMP will use the Microsoft decoders whenever possible. If content can't be decoded with those, it will fall back to the next available decoder (say ffdshow).

[clsid]

No, it uses whatever is set as preferred in the Registry. By default that are the MS decoders. The tool allows changing that.

However, the tool only works for the preferred DirectShow filters. When WMP uses Media Foundation those settings don't have any effect.

[Snowknight26]

Let me rephrase that. When there are MF decoders available, it will use those regardless of DirectShow settings. Then it falls back to DirectShow.

[LoRd_MuldeR]

Let me rephrase that. When there are MF decoders available, it will use those regardless of DirectShow settings. Then it falls back to DirectShow.

But even if there's no suitable MediaFoundation filter and WMP12 falls back to DirectShow, it will still prefer Microsoft's own filters over all third-party filters.

CLSID's tool can be used to change those "preferred" DirectShow filters, but it can't prevent WMP12 from using MF instead of DShow...

[clsid]

MF can be disabled by renaming certain files, but that is not a good solution as it might break stuff. It might be possible to tweak MF through the Registry. I haven't had time to investigate that. If I or anyone else finds such a tweak, it will get added to a future version of the tool.

[St Devious]

I managed to play a mp4 file with H.264/AAC in WMP using ffdshow with clsid's tool. But this .m2ts file doesn't play with ffdshow.

[CruNcher]

Most probably Microsofts .m2ts splitter isn't interoperable with ffdshow try haalis, also see in the Bigest Codec Problems 2009 thread there you gonna find some Splitter/Demultiplexer from Intel (Media Foundation)