Is anyone from intel team looking in to this issue? It is causing severe quality issue. Please provide some solution for this.
I am using vpp samples from Intel Media SDK Samples 2016 188.8.131.52 and Intel(R)_Media_SDK_2016.0.1. I need to convert RGB32 (BGRA) frames into NV12 and pass them to h264 encoder.
I am observing that HW implementation of VPP is blurring the text images portion in output frame, but if I use SW implementation then conversion is perfectly fine. In HW impl, part of text (specifically the vertical lines area) are slightly reddish or blueish. Please refer the attachment.
Can you let me know if it is any known bug in VPP or Graphics driver? How to correct it and make it with same quality as in SW impl? I prefer not to use SW impl of VPP considering the speed factor.
i. sys_analyzer.txt: system analyzer log (Env: Win8.1 (64 bit), HD Graphics 4400, driver 10.18.14.4414)
ii. VppIn.bgr: input frame in BGRA format
iii. VppOut_HW.nv12: output nv12 frame generated through HW impl
iv. VppOut_SW.nv12: output nv12 frame generated through SW impl
v. Compare.jpg: snap shot of both output frame with highlighting the issue
I used following command line parameters:
1. sample_vpp -i VppIn.bgr -sw 1920 -sh 1080 -scc rgb4 -dw 1920 -dh 1080 -dcc nv12 -lib hw -o VppOut_HW.nv12
2. sample_vpp -i VppIn.bgr -sw 1920 -sh 1080 -scc rgb4 -dw 1920 -dh 1080 -dcc nv12 -lib sw -o VppOut_SW.nv12
Thanks for the update, glad to know that this issue is being fixed. It would be helpful if you can share the tentative timeline by when we get the fix.
Yes, but I am already using d3d11 memory on Windows8 onwards, and system memory or d3d9 memory on windows7 OS (as my product needs to support all OS from Win7 onwards).
Are you not seeing this issue if use d3d11? I observed this issue first on Win8.1 OS using d3d11 itself.
Ok. Though I need the fix for windows7 OS also(i.e. using system or d3d9 memory), but if d3d11 fix is quick I can start using that at least for windows8 and 10 also.
It's driver problem. Dev team is working on a solution now.
We are working on solution, but for now I can't say exactly when the fix will be ready. I'll keep you in touch.
Has Intel fixed this issue in driver? Please let me know if there is any update.