On Fri, Jun 11, 2021 at 07:16:17PM +0200, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2021-06-11 17:01:20)
> > On Thu, Jun 10, 2021 at 05:49:48PM +0200, Anton Khirnov wrote:
> > > Quoting Michael Niedermayer (2021-06-01 15:02:27)
> > > > On Mon, May 31, 2021 at 09:55:11AM +0200, Anton Khirn
Quoting Michael Niedermayer (2021-06-11 17:01:20)
> On Thu, Jun 10, 2021 at 05:49:48PM +0200, Anton Khirnov wrote:
> > Quoting Michael Niedermayer (2021-06-01 15:02:27)
> > > On Mon, May 31, 2021 at 09:55:11AM +0200, Anton Khirnov wrote:
> > > > Currently existing sws_scale() accepts as input a use
On Thu, Jun 10, 2021 at 05:49:48PM +0200, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2021-06-01 15:02:27)
> > On Mon, May 31, 2021 at 09:55:11AM +0200, Anton Khirnov wrote:
> > > Currently existing sws_scale() accepts as input a user-determined slice
> > > of input data and produces an ind
Quoting Michael Niedermayer (2021-06-01 15:02:27)
> On Mon, May 31, 2021 at 09:55:11AM +0200, Anton Khirnov wrote:
> > Currently existing sws_scale() accepts as input a user-determined slice
> > of input data and produces an indeterminate number of output lines.
>
> swscale() should return the num
On Mon, May 31, 2021 at 09:55:11AM +0200, Anton Khirnov wrote:
> Currently existing sws_scale() accepts as input a user-determined slice
> of input data and produces an indeterminate number of output lines.
swscale() should return the number of lines output
it does "return dstY - lastDstY;"
> Si
Currently existing sws_scale() accepts as input a user-determined slice
of input data and produces an indeterminate number of output lines.
Since the calling code does not know the amount of output, it cannot
easily parallelize scaling by calling sws_scale() simultaneously on
different parts of the
