Intel QuickSync Decoder - HW accelerated FFDShow decoder with video processing

[egur]

The password thing is new. OEMs and ISVs usually download drivers and other SW/firmware from the SW support site.

[CruNcher]

Made a current compare with 2669 on the WMV3 state with the 50 fps Keynote Video, any yup it fixed all Quicksync API Decoding issues

Cyberlink DXVA = 1.30%
Media SDK = 2.50%
Lav Video Quicksync = 6.50%
Lav Video (avcodec) = 7.00%
ffdshow Quicksync = 7.50%
WMV Decoder = 7.50%

this includes all overheads (Lav Splitter(except for Media SDK doesn't support Lav Splitter using WMV ASF Reader here),Renderer(EVR basic),Audio(WMAudio),MPC-HC GUI Rendering + Copy Back for Lav Quicksync and ffdshow Quicksync)

This is only CPU utilization was not interested for this part in Memory and GPU

[egur]

What's the average CPU frequency for these tests?

[Omel]

Hi t

new drivers as 2669 and 2696 where can i find them. I have tried at downloadcenter.intel.com but can't find them
??

regards

Omel

[Superb]

Originally Posted by Omel

Hi t

new drivers as 2669 and 2696 where can i find them. I have tried at downloadcenter.intel.com but can't find them
??

regards

Omel

Geez man... read the freakin' comments.

[Omel]

Originally Posted by Superb

Geez man... read the freakin' comments.

Whaoooo.. what a friendly answer thx man

[egur]

Originally Posted by Omel

Hi t

new drivers as 2669 and 2696 where can i find them. I have tried at downloadcenter.intel.com but can't find them
??

regards

Omel

They are not available to the general public yet.
IvyBridge will be out very soon and along with it the new generation of drivers will be publicly available.
Current driver generation (Win7): 15.22.xx.xx
Next driver generation (Win7): 15.26.xx.xx

2622 belongs to the 15.22 family.
2639, 2656, 2669, 2696, 27xx all belong to the 15.26 family.

Since drivers are shared between desktop and mobile systems, they need especially long validation and are not released to the public regularly.
The released/leaked 15.26 drivers were aimed at OEMs and ISVs for validation purposes. End users should that use these versions do this at their own risk.
My personal HTPC uses 2622. It's very stable and has very good performance. I use the newer drivers for testing my code and logging the driver progress (also report issues if I find any).

[egur]

@CruNcher
Can you share (or reshare ) the clip you tested on (wmv3)?

[CruNcher]

Here are pretty accurate measurements 1 minute sure here you can find it http://video.ch9.ms/build/2011/key01...y1_2MB_ch9.wmv

High performance Profile

Idle State:



Cyberlink VLD DXVA:




Intel MSDK:



ffdshow-quicksync:



Lav Video Quicksync:



Lav Video avcodec:



WMVideo Decoder:



PS: Memory Utilization is not as accurate as everything else, it takes some time to get back to the old memory state so don't compare memory utilization here as i didn't had the time to wait every x minutes to compare exactly with the old state
Also this is awkward it worked out well though it was meant for overclockers and it's not really good from a screen estate state also it's consuming some overhead itself and probably is responsible for a lot of the frequency changes in idle state and some peaks @ measuring as well :P but hey it has a graph yeah
Getting High resolution noiseless near realtime measuring results (not pre recorded) directly on the system is always a adventure
Perfmon maybe could have done the job as well but i would have had to import the performance counter first for the TDPs Graphic Frequency and then i wonder if Rivatuner wouldn't be actually more efficient as a host for them

[nevcairiel]

Something is wrong with your setup, Idle should be much lower CPU frequency.
Even my Overclocked i7 goes down to 1600 Mhz on idle.

Power-Usage numbers are meaningless if you don't allow the CPU to clock down.

[CruNcher]

Im using High Performance Profile not balanced for testing i like to see it the other way and keep the system from fluctuating to much when running measurements and use balanced when testing responsiveness (latency) (Frequency adaption impacts)
Though SB and NT 6 are very efficient in those regards but i keep with this way of testing

The Frequency goes down look @ the Cyberlink DXVA and MSDK no copy back result and the difference from 5W to 8W = +3W and 1W to 4W = +3W why should they be meaningless ?

DXVA = +3W
MSDK = +4W + 1W
Avcodec = +6W
WMvideo Decoder = +6W + 1W
ffdshow-quicksync = +7W + 1W
Lav Video Quicksync +7W + 1W

what should be wrong here (also keep in mind this is complete overhead of the playback including Client,Splitter,Decoder(Video,Audio) and Renderer) ?

[CruNcher]

VLC almost got it right (guess most of the VLC Linux guys hate DXVA by now )

http://forum.doom9.org/showpost.php?...ostcount=19182

[Omel]

Originally Posted by egur

They are not available to the general public yet.
IvyBridge will be out very soon and along with it the new generation of drivers will be publicly available.
Current driver generation (Win7): 15.22.xx.xx
Next driver generation (Win7): 15.26.xx.xx

2622 belongs to the 15.22 family.
2639, 2656, 2669, 2696, 27xx all belong to the 15.26 family.

Since drivers are shared between desktop and mobile systems, they need especially long validation and are not released to the public regularly.
The released/leaked 15.26 drivers were aimed at OEMs and ISVs for validation purposes. End users should that use these versions do this at their own risk.
My personal HTPC uses 2622. It's very stable and has very good performance. I use the newer drivers for testing my code and logging the driver progress (also report issues if I find any).

Thanks Egur that was the information i was looking for.

that explain a lot for me

best regards

Omel

[Omel]

@Egur

Hi

I am a little confused, under downloadcenter.intel.com I find one driver under Graphics/processor and another under my Mainboard DH67GD which one wil be the correct to use?

my processor is a I3 -2100T?

Best regards

Omel

[egur]

Originally Posted by Omel

@Egur

Hi

I am a little confused, under downloadcenter.intel.com I find one driver under Graphics/processor and another under my Mainboard DH67GD which one wil be the correct to use?

my processor is a I3 -2100T?

Best regards

Omel

For desktops use the newest you can find.

[egur]

Originally Posted by CruNcher

Im using High Performance Profile not balanced for testing i like to see it the other way and keep the system from fluctuating to much when running measurements and use balanced when testing responsiveness (latency) (Frequency adaption impacts)
Though SB and NT 6 are very efficient in those regards but i keep with this way of testing

The Frequency goes down look @ the Cyberlink DXVA and MSDK no copy back result and the difference from 5W to 8W = +3W and 1W to 4W = +3W why should they be meaningless ?

DXVA = +3W
MSDK = +4W + 1W
Avcodec = +6W
WMvideo Decoder = +6W + 1W
ffdshow-quicksync = +7W + 1W
Lav Video Quicksync +7W + 1W

what should be wrong here (also keep in mind this is complete overhead of the playback including Client,Splitter,Decoder(Video,Audio) and Renderer) ?

I'm getting 3-5% CPU usage (i7-2600) for the player's executable (ZoomPlayer) when playing this clip using ffdshow+qs+EVR. The CPU frequency is 1600MHz (LFM).

Summary (wmv9, 60fps, 6mbps, progressive, NV12 output, no post procesing):
ffdshow+QS: 3-5% @1600MHz
ffdshow+wmv9: 6-7% @3600MHz
ffdshow+libavcodec: 4% @2000MHz - fluctuates a lot

[Omel]

Originally Posted by egur

For desktops use the newest you can find.

I use it as a mediaplayer (mediaportal) with TV and Movies and use LAV filters the latest ?

Will the latest intel driver be the optimal driver ? or should I use the 2622 driver as you said previously ?

kind regards

Omel

[egur]

Originally Posted by Omel

I use it as a mediaplayer (mediaportal) with TV and Movies and use LAV filters the latest ?

Will the latest intel driver be the optimal driver ? or should I use the 2622 driver as you said previously ?

kind regards

Omel

Always use latest LAV and/or ffdshow.
With drivers, the performance differences are small and should not concern you. Just use the latest.

[CruNcher]

@Egur

http://forum.doom9.org/showpost.php?...ostcount=10281

Am i right and Microsofts DTV Decoder acts as a Quicksync API Wrapper ?

This would make major sense as you would have full control on a higher level off every Application output that makes use of it, i guess virtually all GPU Vendors will handle it this way and take control over it with their Native ways

[egur]

Originally Posted by CruNcher

@Egur

http://forum.doom9.org/showpost.php?...ostcount=10281

Am i right and Microsofts DTV Decoder acts as a Quicksync API Wrapper ?

This would make major sense as you would have full control on a higher level off every Application output that makes use of it, i guess virtually all GPU Vendors will handle it this way and take control over it with their Native ways

Microsoft DTV Decoder most likely uses DXVA2.
It might use low level DDI calls but that would make very little sense.
The DTV decoder probably initializes the DXVA device differently somehow. It may also parse SPS/PPS headers for errors and try to recover them.

Part of the QuickSync feature set is exposed via the DXVA2 API (decode, vpp), the rest (encode) is done via DDI calls as DXVA2 doesn't support encode.

There's no official QuickSync API. The APIs used under Windows are Media SDK, DXVA2, DDI.