[noggin]

@wrxtasy @hdmkv Good afternoon, I'm thinking of buying one Zidoo x9s.

I need:

- auto framerate
- auto switching color range & space (for example: 2160p 4.2.0 10bit BT2020 and i'll put one movie 1080p, the system changes auto to 1080p resolution 4.2.0 8bit BT 709)

Does Zidoo x9s do it whit the last beta firmware?

  
I don't think 1080p 4:2:0 8-bit BT 709 is a valid HDMI output format. You'd need 4:2:2 or 4:4:4 I think?

AIUI 4:2:0 is only supported for 2160p50/59.4 modes, and isn't supported for 1080p or 2160p30 and below? (4:2:0 was added to the HDMI 2.0 specs to let HDMI 1.4 bandwidth hardware carry 2160/50p or 59.94p video, and effectively sneak into HDMI 2.0 specs without having to cope with the increased bandwidth other HDMI 2.0 modes required.)

[ROMERO91]

@wrxtasy @hdmkv Good afternoon, I'm thinking of buying one Zidoo x9s.

I need:

- auto framerate
- auto switching color range & space (for example: 2160p 4.2.0 10bit BT2020 and i'll put one movie 1080p, the system changes auto to 1080p resolution 4.2.0 8bit BT 709)

Does Zidoo x9s do it whit the last beta firmware?

  
I don't think 1080p 4:2:0 8-bit BT 709 is a valid HDMI output format. You'd need 4:2:2 or 4:4:4 I think?

AIUI 4:2:0 is only supported for 2160p50/59.4 modes, and isn't supported for 1080p or 2160p30 and below? (4:2:0 was added to the HDMI 2.0 specs to let HDMI 1.4 bandwidth hardware carry 2160/50p or 59.94p video, and effectively sneak into HDMI 2.0 specs without having to cope with the increased bandwidth other HDMI 2.0 modes required.)  

You're right. I'm sorry for the mistake. I would like to know if Zidoo makes all these changes automatically ..
But according to this user, it's work perfectly with the lastets beta firmware!
https://forum.kodi.tv/showthread.php?tid...pid2730567

[hdmkv]

Replied to you in the Zidoo thread. Answer is yes .

[riddle]

Some update after Nvidia Shield TV Oreo update? :-)

[outcave]

According to https://mrmc.tv/forum/viewtopic.php?t=41...=10#p18186 it seems that also the new Shield firmware version 7 does not supports dynamic range switching/matching.
It still depend on Android operating system.

@wrxtasy I think you can update the first post by adding also "Oreo" when you specify: Google's Android Nougat OS does not even have support for colorspace conversion/switching.

[wrxtasy]

According to https://mrmc.tv/forum/viewtopic.php?t=41...=10#p18186 it seems that also the new Shield firmware version 7 does not supports dynamic range switching/matching.
It still depend on Android operating system.

@wrxtasy I think you can update the first post by adding also "Oreo" when you specify: Google's Android Nougat OS does not even have support for colorspace conversion/switching.

When Oreo for the Shield comes out of its Preview / Beta / RC / Experience whatever testing program and is released to Joe Public

(and @wesk05) has had a chance to Bench test it !

Thx. for the Shield colorspace discussion link.

[outcave]

According to https://mrmc.tv/forum/viewtopic.php?t=41...=10#p18186 it seems that also the new Shield firmware version 7 does not supports dynamic range switching/matching.
It still depend on Android operating system.

@wrxtasy I think you can update the first post by adding also "Oreo" when you specify: Google's Android Nougat OS does not even have support for colorspace conversion/switching.

When Oreo for the Shield comes out of its Preview / Beta / RC / Experience whatever testing program and is released to Joe Public

(and @wesk05) has had a chance to Bench test it !

Thx. for the Shield colorspace discussion link. 

...but I'm still confused if in Andorid Oreo (aka 8) the colourspace switching/matching is possible.

here seems yes: https://forums.geforce.com/default/topic...6/#5262106


here seems no: https://mrmc.tv/forum/viewtopic.php?t=41...=10#p18186

[wesk05]

When Oreo for the Shield comes out of its Preview / Beta / RC / Experience whatever testing program and is released to Joe Public

(and @wesk05) has had a chance to Bench test it !  

Yep! it has to be rolled out to the public. Only then I can comment on it

[timstephens24]

...but I'm still confused if in Andorid Oreo (aka 8) the colourspace switching/matching is possible.

It's a conversion that's happening, and there's no switching. Like I said over in the MrMC forums, the conversion in Oreo is a lot better than previously, and I can't tell a difference like I could previously (especially with red). Now as to how accurate it is we'll have to wait for someone like @wesk05 and not just base it off my eyeballs, but as long as it's passing the eyeball test I'm relatively happy.

[hdmkv]

Yep! it has to be rolled out to the public. Only then I can comment on it  

Oh the suspense!

[wesk05]

Oh the suspense!  

No, there is no suspense. I don't have the Oreo update on my Shields because I have refused to sign up for the preview.

[hdmkv]

Oh right, I recall from another thread I think. Forgetting things as I age . Look forward to your assessment after public release. I signed up for nVidia's "preview program" just as they hit pause on the Oreo rollout.

[wesk05]

Is this at 2160p? Didn't think 4:2:2 10-bit was valid for that - thought 4:2:2 was 8-bit or 12-bit only at 2160p. Thought 10-bit was 4:2:0 and 4:4:4 only (the former at >30p and the latter at <=30p) 

I believe manufacturers are using 4:2:2 10-bit to indicate that the source 10-bit is not altered (10-bit + 0 padding to make it 12-bit for 4:2:2 encoding).

[noggin]

Is this at 2160p? Didn't think 4:2:2 10-bit was valid for that - thought 4:2:2 was 8-bit or 12-bit only at 2160p. Thought 10-bit was 4:2:0 and 4:4:4 only (the former at >30p and the latter at <=30p) 

I believe manufacturers are using 4:2:2 10-bit to indicate that the source 10-bit is not altered (10-bit + 0 padding to make it 12-bit for 4:2:2 encoding).  

 So are they testing for 00 LSBs on 4:2:2 12-bit sources before they report it's a 10-bit source do you think?  Or is this a source device indicating its outputting 10-bit content in 4:2:2 12-bit with the two LSBs carrying 00s rather than dither?

[wesk05]

So are they testing for 00 LSBs on 4:2:2 12-bit sources before they report it's a 10-bit source do you think?  Or is this a source device indicating its outputting 10-bit content in 4:2:2 12-bit with the two LSBs carrying 00s rather than dither? 

It's the latter, the source device is indicating that the 12-bit 4:2:2 is actually 10-bit with 0 padding.