Guest - Testers are needed for the reworked CDateTime core component. See... https://forum.kodi.tv/showthread.php?tid=378981 (September 29) x
  • 1
  • 51
  • 52
  • 53(current)
  • 54
  • 55
  • 73
Intel Kaby Lake Hardware
(2017-07-16, 10:10)wrxtasy Wrote: So for Multichannel PCM - are the Apollo and Kaby Lake NUC's having any issues with that combo ?

AFAIK Should not be issue, but Kaby Lake won't take 24 bit, have to put @ 32 bit.

(2017-07-16, 09:46)wesk05 Wrote: I think I remember @fritsch saying something about zero padding. While that doesn't alter anything, I am not sure whether that can be considered to be "bit exact".

Zero padding is lossless operation and can be reversed.
Reply
(2017-07-16, 09:46)wesk05 Wrote: I think I remember @fritsch saying something about zero padding. While that doesn't alter anything, I am not sure whether that can be considered to be "bit exact".

As it completely contains the original content losslessly and only pads the LSBs I think that would be deemed bit-exact. If it did something like dithering - that would be different - but AIUI it doesn't.

This is a bit like 20 bit audio being carried in 24 bit streams (which is a 'thing' in some pro-circles - where Dolby E - which needs 20 bit carriage - can be carried and recorded cleanly in 24 bit streams with no problems)
Reply
(2017-07-16, 20:12)noggin Wrote: As it completely contains the original content losslessly and only pads the LSBs I think that would be deemed bit-exact. If it did something like dithering - that would be different - but AIUI it doesn't.
Sure! that's why I used bit exact in quotes and didn't mention anything about lossless Wink It will be a problem only on AVR that can take 24-bit input, but the DAC does 16-bit processing. It may apply dithering to all 24-bit input. Now, this shouldn't be a problem on most newer AVRs that have 24-bit/32-bit DACs.

(2017-07-16, 15:05)P.Kosunen Wrote: AFAIK Should not be issue, but Kaby Lake won't take 24 bit, have to put @ 32 bit.

Zero padding is lossless operation and can be reversed.
I guess you are referring to the driver and not actual HDMI output. Reversed by what, the AVR?
Reply
https://downloadcenter.intel.com/downloa...dows-15-46-

https://communities.intel.com/thread/116390

Intel 22.20.16.4729 driver for Kaby Lake. This is a new driver branch with WDDM 2.2 support on Creators Update 1703. This should enable HDR support.
Reply
(2017-07-17, 21:01)wesk05 Wrote: I guess you are referring to the driver and not actual HDMI output. Reversed by what, the AVR?
Could be hardware limit, i beleive linux alsa driver devs would have enabled it if it was possible. Windows driver might have more limits (link).

Zero padding in general can be reversed back to original, there is no data lost and no harm using it.
Reply
(2017-07-18, 06:51)HDGMA Wrote: https://downloadcenter.intel.com/downloa...dows-15-46-

https://communities.intel.com/thread/116390

Intel 22.20.16.4729 driver for Kaby Lake. This is a new driver branch with WDDM 2.2 support on Creators Update 1703. This should enable HDR support.

This driver made both powerdvd and kodi unstable when playing movies on my windows 10 creators update with i5 kaby lake hw Sad
Reply
(2017-07-18, 14:00)sanity Wrote:
(2017-07-18, 06:51)HDGMA Wrote: https://downloadcenter.intel.com/downloa...dows-15-46-

https://communities.intel.com/thread/116390

Intel 22.20.16.4729 driver for Kaby Lake. This is a new driver branch with WDDM 2.2 support on Creators Update 1703. This should enable HDR support.

This driver made both powerdvd and kodi unstable when playing movies on my windows 10 creators update with i5 kaby lake hw Sad
I lost my W10 desktop picture in general after install, only the Windows logo is showing during boot and after that "no signal" is all what's left. It doesn't matter if I change the TV to deep color or not. Seems I must switch to the HDMI 1.4 port to get things going again.

Anyone knows where the manual added custom resolutions settings are stored in Windows 10 so that I can clean things up?
Kodi 19.1 Android/Google(TV) [ Shield TV Pro [64b] / Mi Box S [32b] / Mi Projector / Fire 4k TV stick / CC with Google TV ]
Kodi 19 [3D MVC build] Shuttle DH270 [Kaby Lake i3-7300/HD630 graphics - W10-1903]
Reply
Working fine for me on the Beebox, didn't get to update the NUC. But still no ability to turn on HDR.

Sent from my HTC 10
Reply
kodi crashing immediately on playback, powerdvd fine, no HDR toggle
Reply
(2017-07-19, 14:51)orby Wrote: kodi crashing immediately on playback, powerdvd fine, no HDR toggle

And yet you post no log or other useful information.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
(2017-07-19, 14:22)fmedrano1977 Wrote: Working fine for me on the Beebox, didn't get to update the NUC. But still no ability to turn on HDR.
I have a higher version (4735) driver as part of Windows 10 Insider Preview build (16241). I don't have any HDR toggle, but HDR/WCG is turned on automatically with HDR content (video clips or 4K Ultra HD Blu-ray disc) in PowerDVD 17. Not sure whether it is a PowerDVD problem or not, but the output is always 4K 60Hz 12-bit YCbCr 4:2:0 when HDR is activated. You can set the desktop to a different mode, but when HDR is activated it will switch to 4K 60Hz. I haven't tried madVR passthrough.
Reply
(2017-07-16, 15:05)P.Kosunen Wrote:
(2017-07-16, 10:10)wrxtasy Wrote: So for Multichannel PCM - are the Apollo and Kaby Lake NUC's having any issues with that combo ?

AFAIK Should not be issue, but Kaby Lake won't take 24 bit, have to put @ 32 bit.

(2017-07-16, 09:46)wesk05 Wrote: I think I remember @fritsch saying something about zero padding. While that doesn't alter anything, I am not sure whether that can be considered to be "bit exact".

Zero padding is lossless operation and can be reversed.

Hi guys, just so you know there are issues with high resolution audio on the NUC's that aren't mentioned on the Kodi forums.
Perhaps not directly related to Kodi but probably affecting it most likely.
16bit/192KHz max output via HDMI
Reply
(2017-07-19, 22:26)nickr Wrote:
(2017-07-19, 14:51)orby Wrote: kodi crashing immediately on playback, powerdvd fine, no HDR toggle

And yet you post no log or other useful information.

funny didn't know a kodi log would help me toggle HDR in windows 10, i will post one next time though
Reply
(2017-07-20, 10:36)DG77 Wrote: Hi guys, just so you know there are issues with high resolution audio on the NUC's that aren't mentioned on the Kodi forums.
Perhaps not directly related to Kodi but probably affecting it most likely.
16bit/192KHz max output via HDMI
Have you tried 32bit/192kHz?
Reply
(2017-07-20, 10:36)DG77 Wrote:
(2017-07-16, 15:05)P.Kosunen Wrote:
(2017-07-16, 10:10)wrxtasy Wrote: So for Multichannel PCM - are the Apollo and Kaby Lake NUC's having any issues with that combo ?

AFAIK Should not be issue, but Kaby Lake won't take 24 bit, have to put @ 32 bit.

(2017-07-16, 09:46)wesk05 Wrote: I think I remember @fritsch saying something about zero padding. While that doesn't alter anything, I am not sure whether that can be considered to be "bit exact".

Zero padding is lossless operation and can be reversed.

Hi guys, just so you know there are issues with high resolution audio on the NUC's that aren't mentioned on the Kodi forums.
Perhaps not directly related to Kodi but probably affecting it most likely.
16bit/192KHz max output via HDMI

(2017-07-20, 13:50)P.Kosunen Wrote:
(2017-07-20, 10:36)DG77 Wrote: Hi guys, just so you know there are issues with high resolution audio on the NUC's that aren't mentioned on the Kodi forums.
Perhaps not directly related to Kodi but probably affecting it most likely.
16bit/192KHz max output via HDMI
Have you tried 32bit/192kHz?

I'm not quite sure how to do that?
I'm running Win10pro and never saw such a setting in Kodi.
Reply
  • 1
  • 51
  • 52
  • 53(current)
  • 54
  • 55
  • 73

Logout Mark Read Team Forum Stats Members Help
Intel Kaby Lake Hardware3
This forum uses Lukasz Tkacz MyBB addons.