Changing video decoder cures several NextPVR problems!

[ShiningDragon]

Ah well, the QuickSync support from egur was something, that interested me a lot, because EVERY system in my big rig is based in SandyBridges (with 3 Kentsfield exceptions).

In the current condition, since introducing egurs work, QuickSync support within ffdshow was only placebo and didn't lowered the cpu usage.
Currently it's even RAISING the cpu usage and limiting the filters and options from ffdshow.

Even if i am not interested in amd hardware ... at least at this point you shouldn't decide based on the mentionied QuickSync Support above. As an example:
480p material on HD Graphics 3000
libavdecoder: ~25% cpu usage at 1,6 GHz
QuickSync: ~37% cpu usage at 1,6 GHz

There's even no real difference if you playback 1080p material.

As he mentioned in his thread: he has to do some steps, which just breaks down the performance.

CPU usage is very high for Intel SW implementation because I keep using the D3D surfaces as frame buffers.

But nevermind, even without "QuickSync" i'll stay at ffdshow. It's doing what i want and with avisynth support it is a real strong one.