04.08.2020, 14:09
(04.08.2020, 04:40)Selur Wrote: Since Hybrid dropped support for 'FFmpeg (NVEnc)' on Windows systems with Hybrid version '2020.06.21.1'.
Hybrid has been using NVEncC itself to add HDR metadata instead of nvhsvp since '2018.04.08.1'.
Since you didn't attach a debug output or even mention what OS you are on I can't really say much aside from that if you are on Windows and you are using NVEncC you might need to update your drivers since NVEncC or use an older NVEncC version, because starting with version 5.10:
you will need newer drivers.Add support for NVENC SDK API ver 10.0. This requires NVIDIA driver 445.87 or later.
If you are on Windows and want to use 'FFmpeg (NVEnc)' you need to stick to a Hybrid version before '2020.06.21.1', but remember I only support the latest Hybrid version.
If you are on Linux, the only ways to add HDR meta data atm. are either using nvhsp or using mkv as container and add them through container tags (Config->Output->MKV Container->Matroska advanced video signaling).
-> share more details about what you are doing and what OS you are in and I might be able to help further.
Cu Selur
Woah totally didn't see the 'add attachment' button when I made this post. I'm currently using Linux Mint 20 with the most current 450 Nvidia Drivers. I have attempted to use the 'hdr patch' option to activate nvhsp, however, i keep getting an absolute path error. I have verified that nvhsp is in the hybrid directory. When I click on the nvhsp button on the tool list to pick a different directory, nothing happens like when i click on all the other ones. Will hybrid support NEVencC under linux? I would prefer not to use the mkv advanced signaling as I've read it does not perform the same way.[attachment=958]
Also... if advanced MKV signaling is the only option - is there a way to make hybrid pull it from the source like the hdr patch option does?