Vimeo & YouTube HDR

Get answers to your questions about color grading, editing and finishing with DaVinci Resolve.
  • Author
  • Message
Offline
User avatar

timbutt2

  • Posts: 1554
  • Joined: Tue Nov 12, 2013 10:32 am

Vimeo & YouTube HDR

PostTue Dec 05, 2017 12:16 am

I'm looking to get some information about the Vimeo HDR guidelines and DaVinci Resolve.

https://help.vimeo.com/hc/en-us/article ... HDR-videos

During the upload process, we will detect that your video is HDR based on metadata in your source file.


There's an aspect that is a bit unclear, and what is exactly what is generating the metadata that tells Vimeo the video is HDR. I look under the current Vimeo Export Presets in DaVinci Resolve and see nothing that clearly tells you that that metadata will be exported.

This may come down to Blackmagic Design updating Resolve to include these new settings for exporting a file for Vimeo 4K HDR. The new preset would thus then export in a H.265 video file that has the HDR metadata included so that Vimeo knows.

Otherwise, I'm curious if anyone here has had experience exporting and uploading HDR video to Vimeo? What were the settings that you used?

EDIT: Presets for both Vimeo and YouTube need to be in app. Beyond that, Netflix. The Deliver Page needs to acknowledge all the deliverable formats appropriately,
"I'm well trained in the art of turning **** to gold." - Tim Buttner (timbutt2)

Cameras: URSA Mini Pro G2, URSA Mini 4.6K EF & Cinema Camera 2.5K EF
Computers: iMac 5K (Late 2015) & MacBook Pro Retina 15.4in (Mid 2018)
Offline
User avatar

timbutt2

  • Posts: 1554
  • Joined: Tue Nov 12, 2013 10:32 am

Re: Vimeo & YouTube HDR

PostWed Dec 06, 2017 5:56 am

BUMP: Due to the recent edit.

I'm asking for presets for Netflix, Vimeo, and YouTube to be in the software.
"I'm well trained in the art of turning **** to gold." - Tim Buttner (timbutt2)

Cameras: URSA Mini Pro G2, URSA Mini 4.6K EF & Cinema Camera 2.5K EF
Computers: iMac 5K (Late 2015) & MacBook Pro Retina 15.4in (Mid 2018)
Offline

Geert Geerits

  • Posts: 31
  • Joined: Tue Mar 31, 2015 6:39 am
  • Location: Belgium

Re: Vimeo & YouTube HDR

PostWed Dec 06, 2017 8:17 am

Asus X99 Pro, Intel CPU i7-5960X, 64GB DDR4
NVidia GTX 1080Ti 11GB DDR5 v.451.48, DeckLink Mini Monitor 4K,
Asus ThunderboltEX3, LaCie 12TB 2Big Dock Thunderbolt 3 Raid 0
Windows 10 Pro 1909 64bit, DaVinci Resolve Studio 16.2.3.015, Desktop Video 11.5.1
Offline
User avatar

Piotr Wozniacki

  • Posts: 1178
  • Joined: Tue Aug 02, 2016 12:17 pm
  • Location: Poland

Re: Vimeo & YouTube HDR

PostWed Dec 06, 2017 9:32 am


While we're at the article again, does anyone here who grades for HDR know a good answer to the Author's doubts on usefulness of working with "HDR mode" enabled in node(s)? I for one still do not - and simply never use it, but perhaps some good soul from BMD could address this? After all, this option has been put there for a purpose (I hope?)... Just what the purpose is, please?

Piotr
AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933 | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)
Offline

Andrew Kolakowski

  • Posts: 6583
  • Joined: Tue Sep 11, 2012 10:20 am
  • Location: Poland

Re: Vimeo & YouTube HDR

PostWed Dec 06, 2017 10:24 am

If you have project set to e.g. Rec.2100 ST048 then MP4 made with Vimeo preset will be flagged as in project setting, but only on container level (not in h264 headers). File is also 8bit which is not what you want for HDR. I would never use Vimeo presets anyway. Resolve compressed formats output are crap.

Latest Resolve does flagging (at least for some containers/formats) based on project settings. If you have color space set to Rec.2100 ST048 (or HLG) it will be properly reflected in exported eg. ProRes, DNxHR, Cineform, Uncompressed etc MOV file.
This should be enough (as minimum) for Youtube or Vimeo to detect file as HDR. This still won't have all detailed information, like mastering display info. For this you still need correctly encoded h265 or use (at least for youtube) use their tool to inject metadata into MKV container.

Based on Viemeo article they do want properly flagged 10bit files, with display mastering info, so in this case I would advice to export some 10bit intermediate file (ProRes, DNxHR, Cineform, v210 etc) and use x265 at high bitrate. Hybrid is 1 option if not you have info on BM forum how to do it with ffmpeg.
Offline
User avatar

waltervolpatto

  • Posts: 7912
  • Joined: Thu Feb 07, 2013 5:07 pm
  • Location: 1146 North Las Palmas Ave. Hollywood, California 90038 USA

Re: Vimeo & YouTube HDR

PostWed Dec 06, 2017 3:11 pm

Andrew Kolakowski wrote:If you have project set to e.g. Rec.2100 ST048 then MP4 made with Vimeo preset will be flagged as in project setting, but only on container level (not in h264 headers). File is also 8bit which is not what you want for HDR. I would never use Vimeo presets anyway. Resolve compressed formats output are crap.

Latest Resolve does flagging (at least for some containers/formats) based on project settings. If you have color space set to Rec.2100 ST048 (or HLG) it will be properly reflected in exported eg. ProRes, DNxHR, Cineform, Uncompressed etc MOV file.
This should be enough (as minimum) for Youtube or Vimeo to detect file as HDR. This still won't have all detailed information, like mastering display info. For this you still need correctly encoded h265 or use (at least for youtube) use their tool to inject metadata into MKV container.

Based on Viemeo article they do want properly flagged 10bit files, with display mastering info, so in this case I would advice to export some 10bit intermediate file (ProRes, DNxHR, Cineform, v210 etc) and use x265 at high bitrate. Hybrid is 1 option if not you have info on BM forum how to do it with ffmpeg.


The problem is that the timeline color might be another color space like Alexa and still generating a HDR: how do you flag it then?

Beyer have a checkbox in the delivery page
SuperServer 5039AD-I
C9X299-PGF - DDR4-2400 16x4 GB
i9-7920xCPU 12c 2.90GHz Water cooled
2x 1080ti DeckLink Studio 4K (11.5.1)
W10-1903 - BMR St. 16.2.2.012
nvidia: 441.66 studio
Offline

Andrew Kolakowski

  • Posts: 6583
  • Joined: Tue Sep 11, 2012 10:20 am
  • Location: Poland

Re: Vimeo & YouTube HDR

PostWed Dec 06, 2017 5:07 pm

You can only flag formats which are properly recognised by some spec and also "other" software. MOV on container level (same as h264/h265 on elementary stream level) has fixed number of possible flagging and only widely accepted formats are there. This currently includes HDR10 (ST048) and HLG. It's not about flagging any possible format out there, but those which are used as final delivery and are widely recognised.
This is also why this "simple" flagging (primaries, transfer function and matrix) is not enough and the best what you can do is to go over h265 which does also allow you to use mastering display info, which is more detailed.
Youtube "own" way of flagging MKV files is a "hack" and response to the missing widely accepted (outside h265) way of detailed flagging HDR files.
Last edited by Andrew Kolakowski on Mon May 13, 2019 9:07 am, edited 1 time in total.
Offline
User avatar

Cary Knoop

  • Posts: 1257
  • Joined: Sun Mar 12, 2017 6:35 pm
  • Location: Newark, CA USA

Re: Vimeo & YouTube HDR

PostWed Dec 06, 2017 6:09 pm

Andrew Kolakowski wrote:Based on Viemeo article they do want properly flagged 10bit files, with display mastering info, so in this case I would advice to export some 10bit intermediate file (ProRes, DNxHR, Cineform, v210 etc) and use x265 at high bitrate.

I agree, that is the most practical approach right now.
Offline

jamiegau

  • Posts: 19
  • Joined: Mon Jan 20, 2014 12:41 pm
  • Location: Melbourne, Australia

Re: Vimeo & YouTube HDR

PostMon May 13, 2019 1:41 am

NOTE:
Resolve 16 now supports rendering down to H.265 with ALSO injecting the correct MetaData into the stream so Youtube (Not sure about Vimeo) understands the HDR content.

HDR is now an easy CHECK BOX away for creating HDR content compatible with common viewing platforms.

HDR for Corporate/Wedding work is now very possible to offer clients.

See
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 7:10 am

Does this need to be in the mp4 container to work in YouTube? The reason I ask is that I uploaded a 4K HDR, rendered in .mov in beta-2 with the HDR boxes checked, to YouTube and the HDR Badge does not appear.
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera
Offline

Andrew Kolakowski

  • Posts: 6583
  • Joined: Tue Sep 11, 2012 10:20 am
  • Location: Poland

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 11:09 am

Hmmm- should work in both MP4 and MOV.
Do you have HDR TV? Try from pendrive with TV.
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 2:48 pm

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, GH5 camera, S1H camera
Offline
User avatar

Cary Knoop

  • Posts: 1257
  • Joined: Sun Mar 12, 2017 6:35 pm
  • Location: Newark, CA USA

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 3:40 pm

Your video is 8-bit, for HDR you need a 10-bit source.
Offline

Mario Kalogjera

  • Posts: 634
  • Joined: Sat Oct 31, 2015 8:44 pm

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 4:31 pm

Weird, it plays in MPC-HC with madvr in 4K HDR...

Also, even though my 4K TV is not HDR, it runs in 4K with vp9 codec in TV's YT app...stats for nerds says: smpte2084 (PQ)/bt2020

Which youtube app are you using to test it...???
Asus Prime X370-Pro, Ryzen 1600X@4GHz, 32 GB G.Skill AEGIS DDR-4 3000MHz, Asrock RX 580 8GB, Adata A400 120 GB system SSD, A2000 500 GB scratch SSD, Media storage - "Always in motion is it", Windows 10 Pro+Resolve Studio 15.3+Fusion Studio 9.0.2
Offline

Andrew Kolakowski

  • Posts: 6583
  • Joined: Tue Sep 11, 2012 10:20 am
  • Location: Poland

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 5:11 pm

Tom Watson wrote:...

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


Some of those values are wrong. Resolve gone crazy in analysis :)
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 5:31 pm

I knew the file was 8 bit. This was a test of the Resolve 16 beta 2 H.265 render with the HDR metadata boxes checked. I found no choice to enable 10 bit. Maybe that is something we need to ask Blackmagic to add.

I am still curious as to why YouTube stopped at 1080p when the upload was 4K. Earlier, I uploaded the mp4 version from the same render settings. It also stopped at 1080p. I waited over an hour now and nothing more. Either I have offended the YouTube upload Gods, or something is not right with these files. I don't know if I have some configuration setting wrong, or if the new Resolve H.265 HDR function has bugs. If others have used this successfully, then that would narrow it down to I am doing something wrong, which is usually the case. However, I have not seen any post where others have used this new function successfully.
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera
Offline
User avatar

Cary Knoop

  • Posts: 1257
  • Joined: Sun Mar 12, 2017 6:35 pm
  • Location: Newark, CA USA

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 5:35 pm

Tom Watson wrote:I knew the file was 8 bit. This was a test of the Resolve 16 beta 2 H.265 render with the HDR metadata boxes checked. I found no choice to enable 10 bit. Maybe that is something we need to ask Blackmagic to add.

Resolve Studio 16 supports 10 bit.

Tom Watson wrote:I am still curious as to why YouTube stopped at 1080p when the upload was 4K.

It depends on the (re)encoding queue, 4K may come later (sometimes even after days).
Offline

Andrew Kolakowski

  • Posts: 6583
  • Joined: Tue Sep 11, 2012 10:20 am
  • Location: Poland

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 6:05 pm

Tom Watson wrote:I knew the file was 8 bit. This was a test of the Resolve 16 beta 2 H.265 render with the HDR metadata boxes checked. I found no choice to enable 10 bit. Maybe that is something we need to ask Blackmagic to add.



You need to choose Main10 profile for 10bit. I have it in free Resolve on Mac, so I assume on PC is also there (it may depend on your GPU type).
Offline

Mario Kalogjera

  • Posts: 634
  • Joined: Sat Oct 31, 2015 8:44 pm

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 6:30 pm

Tom Watson wrote:
I am still curious as to why YouTube stopped at 1080p when the upload was 4K. Earlier, I uploaded the mp4 version from the same render settings. It also stopped at 1080p. I waited over an hour now and nothing more. Either I have offended the YouTube upload Gods, or something is not right with these files. I don't know if I have some configuration setting wrong, or if the new Resolve H.265 HDR function has bugs. If others have used this successfully, then that would narrow it down to I am doing something wrong, which is usually the case. However, I have not seen any post where others have used this new function successfully.


You may have missed my previous post. Your YT link plays in 4K and is flagged as HDR on my TV. What is unexpected is the fact that it should not do that, but it should be served the 4K SDR encode instead as is the case with all other HDR videos on YT, since the TV is SDR. Do try with the 10 bit depth, perhaps it confuses Youtube's encoding procedure.
Asus Prime X370-Pro, Ryzen 1600X@4GHz, 32 GB G.Skill AEGIS DDR-4 3000MHz, Asrock RX 580 8GB, Adata A400 120 GB system SSD, A2000 500 GB scratch SSD, Media storage - "Always in motion is it", Windows 10 Pro+Resolve Studio 15.3+Fusion Studio 9.0.2
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 8:02 pm

Thank you Andrew and Mario. I missed that Main10 choice -- I think. I'm out and about with my laptop right now, so won't be able to do the next experiment until later. The metadata from Mediainfo I posted earlier indicates the profile to be Main, not Main10. If that fixes it, great, and I will post the results of that test.

Andrew indicated that some of the luminance and light levels were wrong, so that I will need to look at. I didn't set Master display data from my calibration in the profile. I need to look to see what is in there by default or mistake. Again, I must say it is usually something I did or failed to do that is the culprit.
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera
Offline

Andrew Kolakowski

  • Posts: 6583
  • Joined: Tue Sep 11, 2012 10:20 am
  • Location: Poland

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 8:06 pm

Those 65K values are very wrong, but it may be Resolve bug or 8bit export consequence.
Why is your range set to full?
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 8:18 pm

I can't remember why the range is set to Full. I am new to this, and followed some instructions I found somewhere. Where should it be set?
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera
Offline

Andrew Kolakowski

  • Posts: 6583
  • Joined: Tue Sep 11, 2012 10:20 am
  • Location: Poland

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 8:25 pm

Keep it limited for codecs like h264/5 which are YUV based by default. In Resolve leave setting to Auto.
Offline
User avatar

Cary Knoop

  • Posts: 1257
  • Joined: Sun Mar 12, 2017 6:35 pm
  • Location: Newark, CA USA

Re: Vimeo & YouTube HDR

PostTue May 14, 2019 9:08 pm

Here is an HDR test uploaded to YouTube and generated by Resolve 16 beta.

Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 4:02 am

I made the change to main10, and re uploaded the video render to YouTube. YT converted it to BT.709, thus no HDR Badge. Here is the metadata from the YT conversion:

General
Complete name : E:\Videos\4K Video Downloader\The 3 Truck Heisler at Sawmill HDR.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/avc1/mp41)
File size : 43.8 MiB
Duration : 1 min 12 s
Overall bit rate : 5 101 kb/s
Writing application : Lavf56.40.101

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 3 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 3 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1 min 12 s
Duration_FirstFrame : -33 ms
Bit rate : 4 970 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 29.970 (29970/1000) FPS
Minimum frame rate : 29.970 FPS
Maximum frame rate : 30.030 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.080
Stream size : 42.7 MiB (97%)
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
Codec configuration box : avcC

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 1 min 12 s
Bit rate mode : Constant
Bit rate : 128 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 44.1 kHz
Frame rate : 43.066 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 1.10 MiB (3%)
Default : Yes
Alternate group : 1

Here is the metadata from the video uploaded to YT:

General
Complete name : E:\Videos\Resolve\The_3-Truck_Heisler_at_Sawmill-3.mp4
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/mp41)
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 10@L5@Main
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : hev1
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 : 10 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.081
Stream size : 173 MiB (99%)
Color range : Limited
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%)
Default : Yes
Alternate group : 1
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera
Offline
User avatar

Cary Knoop

  • Posts: 1257
  • Joined: Sun Mar 12, 2017 6:35 pm
  • Location: Newark, CA USA

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 4:15 am

Don't get the mp4 from YouTube, 4K Video Downloader does not use mp4 for the HDR verison, instead get the mkv version, the largest one.
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 4:46 am

Here is the Mediainfo from the MKV download:

General
Unique ID : 243214864409811314274606568225281665543 (0xB6F97AA19FDD4AEEB59ACAD23C3BEA07)
Complete name : C:\Users\twats\dwhelper\The 3 Truck Heisler at Sawmill HDR.mkv
Format : Matroska
Format version : Version 4
File size : 53.4 MiB
Duration : 1 min 12 s
Overall bit rate mode : Variable
Overall bit rate : 6 220 kb/s
Writing application : Lavf58.12.100
Writing library : Lavf58.12.100
ErrorDetectionType : Per level 1

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4
Format settings : CABAC / 4 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 4 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1 min 12 s
Bit rate : 5 968 kb/s
Width : 1 920 pixels
Height : 1 080 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.096
Stream size : 51.3 MiB (96%)
Writing library : x264 core 152 r2854 e9a5903
Encoding settings : cabac=1 / ref=3 / deblock=1:0:0 / analyse=0x3:0x113 / me=hex / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=34 / lookahead_threads=5 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=9999 / keyint_min=29 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=crf / mbtree=1 / crf=23.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / ip_ratio=1.40 / aq=1:1.00
Default : Yes
Forced : No

Audio
ID : 2
Format : Vorbis
Format settings, Floor : 1
Codec ID : A_VORBIS
Duration : 1 min 12 s
Bit rate mode : Variable
Bit rate : 128 kb/s
Channel(s) : 2 channels
Sampling rate : 44.1 kHz
Compression mode : Lossy
Stream size : 1.10 MiB (2%)
Writing application : Google
Language : English
Default : Yes
Forced : No
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera
Offline
User avatar

Cary Knoop

  • Posts: 1257
  • Joined: Sun Mar 12, 2017 6:35 pm
  • Location: Newark, CA USA

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 4:51 am

Can you share the YouTube link?
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 4:56 am

Oops! I shared the first try, but forgot to share this one.
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 5:00 am

What's going on with that? Try this linkl:
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera
Offline
User avatar

Cary Knoop

  • Posts: 1257
  • Joined: Sun Mar 12, 2017 6:35 pm
  • Location: Newark, CA USA

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 5:08 am

The 200.7 MB file is the HDR file.

Code: Select all
Input #0, matroska,webm, from 'The 3 Truck Heisler at Sawmill HDR.7f9a16e1-25d2-4459-ac00-89d3e1bbbf47.part':
  Metadata:
    encoder         : google/video-file
  Duration: 00:01:12.04, start: 0.000000, bitrate: 23259 kb/s
    Stream #0:0(eng): Video: vp9 (Profile 2), yuv420p10le(tv, bt2020nc/bt2020/smpte2084), 3840x2160, SAR 1:1 DAR 16:9, 29.97 fps, 29.97 tbr, 1k tbn, 1k tbc (default)
    Side data:
      Content Light Level Metadata, MaxCLL=1000, MaxFALL=400
      Mastering Display Metadata, has_primaries:1 has_luminance:1 r(0.7080,0.2920) g(0.1700,0.7970) b(0.1310 0.0460) wp(0.3127, 0.3290) min_luminance=0.000100, max_luminance=1000.000000
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 5:43 am

Cary,
Where are you finding that data?
This is what I get from Medioinfo:
General
UniqueID/String : 325850751845370213470432824226334002500 (0xF5249271153DF239B7815800FB8A4D44)
CompleteName : E:\Videos\4K Video Downloader\The 3 Truck Heisler at Sawmill HDR.mkv
Format/String : Matroska
Format_Version : Version 4
FileSize/String : 201 MiB
Duration/String : 1 min 12 s
OverallBitRate_Mode/String : Variable
OverallBitRate/String : 23.4 Mb/s
Encoded_Application/String : Lavf56.40.101
Encoded_Library/String : Lavf56.40.101

Video
ID/String : 1
Format/String : VP9
CodecID : V_VP9
Duration/String : 1 min 12 s
BitRate/String : 22.8 Mb/s
Width/String : 3 840 pixels
Height/String : 2 160 pixels
DisplayAspectRatio/String : 16:9
FrameRate_Mode/String : Variable
StreamSize/String : 196 MiB (97%)
Default/String : Yes
Forced/String : No

Audio
ID/String : 2
Format/String : Vorbis
Format_Settings_Floor : 1
CodecID : A_VORBIS
Duration/String : 1 min 12 s
BitRate_Mode/String : Variable
BitRate/String : 128 kb/s
Channel(s)/String : 2 channels
SamplingRate/String : 44.1 kHz
Compression_Mode/String : Lossy
StreamSize/String : 1.10 MiB (1%)
Encoded_Application/String : Google
Default/String : Yes
Forced/String : No
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera
Offline
User avatar

Cary Knoop

  • Posts: 1257
  • Joined: Sun Mar 12, 2017 6:35 pm
  • Location: Newark, CA USA

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 5:44 am

Mediainfo does not handle the details for VP9 very well.

I would use ffprobe (comes with ffmpeg).
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 6:05 am

Thanks Cary.
It took me 20 minutes to get all the typos out of the link to the video. I had never used ffprobe before. Learn something new here every day.

Did you try playing this video on a HDR capable device, and if so, did it play in HDR?
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera
Offline
User avatar

Cary Knoop

  • Posts: 1257
  • Joined: Sun Mar 12, 2017 6:35 pm
  • Location: Newark, CA USA

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 6:25 am

Tom Watson wrote:Thanks Cary.
It took me 20 minutes to get all the typos out of the link to the video. I had never used ffprobe before. Learn something new here every day.

Did you try playing this video on a HDR capable device, and if so, did it play in HDR?

Yes, it did.
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostThu May 16, 2019 6:36 am

Good. Thanks for the help. That seems to answer the question. Resolve 16 does provide a H.265 direct render for HDR that works on YouTube. You just need to use the correct render settings, and have the proper project settings. A lot of places to mess up. :D
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera
Offline

Michael Tiemann

  • Posts: 618
  • Joined: Fri Jul 05, 2013 11:22 am

Re: Vimeo & YouTube HDR

PostWed Apr 01, 2020 5:49 pm

Tom Watson wrote:Good. Thanks for the help. That seems to answer the question. Resolve 16 does provide a H.265 direct render for HDR that works on YouTube. You just need to use the correct render settings, and have the proper project settings. A lot of places to mess up. :D


Tom Watson, perhaps I should call you "Doctor Watson" (the partner of Sherlock Holmes) as you were somehow able to divine answer in the above rash of posts that completely eluded me. The answer was certainly not elementary.

In any case, I have learned that I should use ffprobe to see what's in my YouTube-destined files, and from what I can tell, there's just one way to feed YouTube something that will earn the HDR badge, and it's not nearly as simple as either the Resolve documentation or the YouTube documentation states.

On or around March 31st, 2020, the answer is that you need to use H.265 with the Main10 profile and a Rec 2100 color profile/gamut (either PQ or HDR). If you do these things, you don't need to explicitly "Export HDR metadata" or "Embed HDR metadata". I select Embed HDR10 Metadata because there's a 5 second clip that Peter Chamberlain referenced showing somebody ticking that box.

On the other hand, if you use H.264 (which YouTube alludes to in its HDR upload help page), then there is no Main10 profile you can access, and no matter what combination of exporting or embedding HDR metadata, nothing results in a proper yuv420p10le stream, which prevents YouTube from doing anything other than treating it like vanilla video.

I would love to be proved wrong (H.265 encodes significantly more slowly than H.264 on my machine).

P.S. I won't over-state my knowledge and claim that Resolve Studio is required. I happen to have Resolve Studio, and it happens to work for my UHD/HDR exports. If non-Studio Resolve doesn't work for you, don't complain to me!
MacOS Catalina Version 10.15.3
iMac Pro (2017)
3 GHz Intel Xeon W
64GB 2666 MHz DDR4
Radeon Pro Vega 64 16 GB
RED Rocket-X
Decklink 8K Pro card feeding FSI XM310K Monitor
Offline

Andrew Kolakowski

  • Posts: 6583
  • Joined: Tue Sep 11, 2012 10:20 am
  • Location: Poland

Re: Vimeo & YouTube HDR

PostWed Apr 01, 2020 6:05 pm

Not sure what youtube needs, but h264 can have HDR tagging.
If Resolve is unable to set them then you need to use YT MKV tool and add tags separately on MKV container level and upload final h264 MKV file. As far as I remember this is what YT likes.
Offline

Tom Watson

  • Posts: 38
  • Joined: Sat Dec 30, 2017 7:22 pm

Re: Vimeo & YouTube HDR

PostWed Apr 01, 2020 6:49 pm

Here we are almost a year later, still wondering what You Tube really wants. I don't think You Tube knows where they are going with all of this, as it appears they haven't updated any of their guidelines. The 4K stuff is now working fairly well, but now we're going to 6K and 8K.

I am successfully using H.265 with the custom settings that I have worked out. If I want to overcome some of the dumming-down that You Tube does to all videos, I use two to three times the bit rate.

When I experimented with H.264, the file sizes were just too big and took forever to upload.
Resolve Studio 16, Windows 10 Pro, i9 9940X, MSI X299 Carbon MB, EVGA RTX 2080, 128GB (4x16)Corsair Vengeance LPX DDR4 3200, GH5 camera, S1H camera

Return to DaVinci Resolve

Who is online

Users browsing this forum: Charles Bennett, Google Feedfetcher, kenshaw, Lucius Snow, Luke Holzmann and 105 guests