•   
  • 1
  • 13
  • 14
  • 15
  • 16
  • 17(current)
Auto frame rate switching & dynamic range matching - 4K (HDR10) capable Hardware
(2018-11-08, 10:15)wrxtasy Wrote:
(2018-11-08, 08:11)wesk05 Wrote:
(2018-11-06, 13:42)outcave Wrote: @timstephens24 and @noggin I can assure you that even if the Nvidia Shield Colorspace conversion done well I'm able to see chromatic differences on my Panasonic OLED TV between "pure" Rec. 709 and Rec. 709 converted to Rec. 2020 when I put in play Rec. 709 content.
 BT.709 to BT.2020 gamut mapping on Shield accurately follows ITU BT.2087 recommendation. Any luminance difference that you see with Shield's mapped output on a display has to do with the display not applying BT.1886 gamma for BT.2020 SDR input.   

That may be the case be there appears to be an ever increasing list of displays not applying BT.1886 gamma for BT.2020 SDR inputs and then producing unacceptable results for end users with mixed Rec.709 and BT.2020 content.

The question then becomes have NVIDIA chosen the wrong path to take ?

Should they be using Rec.709 <<-->> BT.2020 colorspace switching vs the current Oreo colorspace conversion ?

The old underlying v3.xx, modded Linux Kernel would not be helping either.   
Yes, I think Nvidia chosen the wrong path to take (using conversion), but may be it was forced due to Android 7 API limitation.
Yes, if it's technically possible, Nvidia should use Rec.709 <<-->> BT.2020 colorspace switching instead to use colorspace conversion.

On my side I'm in contact with Nvidia Level 2 support, but I'm still trying to understand if a colorspace switching is technically possible on Andriod 8.
For what I know the Apple TV do that colorspace switching and I expect it will be the possibility also for the Nvidia Shield.
Kodi 18: Nvidia Shield TV (main device) and LibreELEC on Raspberry Pi 2 and Odroid C2
TV: Panasonic TX-55EZ950E (OLED)
AVR: Onkyo TX-NR509 (HDMI ARC)
Reply
Hi, I just bought a fire stick 4K as I now live in the UK and am quite satisfied so far. But I have a problem with kodi 17.6 krypton I just installed with Downloader (android 32 bit). I just cant use the autoframe rate option: it can be h264 720/1080p or h265, I got stuttering and its just impossible to watch anything. It works great with amazon prime videos turning my tv from 60 to 24 Hz for example but not through Kodi unfortunately. Is there any way to fix that?
If not, what tv box would you advise for that purpose, $60 max?
Thanks
Reply
Read this post....

The Best Of - categorised - media players on the market (click)
(Specifically the .. 24p Kodi use on Android devices section)

Then $60 - 4K Kodi only.... THIS post (click)
You need to run 4K auto refresh / resolution switching - capable - LibreELEC or CoreELEC Kodi on such a device.

Reply
thks wrxtasy. Glad to see you again after I read so much of your threads about openelec for odroid c1+ Smile maybe I should consider buying this c2 actually
Reply
Hi @wrxtasy 

It's time to update the first post of this thread because now the Nvidia Shield TV is able to do the colorspace autoswitch!

Since Nvidia Shield Firmware version 7.2.2 the colorspace switch is implemented. Nvidia talk about a "beta feature" but it works based on my tests. This feature, that is called "Colorimetry", is not enabled by default and should be enabled by Enable Developers options: Go to Settings > About > Build > Click 7 times on build to become a developer. Then, go to Settings > Developer Options > Colorimetry (set toggle to ON) > restart Nvidia Shield for changes to take effect.

I set Nvidia Shield to Rec. 709 (BT.709) as default colorspace (because, in my opinion, most contents are in Rec. 709) and when I go put in play a Rec. 2020 (BT.2020) content (default colorspace of HDR) the Shield will go to switch to Rec. 2020 (and my TV recognize and accept the "new" Rec. 2020 signal).
These are the results of my test:
Kodi 18: OK, works! (Play Rec. 709 content -> no switch; Play Rec. 2020 content -> switch to Rec.2020)
PLEX: OK, works! (Play Rec. 709 content -> no switch; Play Rec. 2020 content -> switch to Rec.2020)
Netflix: OK, works! (Play Rec. 709 content -> no switch; Play Rec. 2020 content -> switch to Rec.2020)
Amazon Video: OK, works! (Play Rec. 709 content -> no switch; Play Rec. 2020 content -> switch to Rec.2020)
Youtube: Not OK, it does not work well. As we know Youtube HDR content are non compatible with Nvidia Shield because Nvidia Shield does not HW decode VP9 Profile 2 codec. But the problem here is when you go to put in play a 4K (2160p) SDR video (so with BT.709 colorspace also confirmed in the "stats for nerds" of Youtube) the Shield will go to switch from BT.709 to BT.2020. So, it seems, the Nvidia Shield for 2160p Youtube videos will go always to switch from  Rec. 709 to Rec. 2020. Anyway the color results is good (not whashed) so, may be, in that case Nvidia Shield will got to convert Rec. 709 to Rec. 2020.
Anyway, since HDR Youtube video cannot be played because Nvidia Shield does not HW decode VP9 Profile 2 codec, in my opinion this is a very minor limitation of the new colorspace switch feature.

Bye!
Kodi 18: Nvidia Shield TV (main device) and LibreELEC on Raspberry Pi 2 and Odroid C2
TV: Panasonic TX-55EZ950E (OLED)
AVR: Onkyo TX-NR509 (HDMI ARC)
Reply
Hi

8bit Rec709 or 10bit 709 in ur Settings?
Reply
why isn't fire tv 4k (2018) listed under "Auto dynamic Frame Rate matching / switching" ?
Reply
(2019-03-01, 14:27)k1lerbee Wrote: why isn't fire tv 4k (2018) listed under "Auto dynamic Frame Rate matching / switching" ?
 Possibly because it isn't automatic - and requires very specific API access.  Like the nVidia Shield TV - Netflix, BBC iplayer and most other third party etc. don't frame rate switch on the Fire TV 4K - though Prime Video and Kodi do.
Reply
(2019-03-01, 18:50)noggin Wrote:
(2019-03-01, 14:27)k1lerbee Wrote: why isn't fire tv 4k (2018) listed under "Auto dynamic Frame Rate matching / switching" ?
 Possibly because it isn't automatic - and requires very specific API access.  Like the nVidia Shield TV - Netflix, BBC iplayer and most other third party etc. don't frame rate switch on the Fire TV 4K - though Prime Video and Kodi do. 
 ok as long as Kodi does automatic framerate switch I am fine
Reply
(2019-02-14, 10:45)outcave Wrote: Hi @wrxtasy 

It's time to update the first post of this thread because now the Nvidia Shield TV is able to do the colorspace autoswitch!

Since Nvidia Shield Firmware version 7.2.2 the colorspace switch is implemented. Nvidia talk about a "beta feature" but it works based on my tests. This feature, that is called "Colorimetry", is not enabled by default and should be enabled by Enable Developers options: Go to Settings > About > Build > Click 7 times on build to become a developer. Then, go to Settings > Developer Options > Colorimetry (set toggle to ON) > restart Nvidia Shield for changes to take effect.

I set Nvidia Shield to Rec. 709 (BT.709) as default colorspace (because, in my opinion, most contents are in Rec. 709) and when I go put in play a Rec. 2020 (BT.2020) content (default colorspace of HDR) the Shield will go to switch to Rec. 2020 (and my TV recognize and accept the "new" Rec. 2020 signal).
These are the results of my test:
Kodi 18: OK, works! (Play Rec. 709 content -> no switch; Play Rec. 2020 content -> switch to Rec.2020)
PLEX: OK, works! (Play Rec. 709 content -> no switch; Play Rec. 2020 content -> switch to Rec.2020)
Netflix: OK, works! (Play Rec. 709 content -> no switch; Play Rec. 2020 content -> switch to Rec.2020)
Amazon Video: OK, works! (Play Rec. 709 content -> no switch; Play Rec. 2020 content -> switch to Rec.2020)
Youtube: Not OK, it does not work well. As we know Youtube HDR content are non compatible with Nvidia Shield because Nvidia Shield does not HW decode VP9 Profile 2 codec. But the problem here is when you go to put in play a 4K (2160p) SDR video (so with BT.709 colorspace also confirmed in the "stats for nerds" of Youtube) the Shield will go to switch from BT.709 to BT.2020. So, it seems, the Nvidia Shield for 2160p Youtube videos will go always to switch from  Rec. 709 to Rec. 2020. Anyway the color results is good (not whashed) so, may be, in that case Nvidia Shield will got to convert Rec. 709 to Rec. 2020.
Anyway, since HDR Youtube video cannot be played because Nvidia Shield does not HW decode VP9 Profile 2 codec, in my opinion this is a very minor limitation of the new colorspace switch feature.

Bye!

Does this mean that my TV will use hardware upscalers for 720p/1080p content? Information from another thread:
 Image
Reply
  •   
  • 1
  • 13
  • 14
  • 15
  • 16
  • 17(current)
 
Thread Rating:
  • 4 Vote(s) - 4 Average



Logout Mark Read Team Forum Stats Members Help
Auto frame rate switching & dynamic range matching - 4K (HDR10) capable Hardware44