>
> > I'll also note that the h264 encoder automatically uses multiple
> > threads already so this patch only brings vp8enc in line with it.
>
> After a quick look at x264, it seems to be using more threads than
> physiical CPUs. Is it ok too with vp8enc? I'd really like that we don't
> have that
>
> Hi,
>
> On Mon, Oct 31, 2016 at 08:49:23PM +0100, Francois Gouget wrote:
> > We run the VP8 encoder in real time mode so it uses only the minimum
> > amount of time needed to encode each frame. However by default it
> > only uses one thread so that for large/complex frames it may run at
> > l
Hi,
On Mon, Oct 31, 2016 at 08:49:23PM +0100, Francois Gouget wrote:
> We run the VP8 encoder in real time mode so it uses only the minimum
> amount of time needed to encode each frame. However by default it
> only uses one thread so that for large/complex frames it may run at
> less than the sour
We run the VP8 encoder in real time mode so it uses only the minimum
amount of time needed to encode each frame. However by default it
only uses one thread so that for large/complex frames it may run at
less than the source fps. Besides resulting in dropped frames this
blocks the main server thread
