Kodi Community Forum
WIP Windows DirectX 11 upgrade test thread - Printable Version

Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Development (https://forum.kodi.tv/forumdisplay.php?fid=32)
+--- Forum: Kodi Application (https://forum.kodi.tv/forumdisplay.php?fid=93)
--- Thread: WIP Windows DirectX 11 upgrade test thread (/showthread.php?tid=218274)



RE: Windows DirectX 11 upgrade test thread - afedchin - 2016-02-29

@ciukacz,
thanks but can you test all cases as describet below? don't touch input range in driver setting change only output quantization.

1. full (in driver) + full (in Kodi)
2. full + limited
3. limited + full
4. limited + limited.


RE: Windows DirectX 11 upgrade test thread - Ed76 - 2016-02-29

(2016-02-29, 14:40)ciukacz Wrote: questions regarding intel test:

which binaries? http://mirrors.kodi.tv/test-builds/win32/KodiSetup-20160226-8ff28fb-range_test.exe ?
should "dxvapasscolorrange" setting be used for the test? what value of the variable?

my driver settings: output quantization set to full range, input range set to application settings.
are these ok for the test result to be valid?

maybe we should establish some rules regarding expected correct results, for example:
1. using test disk avshd709, test file 1-Black Clipping.mp4: bars 17+ should visibly blink, 2-16 only after raising brightness
2. same test disk, test file 1-Grayscale Ramp.mp4, banding visible but no more than: https://www.youtube.com/watch?v=5acG8I79NxM

simply install the testversion. there is no need for an advancedsetting/variable. set full rgb output in driver (pixelformat). then try to force full/limited for video within driver.


RE: Windows DirectX 11 upgrade test thread - Ed76 - 2016-03-09

just tested this with a htpc of a friend (amd a6 kaveri). i got the same results as with my pc (amd richland).

@phate89: you told you also have a amd graphic card. have you also done these test? do you get different results (also with kodi 16 final)?


RE: Windows DirectX 11 upgrade test thread - edrikk - 2016-03-21

(2015-09-01, 17:02)Shine Wrote: Here's an always-on-top build based on Isengard-3d763c9 (20150831) and DX11-0a71ba7 (20150827). Untested because I'm at work right now...

Known issue: Kodi might freeze when a competing always-on-top window pops up behind Kodi. As promised, I will PR once I find the time to work around this issue.

Edit: For those who didn't find it, Always-on-top is an option under System -> Video output. Default is disabled, so you have to enable it manually.

Hi @Shine,

Just wondering if you're still around, and what are the odds of a PR for this?
Would still LOVE to see this in Kodi...


RE: Windows DirectX 11 upgrade test thread - _saiko - 2016-03-22

@Ed76 how are you setting video dynamic range in catalyst crimson when they removed those advanced options? (I'm referring to this: https://community.amd.com/thread/191799)
Also, I as well never see bars <17 blinking when proper black levels are displayed (slight change when upping the brightness on the display).

Anyhow Win7x64 SP1, AMD R9 280 w/ catalyst 16.3.1.
I'm also suffering from wrong black levels with full-full-full RGB (driver-kodi-display).
Kodi 15.2 with DXVA - levels ok
Kodi 16.x with DXVA - wrong levels
Kodi 16.x w/o DXVA - levels ok

I'll test the testbuild of Kodi (is it the one @ciukacz linked?) later on to see if there's any change.


RE: Windows DirectX 11 upgrade test thread - Ed76 - 2016-03-23

(2016-03-22, 12:41)_saiko Wrote: @Ed76 how are you setting video dynamic range in catalyst crimson when they removed those advanced options? (I'm referring to this: https://community.amd.com/thread/191799)
Also, I as well never see bars <17 blinking when proper black levels are displayed (slight change when upping the brightness on the display).

Anyhow Win7x64 SP1, AMD R9 280 w/ catalyst 16.3.1.
I'm also suffering from wrong black levels with full-full-full RGB (driver-kodi-display).
Kodi 15.2 with DXVA - levels ok
Kodi 16.x with DXVA - wrong levels
Kodi 16.x w/o DXVA - levels ok

I'll test the testbuild of Kodi (is it the one @ciukacz linked?) later on to see if there's any change.

there are several ways to change color range for video only within driver.

1) install latest catalyst driver
2) install latest crimson and change the setting within registry. if you dont now the registry entry you can use this tool: http://forums.guru3d.com/showthread.php?s=be8149a426a7434140a9506baa3d58e6&t=403389
3) install latest catalyst (+catalyst control center). download and unpack latest crimson. install crimson driver (only the driver!) via windows device manager. the "old" catalyst contol center will now work with latest crimson driver.

you cant test the "testversion" because the link is down. but as i write some posts above: download kodi beta 4, unpack with 7zip, search for shader-folder. from there you copy/replace the "convolutionsep-6x6" shader to kodi 16 final. make sure to set "lanzcos 3" or "spline" (not the optimized one) as upscaling method within kodi.

please post your results here.


RE: Windows DirectX 11 upgrade test thread - Ed76 - 2016-04-07

@afedchin:
it seems its not possible to download the testversion anymore, so nobody cant test this.

at the moment limited colorrange (within kodi) is broken for amd cards or most amd cards. as i wrote: your testversion worked for me (amd) and i guess it also worked for you (intel?). maybe it would be possible to integrate you changes (your testversion) into kodi 17?


RE: Windows DirectX 11 upgrade test thread - hybe - 2016-04-10

@afedchin

Just wanted to confirm problems with Jarvis and DX11, concerning black levels.

Was trying out Jarvis 16.0, and had to revert back to 15.2 to avoid black-clipping.
Havn't tried to turn off DXVA2 though, but listening to others here, I guess it works by doing just that. Not optimal though, which makes me stay with 15.2 for now.

[Display]
Operating System: Windows 10 Pro N, 64-bit
DirectX version: 12.0
GPU processor: GeForce GTX 780
Driver version: 362.00
Direct3D API version: 12
Direct3D feature level: 11_0

Anything more you need?

my original thread:
268430 (thread)


RE: Windows DirectX 11 upgrade test thread - afedchin - 2016-04-10

here is test build http://mirrors.kodi.tv/test-builds/win32/KodiSetup-20160226-8ff28fb-range_test.exe


RE: Windows DirectX 11 upgrade test thread - Ed76 - 2016-04-10

@hybe

please test all the cases afedchin requested. look here: 2261457 (post)

thanks.


RE: Windows DirectX 11 upgrade test thread - wesk05 - 2016-04-11

I tested the range_test build on my HTPC (Intel 4570S (HD Graphics 4600), AMD 7750 graphics card, Win 10 x64)

1) Intel: Display Quantization-Full, Kodi - Use limited color range
0-15 and 236-255 levels are passed (there are some minor rounding errors, eg. 15,15,15 is 15,15,16, 1,1,1 is 0,0,1 and so forth).

2) AMD: Crimson driver 16.4.1, Pixel format - RGB Full, Kodi - Use limited color range
0-15 and 236-255 levels are passed. In fact, the RGB pixel values are spot on. Not a single error.

All pixel readings were taken using DVDO AVLab TPG 4K Pattern Generator's color checker function.

BTW and WTW are passed only when Kodi is set to use limited color range and the display driver output is set to full range.

This doesn't seem to work on the latest Krypton builds.


RE: Windows DirectX 11 upgrade test thread - afedchin - 2016-04-11

(2016-04-11, 02:27)wesk05 Wrote: 0-15 and 236-255 levels are passed
what do you mean?


RE: Windows DirectX 11 upgrade test thread - wesk05 - 2016-04-11

(2016-04-11, 09:20)afedchin Wrote:
(2016-04-11, 02:27)wesk05 Wrote: 0-15 and 236-255 levels are passed
what do you mean?

It just means that when the video contains BTB (YUV 0-15) or WTW (YUV 236-255), those levels are present in the HDMI output also. By default, Kodi doesn't passthrough BTB or WTW. It is either clamped or discarded completely.


RE: Windows DirectX 11 upgrade test thread - afedchin - 2016-04-11

Kodi doesn't control HDMI output levels, the driver does this.


RE: Windows DirectX 11 upgrade test thread - wesk05 - 2016-04-11

(2016-04-11, 20:14)afedchin Wrote: Kodi doesn't control HDMI output levels, the driver does this.

Well... it doesn't work on the Krypton builds.