On Mon, Jul 23, 2018 at 2:33 AM Marton Balint wrote:
>
>
>
> On Tue, 17 Jul 2018, myp...@gmail.com wrote:
>
> > On Sun, Jul 15, 2018 at 1:03 AM Michael Niedermayer
> > wrote:
> >>
> >> On Sat, Jul
> >> 14, 2018 at 12:04:46PM +0200, Marton Balint wrote:
> >> >
> >> >
> >> > On Sat, 14 Jul 2018, Mi
On Tue, 17 Jul 2018, myp...@gmail.com wrote:
On Sun, Jul 15, 2018 at 1:03 AM Michael Niedermayer
wrote:
On Sat, Jul
14, 2018 at 12:04:46PM +0200, Marton Balint wrote:
>
>
> On Sat, 14 Jul 2018, Michael Niedermayer wrote:
>
> >On Fri, Jul 13, 2018 at 10:51:00AM +0200, Marton Balint wrote:
>
On Sun, Jul 15, 2018 at 1:03 AM Michael Niedermayer
wrote:
>
> On Sat, Jul
> 14, 2018 at 12:04:46PM +0200, Marton Balint wrote:
> >
> >
> > On Sat, 14 Jul 2018, Michael Niedermayer wrote:
> >
> > >On Fri, Jul 13, 2018 at 10:51:00AM +0200, Marton Balint wrote:
> > >>
> > >>
> > >>On Thu, 12 Jul 201
On Sat, Jul 14, 2018 at 12:04:46PM +0200, Marton Balint wrote:
>
>
> On Sat, 14 Jul 2018, Michael Niedermayer wrote:
>
> >On Fri, Jul 13, 2018 at 10:51:00AM +0200, Marton Balint wrote:
> >>
> >>
> >>On Thu, 12 Jul 2018, myp...@gmail.com wrote:
> >>
> >>>On Thu, Jul 12, 2018 at 12:43 AM Marton Ba
On Sat, 14 Jul 2018, Michael Niedermayer wrote:
On Fri, Jul 13, 2018 at 10:51:00AM +0200, Marton Balint wrote:
On Thu, 12 Jul 2018, myp...@gmail.com wrote:
On Thu, Jul 12, 2018 at 12:43 AM Marton Balint wrote:
On Wed, 11 Jul 2018, Jun Zhao wrote:
use pixelutils API for sad in motio
On Fri, Jul 13, 2018 at 10:51:00AM +0200, Marton Balint wrote:
>
>
> On Thu, 12 Jul 2018, myp...@gmail.com wrote:
>
> >On Thu, Jul 12, 2018 at 12:43 AM Marton Balint wrote:
> >>
> >>
> >>
> >>On Wed, 11 Jul 2018, Jun Zhao wrote:
> >>
> >>> use pixelutils API for sad in motion estimation.
> >>
>
On Thu, 12 Jul 2018, myp...@gmail.com wrote:
On Thu, Jul 12, 2018 at 12:43 AM Marton Balint wrote:
On Wed, 11 Jul 2018, Jun Zhao wrote:
> use pixelutils API for sad in motion estimation.
Does it make sense to improve this code? I thought a superior and faster
approach was a result of 20
On Thu, Jul 12, 2018 at 12:43 AM Marton Balint wrote:
>
>
>
> On Wed, 11 Jul 2018, Jun Zhao wrote:
>
> > use pixelutils API for sad in motion estimation.
>
> Does it make sense to improve this code? I thought a superior and faster
> approach was a result of 2017 GSOC task:
>
> https://docs.google.
On Wed, 11 Jul 2018, Jun Zhao wrote:
use pixelutils API for sad in motion estimation.
Does it make sense to improve this code? I thought a superior and faster
approach was a result of 2017 GSOC task:
https://docs.google.com/document/d/1Hyh_rxP1KGsVkg7i7yU8Bcv92z0LIL4r-axpoKfvMFk/edit
May
On Wed, Jul 11, 2018 at 8:31 AM Michael Niedermayer
wrote:
>
> On Wed, Jul 11, 2018 at 06:37:37AM +0800, Jun Zhao wrote:
> > use pixelutils API for sad in motion estimation.
> >
> > Signed-off-by: Jun Zhao
> > ---
> > libavfilter/motion_estimation.c | 12 +---
> > libavfilter/motion_es
On Wed, Jul 11, 2018 at 7:47 AM Carl Eugen Hoyos wrote:
>
> 2018-07-11 0:37 GMT+02:00, Jun Zhao :
> > use pixelutils API for sad in motion estimation.
>
> Some performance number make sense for the commit message imo.
>
> Carl Eugen
Will update performance number in next version, Thanks
__
On Wed, Jul 11, 2018 at 06:37:37AM +0800, Jun Zhao wrote:
> use pixelutils API for sad in motion estimation.
>
> Signed-off-by: Jun Zhao
> ---
> libavfilter/motion_estimation.c | 12 +---
> libavfilter/motion_estimation.h |2 ++
> 2 files changed, 11 insertions(+), 3 deletions(-)
>
2018-07-11 0:37 GMT+02:00, Jun Zhao :
> use pixelutils API for sad in motion estimation.
Some performance number make sense for the commit message imo.
Carl Eugen
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/f
use pixelutils API for sad in motion estimation.
Signed-off-by: Jun Zhao
---
libavfilter/motion_estimation.c | 12 +---
libavfilter/motion_estimation.h |2 ++
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/libavfilter/motion_estimation.c b/libavfilter/motion_estima
14 matches
Mail list logo
