uskiwisean wrote:Perfect thanks! I will most likely get the 8K decklink
Great info on your other post.
Reading through your workflow, that seems specific to youtube/online delivery correct? If you were delivering an IMF or Dolby XML to a platfrom like Netflix, they would be able to read the associated files to pull the HDR and SDR information. Am I correct in thinking this? You method is used because you're actually delivering two individual files for upload in their final HDR or SDR state with no information attached?
Not quite. For YouTube I am delivering one single file, which is the HDR grade plus the SDR LUT, wrapped together. I have never delivered to Netflix, but I'm quite sure that they would want similar deliverables: a high-quality, high-resolution HDR media file with an SDR LUT that provides the appropriate trims. But how do you make the SDR LUT? DolbyVision magic gives you a great start, and it could well be that when I have a license to use more of its features, I can get the trim passes of my dreams within the DolbyVision tool. But until then, I've found I have to walk a little bit off the reservation, and grading the trim pass with LUT-compatible operations puts me in a different, SDR-only, world. If I can get a trim pass that doesn't offend without going back to the HDR grade, then I'm ready to export the LUT (which requires that I be in an HD/SDR space). If I realize that my problems are upstream, I need to return to my HDR grade and make adjustments to still hit the marks there but also to make my SDR grade easier.
I've been reading commentary that some shows on Netflix are clearly not paying close attention to the SDR versions of their content, meaning that the SDR viewing audience is seeing mistakes in the automatic translation process. That's why you want to take the care to deliver a LUT that does what YOU want.