![]() I don't want to bring in the tone mapping stuff if it is not necessary, it is just the best info I have bee able to find or been told on other forums for preserving HDR10 metadata. I did compile FFMpeg myself, I just didn't want to interrupt the 50 files I had in queue in handbrake, and no, if I sent colorprim, transfer, colormatrix, master-display, max-cll in handbrake (using x265 main 10) it will spit out a file with those 'HDR tags' but the colorprim/colormatrix is set to bt.709 even if I specify smpte2084 in the extra opts. If you dont want to compile ffmpeg, just use an zeranoe build, they include x265 and are publicly available. These are the relevant HDR10 metadata flags in x265 (max-cll and master-display values may differ from source to source), and you can just "extract" them by using mediainfo. I'm not sure if I understand the issue, just set the flags that matches the source in your re-encode? I dont understand why you wanna add tone map in the mix? I dont use handbreak though, but I have a hard time believing that newer versions cant handle 10bit input properly. I have been looking for an answer to this for a long time, please help point in the right direction if its not too much trouble.ĮDIT: I went ahead and compiled my own FFmpeg for windows with all the extra's and it 'seems' to conserve the HDR10 tags on UHD video but I would still like to hear from community members as to what you do personally to conserve HDR10 metadata in a UHD HDR10 video taken, like I said, for instance, from my Samsung Note10 . It's still 10-bit BT.2020 SMPTE ST 2086 HDR10 'compatible' but the HDR10 metadata is gone. I can't even get the HDR10 metadata conserved on personal video shot with my Samsung Note10 , if I try to re-encode in anyway the HDR10 info is gone. If not can someone either point me to a thread that goes through how to extract the HDR10 metadata from a UHD file and then re-encode the base video and tone map? The person that posted the info I found on redfox.bz was evidently made into a video that was over 2 hours long to explain the workflow but the video is no longer available and the author stopped replying over 2 years ago now. Using HEVC 10-bit main 10 encoder, I am told this has something to do with the handbrake workflow being only 8-bit at some point therefore it is not able to properly conserve HDR10 metadata.Ĭan anyone give me any advice on whether the FFmpeg script above will conserve HDR10 metadata (I know the script is just video, I can easily mux together the audio after the video encodes) before I try it for myself? I am aware of the autobuild that was put together for this purpose so I am looking into that but supposedly handbrake is not able to conserve HDR10 data even with the extra settings of: My.TrueHD.7.1.Atmos.mkvīut I have to compile a FFmpeg myself for windows so that it includes libx265 (I can definitely do this, I just don't want to stop the encoding jobs I have going to try this out right this moment) and all the extras. metadata:s:t:0 filename="" -metadata:s:t:0 mimetype="image/jpeg" \ map 0:0 -metadata:s:v:0 language=eng -metadata:s:v:0 title="My Awesome Movie (2019)" \ metadata title="My Awesome Movie (2019)" \ i "./storage/My.Source.TrueHD.7.1.Atmos.mkv" \ ![]() There is also a person that claims that they get HDR10 conserved by using this FFmpeg script/code: ![]() The most certain answer I have found is to take the original UHD and transcode to DNxHR then use 3DLut plugin through davinci resolve 15/16 to create a tone map and then use davinci resolve 15/16 to combine the tone map with the original video stream and export again as DNxHR (which is HUGE, like 700GB huge, so we are talking 1.4 TB just for the middle workflow) and then finally encoding that DNxHR file into HEVC 10-bit HDR10. I have been trying to learn how to conserve HDR10 metadata that a film/file already has on it but I haven't found a good answer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |