Posts: 25
Threads: 6
Joined: Jul 2015
Hi,
I hope there is a way to tweak the output metadata a bit from LRTimelapse. When I create HDR output using LRTimelapse 444 Colour Sampling and BT2020 Gamut from 14 bit D800 source images, the output movie appears to be created correctly, but when imported into Final Cut Pro it considers the clip to be Standard 709. If I open the file in Compressor 1st, it indicates it is "709† implied" but lets you override this, which I do, specifying 2020 PQ. Exporting this to a temporary file with ProRes 4444 XQ allows me to open this intermediary file in FCP as 2020. Subsequent project output to either iTunes or Vimeo via Compressor using the "Apple Devices 4K (HEVC 10-bit) as the codec" gives me true HDR output (on a LG OLED TV).
Just wondering if there is a bit of metadata missing from the FFMpeg video output in LRTimelapse that would allow for the correct Gamut?
Thanks
I hope there is a way to tweak the output metadata a bit from LRTimelapse. When I create HDR output using LRTimelapse 444 Colour Sampling and BT2020 Gamut from 14 bit D800 source images, the output movie appears to be created correctly, but when imported into Final Cut Pro it considers the clip to be Standard 709. If I open the file in Compressor 1st, it indicates it is "709† implied" but lets you override this, which I do, specifying 2020 PQ. Exporting this to a temporary file with ProRes 4444 XQ allows me to open this intermediary file in FCP as 2020. Subsequent project output to either iTunes or Vimeo via Compressor using the "Apple Devices 4K (HEVC 10-bit) as the codec" gives me true HDR output (on a LG OLED TV).
Just wondering if there is a bit of metadata missing from the FFMpeg video output in LRTimelapse that would allow for the correct Gamut?
Thanks