On Sat, 21 Dec 2019 at 07:12, Philip Langdale wrote:
>
> On Fri, 20 Dec 2019 19:12:00 -0500
> Dennis Mungai wrote:
>
> > On Fri, 20 Dec 2019 at 19:03, Josh Allmann
> >
> > For CLI usage, does this affect the behavior of the global output
> > option
> >
> > -flush_packets 1
> >
> > When the NVENC
On Fri, 20 Dec 2019 19:12:00 -0500
Dennis Mungai wrote:
> On Fri, 20 Dec 2019 at 19:03, Josh Allmann
>
> For CLI usage, does this affect the behavior of the global output
> option
>
> -flush_packets 1
>
> When the NVENC encoder is in use, in any way?
It's unrelated. This is a muxer level (av
On Fri, 20 Dec 2019 at 19:03, Josh Allmann wrote:
>
> On Fri, 20 Dec 2019 at 15:36, Philip Langdale wrote:
> >
> > On 2019-11-18 17:13, Josh Allmann wrote:
> > > This patch is meant to be an entry point for discussion around an
> > > issue we are having with flushing the nvenc encoder while doing
On Fri, 20 Dec 2019 at 15:36, Philip Langdale wrote:
>
> On 2019-11-18 17:13, Josh Allmann wrote:
> > This patch is meant to be an entry point for discussion around an
> > issue we are having with flushing the nvenc encoder while doing
> > segmented transcoding. Hopefully there will be a less klud
On 2019-11-18 17:13, Josh Allmann wrote:
This patch is meant to be an entry point for discussion around an
issue we are having with flushing the nvenc encoder while doing
segmented transcoding. Hopefully there will be a less kludgey
workaround than this.
Hi Josh,
I happened to see your email r
This patch is meant to be an entry point for discussion around an
issue we are having with flushing the nvenc encoder while doing
segmented transcoding. Hopefully there will be a less kludgey
workaround than this.
First, some background some info on where this is coming from. We do
segmented trans
