A lot of people ask about these, so I thought I'd post here so I can point to this in future. Might not be suitable for everyone, but these are the settings I recommend from 2K & 4K viewing on the new Zidoo models: MAIN SETTINGS Playback/Automatic frame rate/Frame rate mode: Switch frame rate and resolution Display/HDR: Auto * Display/Color Settings/4K 50~60Hz: Priority YUV420 10BIT Display/Color Settings/4K 23~30Hz: Priority YUV444 10BIT Display/Color Settings/Non-4K: Priority YUV444 8BIT Display/Color Settings/HDMI Range: 16-235 ** Display/HDMI Mode: 3840x2160p 23Hz *** Audio/HDMI Audio: AUTO **** Audio/Downmix HD Audio output: OFF * Can be set discretely - available options are EDID dependent see below. ** This sets 64 - 940 for 10-bit content. Can be set for Auto but I prefer to set discretely *** This is my personal preference to avoid HDMI resyncs but if resyncs are not a problem and assuming auto framerate/resolution are both on, 1080p 60Hz might be a better option since the GUI/HT4 is natively 1920x1080 and text scrolls more smoothly at 60Hz. (Set this last since changing HDR mode resets HDMI Mode) **** From v6.0.90 "AUTO" works since DTS-HD is now supported correctly (RAW can still be used) OTHER SETTINGS Display/MaxCLL and MaxFALL: ON * Display/Colour Settings/Deep Colour Compatibility Mode: OFF ** * Some systems use MaxFALL/CCL, some don't. Generally leaving ON is fine because even if the system ignores it, there's no issue with the SEI message containing it. Can be useful to turn off for outboard gamma processing. ** Enables forcing of 4K50/60 4:2:0 10/12-bit even if EDID does not allow. (Some TVs can accept this signal even though EDID says it can't) If your EDID does specify 4K50/60 4:2:0 10/12-bit this setting will have no effect. If your EDID does not specify 4K50/60 4:2:0 10/12-bit and does not allow it, setting ON will cause picture loss. HDR SETTINGS FROM v6.0.50 Available settings will depend on EDID DOLBY VISION COMPATIBILITY MODE (v6.0.90 onwards) Display/Dolby vision compatible mode/<on><off> This allows displays that can process both Standard DV and LLDV to prioritise which mode is used with DV output. <ON> - Standard DV is prioritised <OFF> - LLDV is prioritised DOLBY VISION MKV COMPATIBILITY The table below shows the expected outputs for different Dolby Vision Profiles of the VS10 engine. Output of DV or LLDV is EDID dependent and all tests were made with Level 6 files (4K23) LEGAL HDMI MODES For information, below is a table detailing legal HDMI modes at 4K for both HDMI 1.4 and 2.* The numbers show the bitrate and frequency respectively (denoting bandwidth required) for each mode. Where it shows "--", it is not legal mode and therefore not supported by HDMI. HDFURY VERTEX SETTINGS FOR LLDV For those with a Vertex or similar and an HDR TV who wish to try the LLDV trick, Attached is a quick and dirty PDF to show how to set this up. This fools the Zidoo into thinking it's connected to a TV capable of LLDV but remaps the colour primaries into BT.2020 allowing it to be viewed correctly with standard HDR settings. NOTES ON POSTER DIRECTORY, BACKUP AND EXPORT Choosing a "Custom directory" local to the device is the best option, and unless you have a good reason to change, just tick the bottom option "Custom directory" and leave it in Storage:// This means the .hometheatre hidden folder is local, only one is used, and it is therefore easier for the Zidoo to access. The .hometheatre folder stores local copies of online posters, fanart and Clear Logos. If you choose to save to "Device" that confusingly means save to the "source" folders used by HT4, not the Zidoo device. In that case the .hometheatre folder is saved to the root of the "source" device, whether that's USB, NAS or PC. If you have more than one "source" then a .hometheatre folder is created in each source which gets messy. Add more Zidoo devices and it gets very very messy! It should be noted that when a backup is made, this just makes a backup of the SQL Lite database and settings and does not include the artwork - it only saves online links to TMDB image locations and over time these can change and the backup eventually becomes useless. The best way to mitigate this is to use the "Export" function in Settings/Library which exports a copy of the poster (movieName-poster.jpg) and fanart (movieName-fanart.jpg) images plus an NFO file (movieName.nfo) for each movie in the movie's folder. It should be noted that for collections, collectionName Collection-poster.jpg and collectionName Collection-fanart.jpg are not saved in this process so are scraped online (to mitigate this, I create my own files in the movies folders which are then used in a local scrape). I've reported this as a bug. Using local images means that the .hometheatre directory is not used for local images (although you will find collection posters/fanart in there if collectionName includes illegal filename characters - there's a bit of bad logic in there - again reported as a bug. This means that the source folder must be "alive" for posters to show! If you run into trouble, you can then clear the database and rescan from scratch using local images. I wouldn't use NFO parsing using NFOs produced by the box because although it works, it does not carry trailer info unless previously accessed and Cast/Crew info does not work through the database so you loose some functionality there. If you're not worried about cast/crew info and use local trailers (movieName.trailer.ext) you can use NFO import though..