View Single Post
Old 25th January 2021, 02:48   #2251  |  Link
creeve4
Registered User
 
Join Date: Mar 2013
Posts: 15
Quote:
Originally Posted by JKyle View Post
This issue was raised right after the default setting for x265 encoding of vpy was changed from vspipe to direct reading without piping.
See this issue thread.

You can solve this problem in two ways.

1) Select vspipe for Pipe in Input/Output section of x265 Options window.

or

2) get @DJATOM's new x265 build that is believed to have fixed this memory leak issue, and replace the current one with this new build. You need some more testing in this case.
Thank you so much!
creeve4 is offline