Transfer_characteristics=18 (arib-std-b67) HLG The syntax for the parameters is a bit complex: (all ffmpeg parameters are)įfmpeg -i WhiteChristmas.MP4 -c copy -bsf:v hevc_metadata=colour_primaries=9:transfer_characteristics=18:matrix_coefficients=9 WhiteChristmas_meta.MP4īut it makes very much sense, when You read the other documentation for YouTube HDR Adding meta data do not reencode the file, so it is way faster than transcoding to other formats. And the blog had a a reference to the ffmpeg docs and. Today I stubbled by a blog ( ) saying that the metadata could be added to a HEVC file using ffmpeg. I tried using ffmpeg to transcode to some of the supported codecs VP9 (took ages) MP4 combined with MKVMERGE but to no avail. mkv file with the meta data that You can upload to YouTube. ![]() The official google doc that can be googled :-) states that You should use some kind of metadata program called MKVMERGE to end up with a. 2020 10 bit, and yes it do not add the right metadata, as stated by DéDé, but that is fixed by the next step. I tried many different combinations again, again and again. Most of them described the workflow for the so called "Supported apps" (All the video edit big boys), not so much how You could do it without the direct support. Reading the descriptions over and over, and reading all the few resources available. Took me some days to and from to get it right (almost gave up). The more advanced design stuff I do in Affinity Designer/Photo and the animation in Blender and mix it up in the NLE. Resolve is sometimes to much of a good thing, (requiring to much time to watch endless tutorials), so the idea was also the get a more simple tool, as my workflow with a single mirrorless cam is shoot -> cut, correct, grade -> render. (Made one, error though, upgraded to a studio license first, just to figure out that most of the features I would like to have where actually in VPX).ĭid not take me to long to get the bearings around VPX, seem pretty straight forward. And as I got a previous Sony license, I was able to upgrade to VPX. Reason for getting the VPX license, is that I start regularly to hit the limits of the free version of Resolve and with the non-profit occasionally video work I do (shooting mostly stills), it simply cannot warrant a full Resolve license. Just trying to see how far I can push the quality of my log footage. But that is outside the scope of this forum, so thanks. So guess I will try some ffmpeg magic to get that HDR icon to light up. It was my oversight that YouTube actually did not support HEVC HDR but only H.264 HDR. I can confirm that the VPX HEVC output BT.2020 10bit uploads to YouTube just fine, and the grade made in VPX also looks as expected. ![]() Thanks for all Your input, happy to see that there is a such a helpful and well informed community around VPX. M Audio Axiom AIR Mini MIDI keyboard Ver 5. Memory interface 128bit Memory bandwidth 192.03GB/s 4GB of dedicated GDDR6 video memory, shared system memory 16307MB PCi Express x16 Gen3. Total 12TB of four external WD drives for backup. ![]() + x2 WD BLACK 2TB internal SATA 7,200rpm hard drives.I for internal projects 1 for Library clips/sounds/music/stills./backup of working projects. Driver version 31.0.101.2111 with 32GB of 3200MHz Corsair DDR4 ram.ġ x 250GB SSD D: drive for C: drive backup 1 x 250GB SamSung Evo 970 drive for Operating System. Intel i9900K Coffee Lake 3.6 to 5.1GHz CPU with Intel UHD 630 Graphics. Page file space 4.75GB.Īsus ROG STRIX Z390-F Gaming motherboard Rev 1.xx with Supreme FX inboard audio using the S1220A code. Direct X 12.1 latest hardware updates for Western Digital hard drives.
0 Comments
Leave a Reply. |