I think I got the main issue fixed, but I noticed, that this probably will create async output since NVEncC doesn't allow enforcing key frames at specific frame numbers so in case the chapter point isn't on a key frame output will be async.
(added a feature request to the bug tracker of NVEncC, see: https://github.com/rigaya/NVEnc/issues/73)
-> will send you a dev version for testing, if the output is async try x265 instead of NVEnc
Cu Selur
(added a feature request to the bug tracker of NVEncC, see: https://github.com/rigaya/NVEnc/issues/73)
-> will send you a dev version for testing, if the output is async try x265 instead of NVEnc
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.