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 10BIT *** Display/Color Settings/HDMI Range: 16-235 **** Display/Resolution: 3840x2160p 23Hz ***** Audio/HDMI Audio: AUTO ****** Audio/Downmix HD Audio output: OFF * Personal preference - Switch Frame Rate only can be used to let the Zidoo scale and reduce HDMI resyncs. (This is what I personally do) ** Can be set discretely - available options are EDID dependent see below. *** I've changed this from 8-bit to 10-bit because some 2K material is now being released in 10-bit HEVC Commercial SD/2K content is still released in 8-bit and in this case it will be padded to 10-bits with no detrimental effect. You can still choose 8-bit here if all your non-4K content is 8-bit. **** This sets 64 - 940 for 10-bit content. ***** This is my personal preference to reduce HDMI resyncs ****** I recommend "Auto" but "RAW" can be used for bitstream only as a belt and braces approach NOTE - If your display is HDMI 1.4 (300MHz, 8.9Gbps) then change the following to: Display/Color Settings/4K 50~60Hz: Priority YUV420 8BIT Display/Color Settings/4K 23~30Hz: Priority YUV422 12BIT Display/Color Settings/Non-4K: Priority YUV444 8BIT 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 **Updated May '22** Available settings will depend on TV capabilities/EDID DOLBY VISION COMPATIBILITY MODE (v6.0.90 onwards) Quick Settings/Display/Dolby vision compatible mode This allows displays that can process both Standard DV and LLDV to prioritise which mode is used with DV output. Either standard TV led DV or player led LLDV. DOLBY VISION COMPATIBILITY (v6.2.00 onwards) Since the update to v6.2.00, Dolby Vision Profile 7 (and 4) content is now playable from MEL and FEL files in multiple formats as below: STSL = Single Track, Single Layer STDL = Single Track, Dual Layer The RPU (Reference Processing Unit) is used in all cases to process dynamic tone mapping but in the case of Full Enhancement Layers, the video essence of the FEL is not used. However, to quote Dolby: "The base layer essence is a 10-bit video bitstream of the full picture element". The FEL is simply a difference signal between the 12-bit and 10-bit master and although if the base layer is mapped to 1000nits, a 4000nit signal cannot be reconstructed, no consumer displays are capable of this anyway and indeed I'm not aware of any 12-bit consumer displays at this time either. In the case of MEL presentations, all the video information is in the base layer as is obviously the case for Profiles 5 and 8. 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. Also now added a PDF describing how to view LLDV on JVC projectors without an HDFury device. 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. 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, collectionName-poster.jpg) and fanart (movieName-fanart.jpg, collectionName-fanart.jpg) images plus an NFO file (movieName.nfo) for each movie in the movie's folder. Note that the .hometheatre directory is not used for local images. If you run into trouble, you can then clear the database and rescan from scratch using local images. Be aware that if you use NFO parsing using NFOs produced by the box, these do not carry trailer info unless previously accessed and cast info does not work through the database so you loose some functionality there. At my request a switch was added to v6.3.0 to allow local trailers only which means if you want to include a movieName.trailer.ext file for your movies you can mitigate the loss of trailer functionality when using NFO files. This means that the only thing missing when using NFOs to rebuild the database is full cast info and relational links to other movies. If you're not worried about that this gives scanning complete autonomy from the vagaries of online scraping! HOW TO UNBRICK Z9X With a great many thanks to @jjm2473 (who tirelessly helped me when I completely bricked one of my boxes) below is a link to help those who have bricked their devices. https://jjm2473.github.io/nas/2021/03/01/rtd1619-unbrick.en.html TO REGISTER GOOGLE PLAY STORE (FOR "G" FIRMWARE) 1. Open Google Play Store app then Exit. 2. Goto Quick Setting>Other>About>GSF ID, Make a note of the GSF ID. 3. Goto https://www.google.com/android/uncertified log in and enter the GSF ID in the box provided 4. Click Google Play Store APP, if it is still not activated, then restart and check again. HOW TO USE LOCAL TRAILERS Local trailers should be placed in the movie folder and named like MovieName.trailer.ext or MovieName-trailer.ext I also switch on "Use Local Trailer Only" in HT4 Preferences. For example: No Time To Die.mkv (or a BDMV/ISO folder called No Time To Die) should have a trailer called: No Time To Die.trailer.mp4 or No Time To Die-trailer.mp4 (trailers tend to be mp4, but any supported video file will work just fine, eg .mkv) There are a multitude of sources for trailers around the internet, not least of which is YouTube but I use these two sites almost exclusively: https://www.traileraddict.com/ (use Chrome's "Save Video As" plugin) https://www.youtube.com/user/TrailersPlaygroundHD (use Jdownloader) If you want to use more than one trailer then number them like: No Time To Die.trailer.1.mp4 No Time To Die.trailer.2.mp4 etc.