• 1
  • 48
  • 49
  • 50(current)
  • 51
  • 52
  • 56
WIP Windows DirectX 11 upgrade test thread
(2015-12-27, 03:02)bossanova808 Wrote: @afedchin

Just tried that version (26th Dec).

AMD 6530D set to YCbCr 4:4:4 (and AMD reports 10 bit being sent to Denon X2100 Amp). Win 7 64 bit all current updated. AMD latest drivers 'Crimson'.

With hardware acceleration:
Kodi set to full range:
UI good,
Videos elevated blacks
This means what your drivers change color range despite the requirements of the application. Please check your video settings in ADM Control Center
Reply
@afedchin - I have. There are very few video settings to check in Crimson. It's....balls, really. There's no color range setting in the driver at all with these 'current latest drivers'.

I can go back to another driver obviously, was using this in a hope the RGB flicker would be fixed (it's not).

Another option is this: http://forums.guru3d.com/showthread.php?t=403389 - that lets you explicitly set various missing things, including the color range.

I will experiment and report back.
Addons I wrote &/or maintain:
OzWeather (Australian BOM weather) | Check Previous Episode | Playback Resumer | Unpause Jumpback | XSqueezeDisplay | (Legacy - XSqueeze & XZen)
Sorry, no help w/out a *full debug log*.
Reply
@afedchin - quick test as the kids are dominating the TV over holiday time Sad

I tried with the above tool that let's me explicitly set limited range.

I then compared Isengard to your 26th Dec Jarvis.

An easy test is the opening credits to Terminator Genisys (bluray rip) - on Isengard, there are no visible black borders as the names ('20th Century',Schwarzenegger' etc) go past - the black of the film is not distinguishable from the borders. I don't suppose you have that film and want to run a quick check? It seems to me that the black there should be pitch black.

On Jarvis, even with the driver explicitly set to limited range, there is still a difference - the blacks of the credits are very dark greys, not blacks.

I suppose it is possible that Isengard is crushing the blacks and Jarvis isn't, or something, but Jarvis still feels milky to me overall. And on video test / calibration files I've always seen the detail emerge when it should with Isengard, but I haven't tried these with your recent Jarvis yet to get more info.

I'll try with another driver when I can kick the kids off too...

I doubt the log helps, but just in case: https://dl.dropboxusercontent.com/u/1088...imited.log
Addons I wrote &/or maintain:
OzWeather (Australian BOM weather) | Check Previous Episode | Playback Resumer | Unpause Jumpback | XSqueezeDisplay | (Legacy - XSqueeze & XZen)
Sorry, no help w/out a *full debug log*.
Reply
(2015-12-27, 10:35)bossanova808 Wrote: I tried with the above tool that let's me explicitly set limited range.
No need to explicitly set limited range, just set is to application decide.
Reply
Hi afedchin,

Many thanks for your hard work on this. Great to see hardware based 3D in master Smile

I'm running an Intel core i7 processor with Intel HD Graphics 4600, on latest Intel driver, so obviously using Intel Stereo Driver. I'm testing with a full sbs (3840x1080) file, that switches to 3D and plays fine in Stereoscopic Player (using Intel Stereo Driver).

With Kodi and hardware based, i'm getting a delay in the switch to 3D, then a black screen. Audio continues to plays fine. Here's a link to the debug log (.pdb file is in place) on pastebin...

http://pastebin.com/HL6G21AS

Hopefully you can find the bug and fix Smile

Also, just confirming... with hardware based 3D (Intel Stereo Driver), with 3840x1080 full sbs, I should be getting the full 1080p 3D resolution (via frame packing), and not half sbs as with kodi sbs 3D setting?

Many thanks
Reply
Tried the new build and it works as it should (at least with desktop rgb full, kod i limited and TV limited), thanks
I have a question about your changes on dxva render. One of the missing feature of dxva render is the support for handling rotation. A video could have an orientation and kodi supports it in pixel shader and software. Dxva does not.did your work makes it easier to get?
Reply
@afedchin

I could not get it to work with Crimson drivers and that tool.

So:
Purged all AMD drivers
Installed AMD drivers 15.6 beta - I could probably use the last non crimson release too (15.11 beta), but Isengard doesn't play so well with AMD drivers > 15.7, and I am still using Isengard as my main family friendly install.

Kodi - set to full, driver to full, YCbCr 4:4:4 (there's no 'let the application decide' that I can see as such? Am I missing something?) - and the blacks are correct (yay!). Works for both Isengard and Jarvis so that's handy.

So, that's good. Not seeing any other major issues, although I do have a small amount of repeatable video tearing on an Episode of Mr Robot with Jarvis that I don't see in Isengard. But I've only seen it in that one file so far, albeit my testing has been limited.

Thanks again for all your efforts.
Addons I wrote &/or maintain:
OzWeather (Australian BOM weather) | Check Previous Episode | Playback Resumer | Unpause Jumpback | XSqueezeDisplay | (Legacy - XSqueeze & XZen)
Sorry, no help w/out a *full debug log*.
Reply
(2015-12-29, 23:13)liquidskin76 Wrote: http://pastebin.com/HL6G21AS

Hopefully you can find the bug and fix Smile

Also, just confirming... with hardware based 3D (Intel Stereo Driver), with 3840x1080 full sbs, I should be getting the full 1080p 3D resolution (via frame packing), and not half sbs as with kodi sbs 3D setting?

Many thanks
Need to provide a Debug Log. Your log is not debug.
yes, you get the full 3D resolution.

(2015-12-30, 02:24)phate89 Wrote: Tried the new build and it works as it should (at least with desktop rgb full, kod i limited and TV limited), thanks
I have a question about your changes on dxva render. One of the missing feature of dxva render is the support for handling rotation. A video could have an orientation and kodi supports it in pixel shader and software. Dxva does not.did your work makes it easier to get?
Working on it.
Reply
(2015-12-30, 06:50)bossanova808 Wrote: @afedchin


Kodi - set to full, driver to full, YCbCr 4:4:4 .
Can I ask why did you use yCbCr? H264 videos are yCbCr but gpus thinks in rgb full so your video gets converted to rgb full and then converted back to yCbCr. It might create several quality problems..

(2015-12-30, 07:52)afedchin Wrote: Working on it.

Great thanks
Reply
(2015-12-30, 11:48)phate89 Wrote:
(2015-12-30, 06:50)bossanova808 Wrote: Kodi - set to full, driver to full, YCbCr 4:4:4 .
Can I ask why did you use yCbCr? H264 videos are yCbCr but gpus thinks in rgb full so your video gets converted to rgb full and then converted back to yCbCr. It might create several quality problems..

Because I have been experiencing intermittent flickering issues with RGB mode. I'll try it again shortly, but particularly with my projector it was re-syncing like a crazy thing, and there were clear line artifacts etc too.

I'd prefer to use RGB mode, but it needs to be stable. Note these issues were with two different outputs, both completely reliable in YCbCr mode (plasma and projector)
Addons I wrote &/or maintain:
OzWeather (Australian BOM weather) | Check Previous Episode | Playback Resumer | Unpause Jumpback | XSqueezeDisplay | (Legacy - XSqueeze & XZen)
Sorry, no help w/out a *full debug log*.
Reply
Ok so motivated myself to reinstall necessary things to compile Kodi but I have problem with resulting exe.

It seems it's related to DX11 so posting here as it seems it's now in master.

I followed everything as usual, compile all dependencies, all compile fine but EXE compiled shows an unable to create GUI error with the logs :

Code:
11:50:00 T:103240   DEBUG: CRenderSystemDX::InitRenderSystem - Initializing D3D11 Factory...
11:50:00 T:103240   DEBUG: CRenderSystemDX::SetMonitor - Selected \\.\DISPLAY1 output.
11:50:00 T:103240   DEBUG: CRenderSystemDX::SetMonitor - Selected NVIDIA GeForce GTX 580 adapter.
11:50:00 T:103240   DEBUG: CRenderSystemDX::CreateDevice - First try to create device failed with error: .
11:50:00 T:103240   DEBUG: CRenderSystemDX::CreateDevice - Trying to create device with lowest feature level: 0xb000.
11:50:00 T:103240   DEBUG: CRenderSystemDX::CreateDevice - Next try to create device failed with error: .
11:50:00 T:103240   DEBUG: CRenderSystemDX::CreateDevice - Trying to create device without video API support.
11:50:00 T:103240   ERROR: CRenderSystemDX::CreateDevice - D3D11 device creation failure with error .
11:50:00 T:103240   FATAL: CApplication::Create: Unable to init rendering system

A test build triggered from Jenkins does works ok, I just replace the exe with mine that is compiled against the exact same revision.

Is there some new specific steps for DX 11 building ? ( I used to have compiled XBMC / Kodi for years before and have some knowledge about basic setup needed)

Windows 10 all updates / drivers installed.
Reply
@afedchin
With the latest build you posted the video works well and the greys are good but I have a resizing problem. I have a 1080p tv and every video with 1920x1080 looks good but for example with 1920x800 you get a squashed image vertically and with 1280x720 you get only a zoomed portion of the frame.. With latest jarvis build it doesn't happen
log:
http://xbmclogs.com/p0ict8icw
Reply
(2015-12-30, 12:59)Tolriq Wrote: Windows 10 all updates / drivers installed.
http://forum.kodi.tv/showthread.php?tid=...pid2186625

(2015-12-30, 13:10)phate89 Wrote: @afedchin
With the latest build you posted the video works well and the greys are good but I have a resizing problem. I have a 1080p tv and every video with 1920x1080 looks good but for example with 1920x800 you get a squashed image vertically and with 1280x720 you get only a zoomed portion of the frame.. With latest jarvis build it doesn't happen
log:
http://xbmclogs.com/p0ict8icw
It will be fixed with proper fix of color range issue.

(2015-12-30, 12:00)bossanova808 Wrote: Because I have been experiencing intermittent flickering issues with RGB mode.
I think it's a hardware issue. perhaps HDMI cable may cause this.
Reply
(2015-12-30, 07:52)afedchin Wrote:
(2015-12-29, 23:13)liquidskin76 Wrote: http://pastebin.com/HL6G21AS

Hopefully you can find the bug and fix Smile

Also, just confirming... with hardware based 3D (Intel Stereo Driver), with 3840x1080 full sbs, I should be getting the full 1080p 3D resolution (via frame packing), and not half sbs as with kodi sbs 3D setting?

Many thanks
Need to provide a Debug Log. Your log is not debug.
yes, you get the full 3D resolution.

Hi afedchin,

Debug log is definitely on. I've run off another log...

http://pastebin.com/r9p072CU

Also got a crash this time... Error "ERROR: Exception caught on main loop. Exiting". Here's the crashlog's and stacktrace's...

https://dl.dropboxusercontent.com/u/5689...174545.dmp
https://dl.dropboxusercontent.com/u/5689...174546.dmp
https://dl.dropboxusercontent.com/u/5689...174545.txt
https://dl.dropboxusercontent.com/u/5689...174546.txt

Many thanks
Reply
(2015-12-30, 20:10)liquidskin76 Wrote: http://pastebin.com/r9p072CU

Also got a crash this time... Error "ERROR: Exception caught on main loop. Exiting". Here's the crashlog's and stacktrace's...

Many thanks
Driver hangs. So try to install latest Beta driver https://downloadcenter.intel.com/downloa...1-10-15-40-
Reply
  • 1
  • 48
  • 49
  • 50(current)
  • 51
  • 52
  • 56

Logout Mark Read Team Forum Stats Members Help
Windows DirectX 11 upgrade test thread6