On Tue, Aug 30, 2016 at 3:13 AM, Davinder Singh wrote:
> On Sat, Aug 27, 2016 at 6:15 PM Robert Krüger
> wrote:
>
> > [...]
> > what is the way to best contribute with test cases? I have two samples
> that
> > I use for testing, so far the results look very, very promising but there
> > are stil
On Mon, Aug 29, 2016 at 12:20 PM Clément Bœsch wrote:
> On Sun, Aug 28, 2016 at 11:31:10AM +0200, Paul B Mahol wrote:
> > On Sat, Aug 27, 2016 at 2:45 PM, Robert Krüger >
> > wrote:
> > >
> > > what is the way to best contribute with test cases? I have two samples
> that
> > > I use for testing,
On Sat, Aug 27, 2016 at 6:15 PM Robert Krüger
wrote:
> [...]
> what is the way to best contribute with test cases? I have two samples that
> I use for testing, so far the results look very, very promising but there
> are still a few artefact problems, so these could maybe serve as a good
> test c
On Sun, Aug 28, 2016 at 11:31:10AM +0200, Paul B Mahol wrote:
> On Sat, Aug 27, 2016 at 2:45 PM, Robert Krüger
> wrote:
> >
> > what is the way to best contribute with test cases? I have two samples that
> > I use for testing, so far the results look very, very promising but there
> > are still a
On Sun, Aug 28, 2016 at 11:31 AM, Paul B Mahol wrote:
> On Sat, Aug 27, 2016 at 2:45 PM, Robert Krüger
> wrote:
> >
> > what is the way to best contribute with test cases? I have two samples
> that
> > I use for testing, so far the results look very, very promising but there
> > are still a few
On Sat, Aug 27, 2016 at 2:45 PM, Robert Krüger
wrote:
>
> what is the way to best contribute with test cases? I have two samples that
> I use for testing, so far the results look very, very promising but there
> are still a few artefact problems, so these could maybe serve as a good
> test case. I
On Thu, Aug 25, 2016 at 10:28 PM, Davinder Singh
wrote:
> On Thu, Aug 25, 2016 at 5:01 AM Andy Furniss wrote:
>
> >
> >
> > I am testing with a somewhat artificial sample in that it's a framerate
> > de-interlace + scale down of a 1080i master, though it is "real" in the
> > sense that I may wan
On Thu, Aug 25, 2016 at 08:17:03PM +, Davinder Singh wrote:
> On Thu, Aug 25, 2016 at 8:03 PM Michael Niedermayer
> wrote:
>
> > [...]
> >
> > why do these not try predictors like epzs / umh ?
> > i guess some paper doesnt say exlpicitly it should be done
> > but really it should be done for
On Thu, Aug 25, 2016 at 08:17:03PM +, Davinder Singh wrote:
> On Thu, Aug 25, 2016 at 8:03 PM Michael Niedermayer
> wrote:
>
> > [...]
> >
> > why do these not try predictors like epzs / umh ?
> > i guess some paper doesnt say exlpicitly it should be done
> > but really it should be done for
On Thu, Aug 25, 2016 at 5:01 AM Andy Furniss wrote:
>
>
> I am testing with a somewhat artificial sample in that it's a framerate
> de-interlace + scale down of a 1080i master, though it is "real" in the
> sense that I may want to repair similar files where people have produced
> a juddery mess b
On Thu, Aug 25, 2016 at 8:03 PM Michael Niedermayer
wrote:
> [...]
>
> why do these not try predictors like epzs / umh ?
> i guess some paper doesnt say exlpicitly it should be done
> but really it should be done for all predictive zonal searches IMO
>
this should be in different patch. no?
yeah
On Tue, Aug 23, 2016 at 01:17:47PM +, Davinder Singh wrote:
> On Tue, Aug 23, 2016 at 5:38 AM Andy Furniss wrote:
>
> > [...]
> >
> > Nice I can see the edges are better than the last version.
> >
> > The doc/filters.texi hunk doesn't apply to git master.
> >
> > I was going to post some comp
Davinder Singh wrote:
On Tue, Aug 23, 2016 at 5:38 AM Andy Furniss
wrote:
[...]
Nice I can see the edges are better than the last version.
The doc/filters.texi hunk doesn't apply to git master.
I was going to post some comparisons with mcfps tonight, but I'll
need to redo them to see what's
On Tue, Aug 23, 2016 at 5:38 AM Andy Furniss wrote:
> [...]
>
> Nice I can see the edges are better than the last version.
>
> The doc/filters.texi hunk doesn't apply to git master.
>
> I was going to post some comparisons with mcfps tonight, but I'll need
> to redo them to see what's changed.
Davinder Singh wrote:
On Wed, Jun 1, 2016 at 4:13 AM Davinder Singh wrote:
[...]
final patch attached. please review.
this includes bug fixes and various other improvements. also added filter
docs.
Nice I can see the edges are better than the last version.
The doc/filters.texi hunk does
On Wed, Jun 1, 2016 at 4:13 AM Davinder Singh wrote:
> [...]
>
final patch attached. please review.
this includes bug fixes and various other improvements. also added filter
docs.
0001-added-motion-estimation-and-interpolation-filters-v3F.patch
Description: Binary data
___
On Sat, Aug 20, 2016 at 06:39:17PM +, Davinder Singh wrote:
> On Sat, Aug 20, 2016 at 5:45 PM Michael Niedermayer
> wrote:
>
> > how does it perform with matrixbench instead of BBB ?
> >
> > as reference 100fps matrixbench generated with mcfps
> > from https://github.com/michaelni/FFmpeg/tree
On Sat, Aug 20, 2016 at 5:45 PM Michael Niedermayer
wrote:
> how does it perform with matrixbench instead of BBB ?
>
> as reference 100fps matrixbench generated with mcfps
> from https://github.com/michaelni/FFmpeg/tree/mcfps
> ./ffmpeg -i matrixbench_mpeg2.mpg -vf 'mcfps=3:100,setpts=4*PTS'
> ou
On Fri, Aug 19, 2016 at 7:59 PM Robert Krüger
wrote:
> [...]
Impressive results, great job!
thanks :)
>
> I just tried minterpolate=fps=250:mc_mode=aobmc:me=epzs and did have some
> artefacts in one of my slowmo samples but overall the quality is very, very
> nice! If you're interested in mor
On Thu, Aug 18, 2016 at 07:26:39PM +, Davinder Singh wrote:
> On Thu, Aug 18, 2016 at 11:52 PM Paul B Mahol wrote:
>
> > [...]
> >
>
> i tried to modify EPZS. i removed the early termination threshold which
> skip some predictors :-/
> new score:
> $ tiny_psnr 60_source_2.yuv 60_bbb.yuv
> st
On Fri, Aug 19, 2016 at 4:17 PM, Paul B Mahol wrote:
> On 8/19/16, Davinder Singh wrote:
> > On Fri, Aug 19, 2016 at 3:27 AM Paul B Mahol wrote:
> >
> >> On 8/18/16, Paul B Mahol wrote:
> >> > On 8/18/16, Davinder Singh wrote:
> >> >> On Thu, Aug 18, 2016 at 11:52 PM Paul B Mahol
> wrote:
>
On 8/19/16, Davinder Singh wrote:
> On Fri, Aug 19, 2016 at 3:27 AM Paul B Mahol wrote:
>
>> On 8/18/16, Paul B Mahol wrote:
>> > On 8/18/16, Davinder Singh wrote:
>> >> On Thu, Aug 18, 2016 at 11:52 PM Paul B Mahol wrote:
>> >>
>> >>> [...]
>> >>>
>> >>
>> >> i tried to modify EPZS. i removed
On Fri, Aug 19, 2016 at 11:19:22 +, Davinder Singh wrote:
> > Same here and many other places. "!=" is a valid operator. ;)
>
> yes, that would be in case of == operator, not = operator, no?
D'uh, stupid me, I missed that. Sorry!
> will do. can you tell which is faster?
I *believe* switch/c
On Fri, Aug 19, 2016 at 3:27 AM Paul B Mahol wrote:
> On 8/18/16, Paul B Mahol wrote:
> > On 8/18/16, Davinder Singh wrote:
> >> On Thu, Aug 18, 2016 at 11:52 PM Paul B Mahol wrote:
> >>
> >>> [...]
> >>>
> >>
> >> i tried to modify EPZS. i removed the early termination threshold which
> >> sk
On Fri, Aug 19, 2016 at 1:50 AM Moritz Barsnick wrote:
> On Thu, Aug 18, 2016 at 19:26:39 +, Davinder Singh wrote:
>
> > +@table @option
> > +@item algo
> > +Set the algorithm to be used. Accepts one of the following values:
> > +
> > +@table @samp
> > +@item ebma
> > +Exhaustive block matchi
On 8/18/16, Paul B Mahol wrote:
> On 8/18/16, Davinder Singh wrote:
>> On Thu, Aug 18, 2016 at 11:52 PM Paul B Mahol wrote:
>>
>>> [...]
>>>
>>
>> i tried to modify EPZS. i removed the early termination threshold which
>> skip some predictors :-/
>> new score:
>> $ tiny_psnr 60_source_2.yuv 60_b
On 8/18/16, Davinder Singh wrote:
> On Thu, Aug 18, 2016 at 11:52 PM Paul B Mahol wrote:
>
>> [...]
>>
>
> i tried to modify EPZS. i removed the early termination threshold which
> skip some predictors :-/
> new score:
> $ tiny_psnr 60_source_2.yuv 60_bbb.yuv
> stddev: 1.02 PSNR: 47.94 MAXDIFF: 1
On Thu, Aug 18, 2016 at 19:26:39 +, Davinder Singh wrote:
> +@table @option
> +@item algo
> +Set the algorithm to be used. Accepts one of the following values:
> +
> +@table @samp
> +@item ebma
> +Exhaustive block matching algorithm.
> +@end table
> +Default value is @samp{ebma}.
[...]
> +
On Thu, Aug 18, 2016 at 11:52 PM Paul B Mahol wrote:
> [...]
>
i tried to modify EPZS. i removed the early termination threshold which
skip some predictors :-/
new score:
$ tiny_psnr 60_source_2.yuv 60_bbb.yuv
stddev: 1.02 PSNR: 47.94 MAXDIFF: 186 bytes:476928000/474163200
original epzs:
$ tiny
On 8/18/16, Davinder Singh wrote:
> On Tue, Aug 16, 2016 at 1:47 AM Paul B Mahol wrote:
>
>> [...]
>
>
> hi,
>
> made EPZS work correctly:
> https://github.com/dsmudhar/FFmpeg/commit/0fc7a5490252a7f9832775b2773b35a42025553b
> also reduced no of repeated predictors which increased the speed also.
On Tue, Aug 16, 2016 at 1:47 AM Paul B Mahol wrote:
> [...]
hi,
made EPZS work correctly:
https://github.com/dsmudhar/FFmpeg/commit/0fc7a5490252a7f9832775b2773b35a42025553b
also reduced no of repeated predictors which increased the speed also.
> What about artifacts with UMH?
> See for examp
On Tue, Aug 16, 2016 at 5:46 PM Michael Niedermayer
wrote:
> [...]
>
> not sure i suggested it previously already but you can add yourself
> to the MAINTAINERs file if you want to maintain / continue working on
> the code after GSoC
>
i surely will.
thanks
__
On Sat, Aug 13, 2016 at 12:18:56PM +, Davinder Singh wrote:
> On Thu, Aug 11, 2016 at 12:10 AM Davinder Singh wrote:
>
> > [...]
> >
> > latest changes:
> https://github.com/dsmudhar/FFmpeg/blob/dev/libavfilter/vf_minterpolate.c
> uses shared motion estimation code now, added options, improve
On Tue, Aug 16, 2016, 1:47 AM Paul B Mahol wrote:
> On 8/15/16, Davinder Singh wrote:
> > On Tue, Aug 16, 2016 at 1:40 AM Davinder Singh
> wrote:
> >
> >> On Sat, Aug 13, 2016 at 8:05 PM Paul B Mahol wrote:
> >>
> >>> [...]
> >>
> >>
> >>> Also, why is there no code for scene change detection?
On 8/15/16, Davinder Singh wrote:
> On Tue, Aug 16, 2016 at 1:40 AM Davinder Singh wrote:
>
>> On Sat, Aug 13, 2016 at 8:05 PM Paul B Mahol wrote:
>>
>>> [...]
>>
>>
>>> Also, why is there no code for scene change detection?
>>> If scene changes abruptly it will give bad frame.
>>>
>>
>> added s
On Tue, Aug 16, 2016 at 1:40 AM Davinder Singh wrote:
> On Sat, Aug 13, 2016 at 8:05 PM Paul B Mahol wrote:
>
>> [...]
>
>
>> Also, why is there no code for scene change detection?
>> If scene changes abruptly it will give bad frame.
>>
>
> added scene change detection from framerate filter:
>
>
On Sat, Aug 13, 2016 at 8:05 PM Paul B Mahol wrote:
> [...]
> Also, why is there no code for scene change detection?
> If scene changes abruptly it will give bad frame.
>
added scene change detection from framerate filter:
https://github.com/dsmudhar/FFmpeg/commit/1ad01c530569dfa1f085a31b6435597
On Sat, Aug 13, 2016 at 12:18:56PM +, Davinder Singh wrote:
> On Thu, Aug 11, 2016 at 12:10 AM Davinder Singh wrote:
>
> > [...]
> >
> > latest changes:
> https://github.com/dsmudhar/FFmpeg/blob/dev/libavfilter/vf_minterpolate.c
> uses shared motion estimation code now, added options, improve
On Sat, Aug 13, 2016 at 03:51:17PM +, Davinder Singh wrote:
> On Sat, Aug 13, 2016 at 8:05 PM Paul B Mahol wrote:
>
> > On 8/13/16, Paul B Mahol wrote:
> > > On 8/13/16, Davinder Singh wrote:
> > >>
> > >> patch attached.
> > >>
> > >
> > > Please add EPZS to minterpolate.
> > >
> >
> > Als
On Sat, Aug 13, 2016 at 8:05 PM Paul B Mahol wrote:
> On 8/13/16, Paul B Mahol wrote:
> > On 8/13/16, Davinder Singh wrote:
> >>
> >> patch attached.
> >>
> >
> > Please add EPZS to minterpolate.
> >
>
> Also, why is there no code for scene change detection?
If scene changes abruptly it will g
On Sat, Aug 13, 2016 at 7:28 PM Paul B Mahol wrote:
> On 8/13/16, Davinder Singh wrote:
> >
> > patch attached.
> >
>
> Please add EPZS to minterpolate.
>
added.
https://github.com/dsmudhar/FFmpeg/commit/1ad40c3f405625075b93dde71a749593dc64f0e3
> __
On 8/13/16, Paul B Mahol wrote:
> On 8/13/16, Davinder Singh wrote:
>>
>> patch attached.
>>
>
> Please add EPZS to minterpolate.
>
Also, why is there no code for scene change detection?
If scene changes abruptly it will give bad frame.
___
ffmpeg-deve
On 8/13/16, Davinder Singh wrote:
>
> patch attached.
>
Please add EPZS to minterpolate.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On Thu, Aug 11, 2016 at 12:10 AM Davinder Singh wrote:
> [...]
>
> latest changes:
https://github.com/dsmudhar/FFmpeg/blob/dev/libavfilter/vf_minterpolate.c
uses shared motion estimation code now, added options, improved vsbmc
i tried to make filter options as flexible as possible so that multipl
On Thu, Aug 11, 2016 at 9:09 PM Paul B Mahol wrote:
> On 8/10/16, Davinder Singh wrote:
> > On Mon, Jul 25, 2016 at 9:35 AM Davinder Singh
> wrote:
> >
> >> https://github.com/dsmudhar/FFmpeg/commits/dev
> >>
> >> The Paper 2 algorithm is complete. It seems good. If I compare Paper 2
> >> (whic
On 8/10/16, Davinder Singh wrote:
> On Mon, Jul 25, 2016 at 9:35 AM Davinder Singh wrote:
>
>> https://github.com/dsmudhar/FFmpeg/commits/dev
>>
>> The Paper 2 algorithm is complete. It seems good. If I compare Paper 2
>> (which uses bilateral motion estimation) v/s motion vectors exported by
>>
On Mon, Jul 25, 2016 at 9:35 AM Davinder Singh wrote:
> https://github.com/dsmudhar/FFmpeg/commits/dev
>
> The Paper 2 algorithm is complete. It seems good. If I compare Paper 2
> (which uses bilateral motion estimation) v/s motion vectors exported by
> mEstimate filter:
>
> $ tiny_psnr 60_source
On Wed, Jul 27, 2016 at 4:50 PM Michael Niedermayer
wrote:
> On Tue, Jul 26, 2016 at 07:30:14PM +, Davinder Singh wrote:
> > hi
> >
> > On Mon, Jul 25, 2016 at 9:55 PM Ronald S. Bultje
> wrote:
> >
> > > Hi,
> > >
> > > On Mon, Jul 25, 2016 at 5:39 AM, Michael Niedermayer
> > > > > > wrote:
On Wed, Jul 27, 2016 at 08:41:28AM -0400, Ronald S. Bultje wrote:
> Hi,
>
> On Wed, Jul 27, 2016 at 7:20 AM, Michael Niedermayer > wrote:
>
> > On Tue, Jul 26, 2016 at 07:30:14PM +, Davinder Singh wrote:
> > > hi
> > >
> > > On Mon, Jul 25, 2016 at 9:55 PM Ronald S. Bultje
> > wrote:
> > >
Hi,
On Wed, Jul 27, 2016 at 7:20 AM, Michael Niedermayer wrote:
> On Tue, Jul 26, 2016 at 07:30:14PM +, Davinder Singh wrote:
> > hi
> >
> > On Mon, Jul 25, 2016 at 9:55 PM Ronald S. Bultje
> wrote:
> >
> > > Hi,
> > >
> > > On Mon, Jul 25, 2016 at 5:39 AM, Michael Niedermayer
> > > > > >
On Tue, Jul 26, 2016 at 07:30:14PM +, Davinder Singh wrote:
> hi
>
> On Mon, Jul 25, 2016 at 9:55 PM Ronald S. Bultje wrote:
>
> > Hi,
> >
> > On Mon, Jul 25, 2016 at 5:39 AM, Michael Niedermayer
> > > > wrote:
> >
> > > On Mon, Jul 25, 2016 at 04:05:54AM +, Davinder Singh wrote:
> > >
On Wed, Jul 27, 2016 at 1:06 AM Ronald S. Bultje wrote:
> Hi,
>
> On Tue, Jul 26, 2016 at 3:30 PM, Davinder Singh
> wrote:
>
> > hi
> >
> > On Mon, Jul 25, 2016 at 9:55 PM Ronald S. Bultje
> > wrote:
> >
> > > Hi,
> > >
> > > On Mon, Jul 25, 2016 at 5:39 AM, Michael Niedermayer
> > > > > > wro
Hi,
On Tue, Jul 26, 2016 at 3:30 PM, Davinder Singh wrote:
> hi
>
> On Mon, Jul 25, 2016 at 9:55 PM Ronald S. Bultje
> wrote:
>
> > Hi,
> >
> > On Mon, Jul 25, 2016 at 5:39 AM, Michael Niedermayer
> > > > wrote:
> >
> > > On Mon, Jul 25, 2016 at 04:05:54AM +, Davinder Singh wrote:
> > > >
hi
On Mon, Jul 25, 2016 at 9:55 PM Ronald S. Bultje wrote:
> Hi,
>
> On Mon, Jul 25, 2016 at 5:39 AM, Michael Niedermayer
> > wrote:
>
> > On Mon, Jul 25, 2016 at 04:05:54AM +, Davinder Singh wrote:
> > > https://github.com/dsmudhar/FFmpeg/commits/dev
>
>
> So, correct me if I'm wrong, but
On Mon, Jul 25, 2016 at 12:25:07PM -0400, Ronald S. Bultje wrote:
> Hi,
>
> On Mon, Jul 25, 2016 at 5:39 AM, Michael Niedermayer > wrote:
>
> > On Mon, Jul 25, 2016 at 04:05:54AM +, Davinder Singh wrote:
> > > https://github.com/dsmudhar/FFmpeg/commits/dev
>
>
> So, correct me if I'm wrong
Hi,
On Mon, Jul 25, 2016 at 5:39 AM, Michael Niedermayer wrote:
> On Mon, Jul 25, 2016 at 04:05:54AM +, Davinder Singh wrote:
> > https://github.com/dsmudhar/FFmpeg/commits/dev
So, correct me if I'm wrong, but it seems the complete ME code currently
lives inside the filter. I wonder if tha
On Mon, Jul 25, 2016 at 04:05:54AM +, Davinder Singh wrote:
> https://github.com/dsmudhar/FFmpeg/commits/dev
>
> The Paper 2 algorithm is complete. It seems good. If I compare Paper 2
> (which uses bilateral motion estimation) v/s motion vectors exported by
good!
> mEstimate filter:
>
> $
https://github.com/dsmudhar/FFmpeg/commits/dev
The Paper 2 algorithm is complete. It seems good. If I compare Paper 2
(which uses bilateral motion estimation) v/s motion vectors exported by
mEstimate filter:
$ tiny_psnr 60_source_2.yuv 60_mest-esa+obmc.yuv
stddev:1.43 PSNR: 45.02 MAXDIFF: 17
On Mon, Jun 20, 2016 at 4:33 PM Michael Niedermayer
wrote:
> On Mon, Jun 20, 2016 at 09:54:15AM +, Davinder Singh wrote:
> > On Sat, Jun 18, 2016 at 3:16 AM Michael Niedermayer
>
> > wrote:
> >
> > > On Fri, Jun 17, 2016 at 08:19:00AM +, Davinder Singh wrote:
> > > [...]
> > > > Yes, I d
On Mon, Jun 20, 2016 at 09:54:15AM +, Davinder Singh wrote:
> On Sat, Jun 18, 2016 at 3:16 AM Michael Niedermayer
> wrote:
>
> > On Fri, Jun 17, 2016 at 08:19:00AM +, Davinder Singh wrote:
> > [...]
> > > Yes, I did that, after understanding it completely. It now works with the
> > > moti
On Sat, Jun 18, 2016 at 3:16 AM Michael Niedermayer
wrote:
> On Fri, Jun 17, 2016 at 08:19:00AM +, Davinder Singh wrote:
> [...]
> > Yes, I did that, after understanding it completely. It now works with the
> > motion vectors generated by mEstimate filter. Now I’m trying to improve
> it
> > b
On Fri, Jun 17, 2016 at 11:45:51PM +0200, Michael Niedermayer wrote:
> On Fri, Jun 17, 2016 at 08:19:00AM +, Davinder Singh wrote:
[...]
> Can i see your current "work in progress" ?
I found https://github.com/dsmudhar/FFmpeg, i somehow wasnt aware of
that repo even though you posted it in a p
On Fri, Jun 17, 2016 at 08:19:00AM +, Davinder Singh wrote:
> On Wed, Jun 15, 2016 at 5:04 PM Michael Niedermayer
> wrote:
>
> > Hi
> >
> > On Tue, May 31, 2016 at 10:43:38PM +, Davinder Singh wrote:
> > > There’s a lot of research done on Motion Estimation. Depending upon the
> > > inten
On Wed, Jun 15, 2016 at 5:04 PM Michael Niedermayer
wrote:
> Hi
>
> On Tue, May 31, 2016 at 10:43:38PM +, Davinder Singh wrote:
> > There’s a lot of research done on Motion Estimation. Depending upon the
> > intended application of the resultant motion vectors, the method used for
> > motion
Hi
On Tue, May 31, 2016 at 10:43:38PM +, Davinder Singh wrote:
> There’s a lot of research done on Motion Estimation. Depending upon the
> intended application of the resultant motion vectors, the method used for
> motion estimation can be very different.
>
> Classification of Motion Estimati
65 matches
Mail list logo
