discussions and patches > de...@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH] Allow client to enable/disable
> > openh264 load balancing.
> >
> > On Thu, Dec 01, 2016 at 03:52:55PM -0500, Gregory J. Wolfe wrote:
> > > The libopenh264 library allows th
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> Behalf Of Michael Niedermayer
> Sent: Tuesday, December 13, 2016 2:28 PM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] A
On Thu, Dec 01, 2016 at 03:52:55PM -0500, Gregory J. Wolfe wrote:
> The libopenh264 library allows the client to enable or disable
> load balancing when running multi-threaded. When enabled, the
> slice sizes are dynamically adjusted in order to use the
> multiple threads more efficiently. Howeve
On Wed, Nov 30, 2016 at 16:44:40 +, Gregory J Wolfe wrote:
> Not sure exactly what you mean by "documentation update". Some
> comments in the code, or more verbosity than "enable/disable load
> balancing"? Please elaborate.
I was referring to doc/encoders.texi, but just noticed that
libopenh
The libopenh264 library allows the client to enable or disable
load balancing when running multi-threaded. When enabled, the
slice sizes are dynamically adjusted in order to use the
multiple threads more efficiently. However, this can also lead
to valid but slightly different results from run to
> -Original Message-
> From: ffmpeg-devel [mailto:ffmpeg-devel-boun...@ffmpeg.org] On
> Behalf Of Moritz Barsnick
> Sent: Tuesday, November 29, 2016 7:15 AM
> To: FFmpeg development discussions and patches de...@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] A
On Mon, Nov 28, 2016 at 16:29:01 -0500, Gregory J. Wolfe wrote:
> +#if OPENH264_VER_AT_LEAST(1, 6)
> +{ "load_balancing", "enable/disable load balancing",
> OFFSET(load_balancing), AV_OPT_TYPE_BOOL, { .i64 = 1 }, 0, 1, VE },
> +#endif
This could use a documentation update.
And since document
The libopenh264 library allows the client to enable or disable
load balancing when running multi-threaded. When enabled, the
slice sizes are dynamically adjusted in order to use the
multiple threads more efficiently. However, this can also lead
to valid but slightly different results from run to
