Intel QuickSync Decoder - HW accelerated FFDShow decoder with video processing

[egur]

I read the white paper on Optimus (Nvidia's switchable graphics solution). It's not 100% clear whether they disable the iGPU calls when the dGPU is active. The notion of the white paper is that it does. So it may NOT expose the existence of the iGPU to your application.
The proper behavior would be (for your app):
- Adapter #1 (main) NV620m
- Adapter #2 (secondary) HD 4000

If it exposes only the first adapter in D3D11, then there's nothing to do.

I don't have an Optimus system available for testing.

To check this, I'll prepare a version that will open a message box with this information. Wait a day or two, I'm in the middle of something else.

[jkauff]

Eric, are you part of the Intel team working with the Handbrake folks on the new open source Media SDK? Handbrake forum reports Intel has been quite helpful in the effort so far.

[egur]

No, I'm doing this on my own time nowadays, as a hobby of sorts. I belong to a completely different division.
My position is enabling and supporting OEMs on CPU related issues/questions.

[egur]

Version 0.42 is out with the following changes:
* Direct3D11 playback (decode + video processing) on Windows 8. Windows 8 allows D3D11 to play video without a display connected to the accelerating GPU.
* Fixed a minor bug in the deinterlacer.
* Fixed an issue with H264 handling of fragmented streams (TV streams with some splitters)
* Updated MSDK headers and dispatch library to Intel Media SDK 2013.
* FFDShow: r4508

Downloads
* For the latest cutting edge FFDShow builds download my builds Intel QuickSync Decoder SourceForge home page (http://sourceforge.net/projects/qsdecoder/)
* FFDShow-tryout site (http://ffdshow-tryout.sourceforge.net/download.php)
* LAV Splitter builds (http://forum.doom9.org/showthread.php?t=156191)

[Superb]

Great work Eric! :D

[betaking]

last ffdshow svn can not compile
vista sp2 msvc 2010sp1
生成启动时间为 13/05/20 PM 07:30:11。
1>项目“C:\ffdshow\src\codecs\IntelQuickSyncDecoder\IntelQuickSyncDecoder.vcxproj”在节点 2 上(build 个目标)。
1>InitializeBuildStatus:
正在创建“C:\ffdshow\obj\Release_Win32_VC2010\IntelQuickSyncDecoder\IntelQuickSyncDecoder.unsuccessfulbuild”，因为已指定“AlwaysCreate”。
ClCompile:
C:\Program Files\Microsoft Visual Studio 10.0\VC\bin\CL.exe /c /I\Include /I\Include\um /I\Include\shared /Isrc\MSDK\include /Zi /nologo /W4 /WX /MP /Ox /Oi /Ot /Oy /D WIN32 /D NDEBUG /D _WINDOWS /D _USRDLL /D QUICKSYNC_EXPORTS /D _CRT_SECURE_NO_WARNINGS /D _WINDLL /D _UNICODE /D UNICODE /Gm- /EHsc /MT /GS- /Gy /fprecise /Zc:wchar_t /Zc:forScope /Yc"StdAfx.h" /Fp"C:\ffdshow\obj\Release_Win32_VC2010\IntelQuickSyncDecoder\IntelQuickSyncDecoder.pch" /Fo"C:\ffdshow\obj\Release_Win32_VC2010\IntelQuickSyncDecoder\\" /Fd"C:\ffdshow\obj\Release_Win32_VC2010\IntelQuickSyncDecoder\vc100.pdb" /Gd /TP /wd4996 /wd4995 /analyze- /errorReportrompt src\stdafx.cpp
stdafx.cpp
1>c:\ffdshow\src\codecs\intelquicksyncdecoder\src\stdafx.h(23): fatal error C1083: 无法打开包括文件:“dxgi1_2.h”: No such file or directory
1>已完成生成项目“C:\ffdshow\src\codecs\IntelQuickSyncDecoder\IntelQuickSyncDecoder.vcxproj”(build 个目标)的操作 - 失败。

生成失败。

已用时间 00:00:03.97

[egur]

hopefully fixed :sly:

[betaking]

hopefully fixed :sly:

YES it fix! Thanks!:)

[itsonlyjustincase]

I read the white paper on Optimus (Nvidia's switchable graphics solution). It's not 100% clear whether they disable the iGPU calls when the dGPU is active. The notion of the white paper is that it does. So it may NOT expose the existence of the iGPU to your application.
The proper behavior would be (for your app):
- Adapter #1 (main) NV620m
- Adapter #2 (secondary) HD 4000

If it exposes only the first adapter in D3D11, then there's nothing to do.

I don't have an Optimus system available for testing.

To check this, I'll prepare a version that will open a message box with this information. Wait a day or two, I'm in the middle of something else.


That is exactly what i tested but it doesn't work. For information i use a soft called Mirillis Action! to record my mix. It can use the igpu to record the video window on the secondary display although the soft is using the dGPU (and Cuvid with Lav)

I gonna test the new version to see what happens

[itsonlyjustincase]

I have just tested. My soft doesn't work if i don't force the nvidia to be used. But then i guess i won't use igpu as the dgpu has been forced. The QS works fine with others

Thanks for your work tough :)

[egur]

I've confirmed that several dGPU drivers in switchable graphics will block the secondary (Intel/iGPU) device.
This means no hybrid/headless support is possible.
Maybe new versions of the Nvidia/AMD drivers will provide this option.
Desktops don't have these issues.

[hoborg]

BTW, i tryed to run Intel HD 2000 + AMD 7750 (primary) together on my desktop few weeks ago on Win7 x64 and they fight each other. This mean internet browser was crashing (flash module), Direct show was crashing (while adding video renderer to graph), games was crashing while D3D init, etc... All was randomized. It is possible to make it working ?

[nevcairiel]

I have been running NVIDIA + Intel for a long time, and its working just fine.
AMD is kinda known to be unfriendly to other GPUs in the system, although i thought that was changed in more recent drivers. I've briefly used a 7750 and a Intel HD 3000 in my HTPC together, and didn't notice any issues, but it was only for a few days for some testing.

[egur]

My main home PC has HD 2000 + Radeon HD 6950. I'm not aware of any issues. When I did have issues, the motherboard was causing them.

[hoborg]

My main home PC has HD 2000 + Radeon HD 6950. I'm not aware of any issues. When I did have issues, the motherboard was causing them.

Can i ask what motherboard do you have?
I have is Gigabyte GA-B75M-D3H 1.1.

[wanezhiling]

Its your win7s problem, install a clean win7 again.

[hoborg]

Its your win7s problem, install a clean win7 again.

Well, i still hoping in GBA motherboard with Haswell GT3e to replace my current setup. :)

[egur]

You should try updating your BIOS, might solve the problem.
I have an Asus Z77 chipset, don't remember the model. Gigabyte are considered very good too but sometimes these boards (all manufacturers) have BIOS bugs that get resolved in updates.

[itsonlyjustincase]

I've confirmed that several dGPU drivers in switchable graphics will block the secondary (Intel/iGPU) device.
This means no hybrid/headless support is possible.
Maybe new versions of the Nvidia/AMD drivers will provide this option.
Desktops don't have these issues.

I'm french so perhaps i expressed in a wrong way. What i wanted to say is that using the dGPU doesn't disable the iGPU here. In fact when i plug my HDMI TV, i can use my dGPU to mix my videos and use the iGPU through Mirillis Action to record in mp4 the video window (without a single fps drops). It does work well and we can see both GPU working thanks to GPU-Z.

My trouble is just coming from the software that doesn't support intel GPU......i thought i could kind of fool it thanks to DX11 QS and Lav Video but it doesn't work. So i'll stick to CUVID

[itsonlyjustincase]

Nev has just confirmed to me that the last lav update doesn't contains the QS 0.42. Perhaps i still have a chance. I'll try it tonight

[egur]

you can the ffdshow build I've prepared. You can copy the QS DLL from it (backup the old one first). Their interfaces are compatible.

[itsonlyjustincase]

you can the ffdshow build I've prepared. You can copy the QS DLL from it (backup the old one first). Their interfaces are compatible.

Thanks i'll do that and get back to you

[itsonlyjustincase]

tried but doesn't work. At the moment the software is forced to use dGPU, when using quickync it says not available (through LAV) and uses avcodec instead (libav in ffdshow)

[itsonlyjustincase]

i find it weird as it shouldn't tell me the quick sync is not available cause the goal is to have it even if the dGPU is the GPU in use.

This workaround works well with Mirillis Action and permit to record with iGPU even if the dGPU is used :

http://mirillis.com/en/products/tutorials/action-tutorial-intel-quick-sync-setup_for_desktops.html#top

I tried it here but it didn't change anything

[egur]

On my system (SandyBridge desktop), if only the dGPU is connected and LAV used the new (0.42) IntelQuicksyncDecoder.dll it will report either Available or Active. LAV video decoder queries my DLL for ability to work.
If you replaced the right DLL and still doesn't get it to work, it means that the Nvidia's Optimus may block the iGPU enumaration, thus disabling QuickSync.

Update
Here's the media SDK system analyzer (http://www.mediafire.com/?yi5mpdd4djeg3u1).
Unzip the file and create an Optimus profile for it, the same profile for your app (dGPU profile).
Execute it (command line) and see if it supports any HW:
Version Target Supported Dec Enc
1.0 HW Yes X X
1.0 SW No
1.1 HW Yes X X
1.1 SW No
1.3 HW Yes X X
1.3 SW No
1.4 HW Yes X X

[itsonlyjustincase]

On my system (SandyBridge desktop), if only the dGPU is connected and LAV used the new (0.42) IntelQuicksyncDecoder.dll it will report either Available or Active. LAV video decoder queries my DLL for ability to work.
If you replaced the right DLL and still doesn't get it to work, it means that the Nvidia's Optimus may block the iGPU enumaration, thus disabling QuickSync.

Update
Here's the media SDK system analyzer (http://www.mediafire.com/?yi5mpdd4djeg3u1).
Unzip the file and create an Optimus profile for it, the same profile for your app.
Execute it (command line) and see if it supports any HW:

Thanks again for your help. Will try this out tonight

[itsonlyjustincase]

But i have thought again about it and yes in fact i think the way optimus works, when you set a profile for an app to force a GPU, this app won't get access to another GPU. That is why Action! works with iGPU while my app is using dGPU. It is just because it's not the same profile. So unless nvidia would change the way optimus works (i won't even take time to write to them for that cause i think i will never have any answer) i won't be able to use the quick sync while the app has a profile which forces it to use dGPU.

Thank you very much for your work any way

[itsonlyjustincase]

Here is the result :

C:\Users\Admin1\Desktop\MediaSDK_sys_analyzer>sys_analyzer.exe
Intel Media SDK System Analyzer (32 bit)


The following versions of Media SDK API are supported by platform/driver:

Version Target Supported Dec Enc
1.0 HW Yes X
1.0 SW No
1.1 HW Yes X
1.1 SW No
1.3 HW Yes X
1.3 SW No
1.4 HW Yes X
1.4 SW No
1.5 HW Yes X
1.5 SW No
1.6 HW Yes X
1.6 SW No

Graphics Devices:
Name Version State
NVIDIA GeForce GT 620M 9.18.13.2000 08

System info:
CPU: Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz
OS: Microsoft Windows 8 Professionnel
Arch: 64 bits

Installed Media SDK packages (be patient...processing takes some time):

Installed Media SDK DirectShow filters:

Installed Intel Media Foundation Transforms:
Intel« Hardware M-JPEG Decoder MFT : {00C69F81-0524-48C0-A353-4DD9D54F9A6E}
Intel« Quick Sync Video H.264 Encoder MFT : {4BE8D3C0-0515-4A37-AD55-E4BAE19AF
471}




Tips:
- SW target does not work: make sure Media SDK DLL (e.g. libmfxsw64.dll)
is located in your executable path or in system path

Analysis complete... [press ENTER]


C:\Users\Admin1\Desktop\MediaSDK_sys_analyzer>

[itsonlyjustincase]

I dit the test by forcing the dGPU then forcing the iGPU then forcing autoselect which is by default the iGPU. Result is the same in each case

[itsonlyjustincase]

Something weird. Instead of launching through command line I tried doing a right click then use iGPU :

Graphics Devices:
Name Version State
NVIDIA GeForce GT 620M 9.18.13.2000 08
Intel(R) HD Graphics 4000 9.18.10.3071 Active


It is weird i don't get the same result when i force the use of iGPU through the nvidia panel

[egur]

D3D11 initial performance results:
I've found that the performance under d3d11 is significantly worse, about 2-3.5x slower than d3d9. The lower the bitrate the higher the performance drop due to extra copying done by the driver in D3D11. The D3D11 API has a built in copy-back mechanism which is slower than mine.
I couldn't find a way to get direct access to the VRAM as in D3D9.

I've already fixed some of the problem so expect a new version soon.

[itsonlyjustincase]

D3D11 initial performance results:
I've found that the performance under d3d11 is significantly worse, about 2-3.5x slower than d3d9. The lower the bitrate the higher the performance drop due to extra copying done by the driver in D3D11. The D3D11 API has a built in copy-back mechanism which is slower than mine.
I couldn't find a way to get direct access to the VRAM as in D3D9.

I've already fixed some of the problem so expect a new version soon.

Egur could you make me a feedback regarding my results ? I don't really know how to interpret it or not sure i interpreted it well.

Regarding the poorer performance with DX11 it doesn't shock me. When i was trying to fix some old problems of GPU frequency drops i could see tons of post where people were saying that they had better performance with their game in DX9 than DX11 when they had the possibility to go back to DX9 (cause some time they just couldn't). I don't understand why Microsoft do shit like that........

[egur]

The results say that your system is fine. SW implementation comes with the media SDK installation which you don't need.
I'm not sure whether the results are accurate, I'll try to write a simple program that does the check myself to be 100% sure. I'll get back to you in a day or 2.

[itsonlyjustincase]

The results say that your system is fine. SW implementation comes with the media SDK installation which you don't need.
I'm not sure whether the results are accurate, I'll try to write a simple program that does the check myself to be 100% sure. I'll get back to you in a day or 2.

Thank you

[egur]

Version 0.43 is out with the following changes:
* Direct3D11 playback (decode + video processing) on Windows 8. Due to performance degradation in D3D11, it will be used only when needed.
* Optimized D3D11 decode - 50% faster than before.
* FFDShow: r4512

Downloads
* For the latest cutting edge FFDShow builds download my builds Intel QuickSync Decoder SourceForge home page (http://sourceforge.net/projects/qsdecoder/)
* FFDShow-tryout site (http://ffdshow-tryout.sourceforge.net/download.php)
* LAV Splitter builds (http://forum.doom9.org/showthread.php?t=156191)

[betaking]

last ffdshow svn can not compile
vista sp2 msvc 2010sp1
生成启动时间为 13/05/25 PM 09:29:17。
1>项目“C:\ffdshow\src\codecs\IntelQuickSyncDecoder\IntelQuickSyncDecoder.vcxproj”在节点 2 上(build 个目标)。
1>InitializeBuildStatus:
正在创建“C:\ffdshow\obj\Release_Win32_VC2010\IntelQuickSyncDecoder\IntelQuickSyncDecoder.unsuccessfulbuild”，因为已指定“AlwaysCreate”。
ClCompile:
C:\Program Files\Microsoft Visual Studio 10.0\VC\bin\CL.exe /c /I\Include /I\Include\um /I\Include\shared /Isrc\MSDK\include /Zi /nologo /W4 /WX /MP /Ox /Oi /Ot /Oy /D WIN32 /D NDEBUG /D _WINDOWS /D _USRDLL /D QUICKSYNC_EXPORTS /D _CRT_SECURE_NO_WARNINGS /D _WINDLL /D _UNICODE /D UNICODE /Gm- /EHsc /MT /GS- /Gy /fp:precise /Zc:wchar_t /Zc:forScope /Yc"StdAfx.h" /Fp"C:\ffdshow\obj\Release_Win32_VC2010\IntelQuickSyncDecoder\IntelQuickSyncDecoder.pch" /Fo"C:\ffdshow\obj\Release_Win32_VC2010\IntelQuickSyncDecoder\\" /Fd"C:\ffdshow\obj\Release_Win32_VC2010\IntelQuickSyncDecoder\vc100.pdb" /Gd /TP /analyze- /errorReport:prompt src\stdafx.cpp
stdafx.cpp

Note: Intel QuickSync Decoder is built without D3D11 support!
Must have Windows SDK 8.0 installed and environment variable INTELMEDIASDK_WINSDK_PATH
should point to it.
e.g. "C:\Program Files (x86)\Windows Kits\8.0"
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\atlmfc\include\atlconv.h(757): error C2220: 警告被视为错误 - 没有生成“object”文件
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\atlmfc\include\atlconv.h(757): warning C4995: “wcscpy”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\atlmfc\include\atlconv.h(768): warning C4995: “wcscat”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\cstdio(48): warning C4995: “gets”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\cstdio(52): warning C4995: “sprintf”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\cstdio(55): warning C4995: “vsprintf”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\cstring(21): warning C4995: “strcat”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\cstring(22): warning C4995: “strcpy”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\cwchar(30): warning C4995: “swprintf”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\cwchar(31): warning C4995: “vswprintf”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\cwchar(33): warning C4995: “wcscat”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\cwchar(35): warning C4995: “wcscpy”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\intrin.h(1092): warning C4995: “wcscat”: 名称被标记为 #pragma deprecated
1>C:\Program Files\Microsoft Visual Studio 10.0\VC\include\intrin.h(1094): warning C4995: “wcscpy”: 名称被标记为 #pragma deprecated
1>已完成生成项目“C:\ffdshow\src\codecs\IntelQuickSyncDecoder\IntelQuickSyncDecoder.vcxproj”(build 个目标)的操作 - 失败。

生成失败。

已用时间 00:00:04.86

[egur]

Very odd. Doesn't happen on my system. I'll fix it anyway in a few minutes

Update
Fixed

[betaking]

Very odd. Doesn't happen on my system. I'll fix it anyway in a few minutes

Update
Fixed

Thanks! it fix!

[ajp_anton]

* Direct3D11 playback (decode + video processing) on Windows 8. Due to performance degradation in D3D11, it will be used only when needed.Does this mean only when the GPU is not connected to a display?

[egur]

Does this mean only when the GPU is not connected to a display?
Correct, when the iGPU is disconnected. If performance would be the same I'd opt for d3d11 as default.

[Plutotype]

Sorry for asking this maybe again, but does Intel iGPU makes no difference in terms of video playback using LAVfilters and madVR in comparison to AMD/NVidia?
No issues with RGB Full HDMI output? No issues with HD audio?
No issues with dropped frames, colors or scaling? No issues with different fps/hz and resolutions?

Planning to buy a Haswell ultrabook with i7-4558U (HD5100 GPU ).
Thanks

[huhn]

No issues with RGB Full HDMI output?

tthis can make problems is a know issue for over 1 year know

see here: http://communities.intel.com/thread/29420?start=0&tstart=0

this does not affected all tvs out there of course. i got this problem with my pc monitor too...

No issues with different fps/hz and resolutions?

at the moment sandybridge can't display 24000/1001 and ivy is at ~23.9720 this is not perfect but not that bad a repeat frame all ~4 min

this is an hardware issue. but most likely fixed with haswell.

No issues with HD audio?
never heard of problems with audio and intel

but this has nothing to do with quicksync

[egur]

Sorry for asking this maybe again, but does Intel iGPU makes no difference in terms of video playback using LAVfilters and madVR in comparison to AMD/NVidia?
No issues with RGB Full HDMI output? No issues with HD audio?
No issues with dropped frames, colors or scaling? No issues with different fps/hz and resolutions?

Planning to buy a Haswell ultrabook with i7-4558U (HD5100 GPU ).
Thanks

The full range RGB issue didn't affect most TVs, I have full range on my TV on using SandyBridge.

Very close to launch there will be several press reviews that will answer all the questions.

I personally recommend waiting for Haswell since Intel supplies driver updates ~2 years after launch so IvyBridge driver will probably stop updating in mid 2014. This policy may change, but that's the current state.
Haswell also provides better performance and power and the iGPU is much stronger too.

[NikosD]

I want to check your newest DLL with my Win 8 Pro x64 system.

I have a Sandy HD2000 with 9.17.10.3062 drivers and my monitor is connected to dGPU (Radeon 5750 - Catalyst 13.4).

I don't want to install FFDShow and nevcairiel is not helping us by not installing Win 8 on his system. :scared:

If you upload somewhere the DLL, is it possible to test it with LAV video 0.57 by just replacing quicksync DLL ?

I tried latest PotPlayer v1.5.38118 and it doesn't seem capable of using QS decoding (it uses DXVA of AMD card even if I select QS).

Of course if I make a fake display following one of the best guides with pictures here : http://imouto.my/headless-quicksync/ I can use PotPlayer with QS acceleration without connecting a monitor on iGPU.

But the same functionality already exists with Win 7.

Win 8 can use QS acceleration, without even creating a fake display, right ?

My BIOS settings are:
Primary display: Auto
iGPU multi-monitor: Enable

P.S

My MSDK analysis

Intel Media SDK System Analyzer (32 bit)


The following versions of Media SDK API are supported by platform/driver:

Version Target Supported Dec Enc
1.0 HW Yes X X [Adapter 1]
1.0 SW No
1.1 HW Yes X X [Adapter 1]
1.1 SW No
1.3 HW Yes X X [Adapter 1]
1.3 SW No
1.4 HW Yes X X [Adapter 1]
1.4 SW No
1.5 HW No
1.5 SW No
1.6 HW No
1.6 SW No

Graphics Devices:
Name Version State
Intel(R) HD Graphics 9.17.10.3062 Active
AMD Radeon HD 6700 Series 12.104.0.0 Active

System info:
CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
OS: Microsoft Windows 8 Pro
Arch: 64-bit

Installed Media SDK packages (be patient...processing takes some time):

Installed Media SDK DirectShow filters:

Installed Intel Media Foundation Transforms:
Intelχ Quick Sync Video H.264 Encoder MFT : {4BE8D3C0-0515-4A37-AD55-E4BAE19AF
471}




Tips:
- SW target does not work: make sure Media SDK DLL (e.g. libmfxsw64.dll)
is located in your executable path or in system path

Analysis complete... [press ENTER]

[andyvt]

The full range RGB issue didn't affect most TVs, I have full range on my TV on using SandyBridge.


Did you do anything special to make that work? I am not able to make any Intel GPU use RGB-Full over HDMI either of my Panasonic TVs.

[huhn]

there is no way to force it but intel can detect it right.

you can try to change the desktop color to 16 bit some people say this force full rgb didn't work for me. it still uses 24 bit after that change.

[GTPVHD]

http://www.anandtech.com/show/7003/the-haswell-review-intel-core-i74770k-i54560k-tested

http://www.anandtech.com/show/6993/intel-iris-pro-5200-graphics-review-core-i74950hq-tested

Haswell reviews are up, Iris Pro 5200 is really impressive, it trounces the 100W desktop Trinity real good.

[egur]

I have a Sandy HD2000 with 9.17.10.3062 drivers and my monitor is connected to dGPU (Radeon 5750 - Catalyst 13.4).
That should work, very similar to my setup.

I don't want to install FFDShow ...
That's the easiest option, you can later uninstall it. Once installed, copy the QS DLL.

If you upload somewhere the DLL, is it possible to test it with LAV video 0.57 by just replacing quicksync DLL ?
Yes, works for me.

Win 8 can use QS acceleration, without even creating a fake display, right ?
Correct, via D3D11 instead of D3D9. This feature doesn't work on Windows 7.


My MSDK analysis

Intel Media SDK System Analyzer (32 bit)
...
Your setup looks great :)
SW decoding is missing but you don't need that anyway.

[egur]

Did you do anything special to make that work? I am not able to make any Intel GPU use RGB-Full over HDMI either of my Panasonic TVs.

Not really. My Panasonic TV was set to full range.
What wrong is that the iGPU reports partial range but using test patterns it shows that it was sending full range.
The TV reported full range and the blacks (which are great in Panasonic plasma TVs) were excellent.
Setting the iGPU to full range did the opposite, it set the actual range to limited (16-235). So the bug is there last time I checked (6 months ago), but the end result is that the output is fine.
So for my TV its all about wrong labels.
I've reported this issue to the graphics team but that's about all I can do.

[andyvt]

Not really. My Panasonic TV was set to full range.
What wrong is that the iGPU reports partial range but using test patterns it shows that it was sending full range.
The TV reported full range and the blacks (which are great in Panasonic plasma TVs) were excellent.
Setting the iGPU to full range did the opposite, it set the actual range to limited (16-235). So the bug is there last time I checked (6 months ago), but the end result is that the output is fine.
So for my TV its all about wrong labels.
I've reported this issue to the graphics team but that's about all I can do.

So if I understand correctly. You leave the limited/full toggle in the iGPU settings tool alone and configure the TV to use Nonstandard" (RGB-Full) for the HDMI port you have it connected to?