I’ve noticed that with OpenPHT color space set to 16-235, my GPU (Intel Haswell NUC) set to FULL RANGE, and my Samsung KS8000 HDMI level set to LOW (limited), that DXVA2 is producing crushed blacks. No issues, though, with software decoding.
Interestingly, Kodi does not have this issue with the same settings (Kodi also set to 16-235).
Is there a reason why DXVA2 would produce crushed blacks?
Thanks.
Are you sure the PMS isn’t transcoding?
@benjaminwolf said:
Are you sure the PMS isn’t transcoding?
Absolutely sure. It’s local play over Ethernet and set to play as is. Why would DXVA2 cause the image to be darker?
I’m no expert at this, but using dxva2 should surrender all the image controls over to the graphics driver, right?
In that case, something with the driver must cause crushed blacks. So maybe double check the settings for your graphic driver. Or up/downgrade the driver for test? Just tossing some ideas.
But Kodi is fine with DXVA2 enabled. So… wouldn’t that means OpenPHT is the issue?!
@WilliamG said:
But Kodi is fine with DXVA2 enabled. So… wouldn’t that means OpenPHT is the issue?!
Ah, right. I missed that.
Very strange indeed.
@WilliamG said:
But Kodi is fine with DXVA2 enabled. So… wouldn’t that means OpenPHT is the issue?!
did you try the same version of KODI that the current openPHT is based off ? (i think its frodo) or did you just download the latest Kodi?
I used I believe the latest version of Kodi. Is there a new version of OpenPHT in the works with the same…DXVA2 implementation?
OpenPHT 1.6.0+ is using the playback and rendering engine from Kodi Jarvis 16.1 for all platforms except Windows/DXVA2.
The Windows version was held back and uses the DirectX 9 rendering engine from Kodi Isengard 15.2 instead of the Direct X 11 rendering engine added in Kodi Jarvis.
The upcoming 1.7.0 release will still use the Direct X 9 rendering engine but I will look into upgrading it to Direct X 11 in a future update, it has been proven stable for Kodi Jarvis and it should fix color space issues.
@Kwiboo said:
OpenPHT 1.6.0+ is using the playback and rendering engine from Kodi Jarvis 16.1 for all platforms except Windows/DXVA2.
The Windows version was held back and uses the DirectX 9 rendering engine from Kodi Isengard 15.2 instead of the Direct X 11 rendering engine added in Kodi Jarvis.The upcoming 1.7.0 release will still use the Direct X 9 rendering engine but I will look into upgrading it to Direct X 11 in a future update, it has been proven stable for Kodi Jarvis and it should fix color space issues.
Thank you for the response! I love OpenPHT, so it would be great to see the DirectX11 rendering engine update at some point! 
