View Single Post
Old 1st July 2020, 13:16   #29544  |  Link
jdobbs
Moderator
 
Join Date: Oct 2001
Posts: 20,973
Just a head's up. I tested the new version of NVENCC yesterday, and the new option to include headers results an encoding failure with a "Cannot allocate memory" message. Removing the new option from the command line makes the encoding error goes away. But, then, of course you're back to having the FF/REW/CHAP issues. I posted an issue report on GITHUB. It appears that the new option creates a memory leak (as can be observed by watching the process under the Windows 10 task manager). On the 32 bit version of NCENCC it hits the memory limitation pretty quickly (you have to use the 32 bit version to remain compatible with AVISYNTH 2.60 -- which must be used under certain circumstances).

So the options right now are to wait and see if it gets another quick fix, or to go ahead and implement the code that adds the headers within BD-RB. I'd prefer the first option, as that's a cleaner way to go. So I'm going to wait for a bit and see what happens.
__________________
Help with development of new apps: Donations.
Website: www.jdobbs.net

Last edited by jdobbs; 1st July 2020 at 13:57.
jdobbs is offline   Reply With Quote