[lstar337]

Plan is to make autoswitching available only when necessary. The colour space options are good but can cause problems when playing BT709 material. So we are planning to switch when necessary and only if supported; as we have now decoupled colourspace and HDR since the March update (which was a limitation on AML before).

Will this autoswitching be not only for colour spacing, but also bit depth?
Is this something that can be enabled with downgrading resolution switching as well?    

The plan is to do it for colour primary (BT709/BT2020) and bit depth.
I will start with primaries however; and add a GUI setting for this. 

  

Plan is to make autoswitching available only when necessary. The colour space options are good but can cause problems when playing BT709 material. So we are planning to switch when necessary and only if supported; as we have now decoupled colourspace and HDR since the March update (which was a limitation on AML before). 

MVC playback now works in TB or SBS. So users will get that at the least. 
We have added an option for full output, but doesn't seem to work on all displays with our testing.

Sam

 Yes - it's definitely important to be able to play SDR Rec 2020 content in Rec 2020, and not assume all Rec 2020 content is HDR10 and flag it as such.  (This will also help when playing HLG Rec 2020 HDR stuff if the S905X can't flag HLG over HDMI.  Outputting it as SDR and then manually switching your TV from SDR to HLG HDR will solve that problem, but it won't if the Rec 2020 is output flagged as Rec 709, or crudely converted to Rec 709). In other words, output the two different colour gamut formats as-is, or convert non-compatible sources if the display can't handle that colour gamut?

When it comes to bit-depth - presumably you need to have an automatic mode that choses the best based on EDID - and some manual over-rides? 

Because of the confusion inherent in the HDMI 2.0 specs (2160p 4:2:2 being 12-bit only, 4:2:0 and 4:4:4 offering 8-bit, 10-bit, 12-bit and 16-bit at different frame rates) it may be sensible to annotate the options. I can imagine lots of people thinking that selecting 4:2:2 12 bit output is 'wrong' for 10-bit content, but it is the only 4:2:2 bit-depth supported.  It may also be worth having options for <30p UHD and >30p UHD? (Or at least listing them?)    

I don't plan to parse the EDID yet; just offer some manual settings for now to cover most scenarios. As I have a better understanding of corner cases and people's setups, I expect to refine things a little more over time. The bandwidth limitations (based on frame rate) is indeed something to consider, and I suspect will cause some confusion if people think that the device is outputting the 'wrong' signal.

 

Sam, will the Vero 4K be able to learn IR signals?

My Wetek Core has just died and is probably not economical to repair so I am looking for a replacement. The Vero looks like it ticks all the right boxes.

The remote for the Wetek is quite nice and it still works so I would like to be able to use it with the Vero box if possible. I know the Vero will be fine with the wireless part as that all works with the Rpi3 build of OSMC that I am currently testing (congrats on how silky smooth that is btw), but I would like to turn the box on and off with the IR part just like the Wetek core does.

This is really just to keep it family compatible. They mostly dislike change (we have a daughter with sensory issues and autism traits), so keeping a familiar remote will help a lot.

Thanks for your time.

  The Vero 4K can learn IR signals. I believe the WeTek remotes are NEC based (use amremote); so you'd probably need to record an LIRC profile if one doesn't exist already. Vero 4K has a standby mode which can be used via the Power menu. This behaves a little differently to what you'd be used to on the WeTek, but the effects are similar.

Sam 

Thanks for your reply Sam.