Hi Vasiliy, *--vbv-init <float>* helps determining the absolute maximum frame size - http://x265.readthedocs.io/en/default/cli.html#cmdoption-vbv-init .
*--max-ausize-factor <float>* also help us control the maximum frame size - http://x265.readthedocs.io/en/default/cli.html#cmdoption-max-ausize-factor. It is actually a factor ranging from 0.5 - 1 which tells what fraction of the maximum frame size allowed in the specification for particular level should be used as maximum frame size in the encoder. Though maximum frame size varies between key frames and non key frames, this option should be helpful in your case. Thanks, Aruna On Tue, Apr 17, 2018 at 12:55 PM, Vasiliy Volkov <volk.vasi...@gmail.com> wrote: > Hi, > > Is it possible to specify maximum frame size in addition to VBV options, > somehow? So then I can be sure that libx265 ratecontroller will not use any > larger value for all frames than specified size. It's useful when working > with some "strange" devices which has small buffers and also has some side > effects if frame large enough to fulfil most of buffer space. > > _______________________________________________ > x265-devel mailing list > x265-devel@videolan.org > https://mailman.videolan.org/listinfo/x265-devel > >
_______________________________________________ x265-devel mailing list x265-devel@videolan.org https://mailman.videolan.org/listinfo/x265-devel
