On Sun, Mar 3, 2019 at 11:31 PM Derek Buitenhuis
wrote:
>
> On 23/02/2019 00:35, Jan Ekström wrote:
> > This way values such as maxrate/bufsize can be utilized
> > further down the chain.
> > ---
> > libavcodec/libx265.c | 8
> > 1 file changed, 8 insertions(+)
>
> OK.
>
> - Derek
Thank
On 23/02/2019 00:35, Jan Ekström wrote:
> This way values such as maxrate/bufsize can be utilized
> further down the chain.
> ---
> libavcodec/libx265.c | 8
> 1 file changed, 8 insertions(+)
OK.
- Derek
___
ffmpeg-devel mailing list
ffmpeg-de
On Sat, Feb 23, 2019 at 2:35 AM Jan Ekström wrote:
>
> This way values such as maxrate/bufsize can be utilized
> further down the chain.
> ---
Ping.
This is similar to what the libx264 and libvpx wrappers do, and
enables modules such as hlsenc, movenc and mpegenc in libavformat
utilize the rate
This way values such as maxrate/bufsize can be utilized
further down the chain.
---
libavcodec/libx265.c | 8
1 file changed, 8 insertions(+)
diff --git a/libavcodec/libx265.c b/libavcodec/libx265.c
index 98415366da..fe39f45241 100644
--- a/libavcodec/libx265.c
+++ b/libavcodec/libx265.c
