I have the Samsung UN55HU8550 4K TV with the SEK-3500U expansion kit. This set, for lack of a better description, only displays "HDR light." Not nearly as many nits as the newer sets. It also does not feature an HDR Badge when playing HDR content, even from UHD BD discs with HDR, but it does display the HDR to its capability. I have played the mov file I created on this set and it looks like HDR.
I have two 32" LG monitors side by side at this work station. One is HDR the other is not. Both are calibrated. When playing the mov file with the player split between the two monitors, I can see the dramatic difference between HDR and SDR. I can also add the TV as a third monitor, and have the video playing in all three. The TV and HDR monitor then play in HDR, and look good, but this is from a file that has not yet been mangled by YouTube.
I also rendered the same video in mp4 with Resolve 16, with the only difference in settings being the mp4 choice. It also plays fine on the HDR monitor and TV, and looks the same as the mov version.
In comparing the Mediainfo date between the two files, I only see two differences: The mov file shows "Codec ID: qt 0000.02 (qt)" where the mp4 file shows: "Codec ID: isom (isom/iso2/mp41)". The other difference is the mov metadata lists "Language:English" the mp4 file metadata doesn't list this attribute. I don't see how any of the differences in metadata would cause the HDR Badge to not trigger on YouTube since all of the other metadata is identical. Here's the data:
General
Complete name : E:\Videos\Resolve\The_3-Truck_Heisler_at_Sawmill.mov
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 0000.02 (qt )
File size : 175 MiB
Duration : 1 min 12 s
Overall bit rate : 20.4 Mb/s
Writing application : Lavf57.25.100
Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main@L5@Main
HDR format : SMPTE ST 2086
Codec ID : hvc1
Codec ID/Info : High Efficiency Video Coding
Duration : 1 min 12 s
Bit rate : 20.2 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 29.970 (30000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.081
Stream size : 174 MiB (99%)
Language : English
Color range : Full
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : BT.2020
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 1000 cd/m2
MaxCLL_Original : 65535 cd/m2
Maximum Frame-Average Light Level : 400 cd/m2
MaxFALL_Original : 65535 cd/m2
SEI_rbsp_stop_one_bit : Missing
Codec configuration box : hvcC
Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 1 min 12 s
Duration_LastFrame : -4 ms
Bit rate mode : Constant
Bit rate : 192 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 1.66 MiB (1%)
Language : English
Default : Yes
Alternate group : 1
Other
ID : 3
Type : Time code
Format : QuickTime TC
Duration : 1 min 12 s
Time code of first frame : 01:00:00:00
Time code, striped : Yes
Language : English
Default : No
Due to a really slow Internet connection at home, I have not uploaded the mp4 file to YouTube -yet.
I will do that later today from a place with a fiber connection. That will be the ultimate test between the two formats.
Here is the link to the mov file on YouTube:
The other interesting thing with this upload is that is was a 4K file that was uploaded as can be seen in the metadata, but YouTube only processed it as 1080p. This has never been a problem with non HDR uploads from Resolve renders in mov in the past.
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, Decklink mini 4K GH5 camera, S1H camera