On Thu, Aug 10, 2017 at 6:59 AM Michael Niedermayer
wrote:
> On Wed, Aug 09, 2017 at 07:46:30AM +0000, Davinder Singh wrote:
> > hi,
> >
> > this disables unused function amv_encode_picture() when AMV encoder is
> > disabled (and mjpeg enabled).
> > silence
decContext *avctx, AVPacket *pkt,
^
Patch attached.
Regards.
--
Davinder Singh
0001-avcodec-mjpegenc-disable-unused-code-with-AMV.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailma
On Tue, Aug 1, 2017 at 7:40 AM Davinder Singh wrote:
> [...]
>
Keeping where the code lives, aside,
main thing is API, so we need to talk about it.
--
Davinder Singh
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/m
Hi Nicolas,
On Tue, Aug 1, 2017 at 11:57 AM Nicolas George wrote:
> Le quartidi 14 thermidor, an CCXXV, Davinder Singh a écrit :
> > As we've been planning since forever (
> > https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/snow.h#L182,
> > http://ffmpeg.org/p
t of MpegEncContext. for this a lot of things need to be
moved from MpegEncContext to MotionEstContext. MpegEncContext is used at
lot of places. Please suggest your approach on this. Generic ME should
surely be seperated.
Please share your views on
On Fri, May 26, 2017 at 2:49 PM Paul B Mahol wrote:
> On 5/26/17, Michael Niedermayer wrote:
> > On Mon, May 08, 2017 at 07:40:25PM +, Davinder Singh wrote:
> >> hi,
> >>
> >> On Mon, Apr 24, 2017 at 9:43 PM Paul B Mahol wrote:
> >>
> >&g
hi,
On Mon, Apr 24, 2017 at 9:43 PM Paul B Mahol wrote:
> On 4/24/17, Davinder Singh wrote:
> > Patch attached.
> >
>
> So this encodes video frames to generate motion vectors?
>
yes. it significantly improves the frame quality. can please you test it?
the filter wil
Patch attached.
0001-minterpolate-added-codec_me_mode.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
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 Mon, Aug 29, 2016 at 8:59 PM Paul B Mahol wrote:
[...]
And using avcodec* stuff is in lavfi is not needed.
uses AVPixFmtDesc now. should I also not use libavcodec/mathops.h? median
of 3 function is shared. can it be moved?
updated patch attached.
0001-avfilter-vf_minterpolate-rename-chroma
On Sun, Aug 28, 2016 at 5:23 PM Michael Niedermayer
wrote:
> On Fri, Aug 26, 2016 at 09:34:39PM +0000, Davinder Singh wrote:
> > patch attached.
>
> > MAINTAINERS |5 +
> > 1 file changed, 5 insertions(+)
> > 51ccc94a6198acc33e77db17bf973e88f63801f5
&g
hi,
the mv can be negative. right shifting rounds off it to -ve infinity.
changed to division, doesn't seem to affect speed at all.
this fixes the green line that appear on top or left in bidir mode. also
improved the quality by +0.08dB
thanks,
DSM_
0002-avfilter-vf_minterpolate-fix-green-line
hi,
this rename confusing chroma variables to one used in AVPixFmtDescriptor.
more consistent.
also removed some useless vars from context.
thanks
DSM_
0001-avfilter-vf_minterpolate-rename-chroma-log-vars.patch
Description: Binary data
___
ffmpeg-deve
On Sat, Aug 27, 2016 at 2:26 AM Michael Niedermayer
wrote:
> On Fri, Aug 26, 2016 at 04:00:09PM -0300, James Almer wrote:
> > On 8/26/2016 3:19 PM, Michael Niedermayer wrote:
> > > IIRC, The spaces are not standard before the #
> >
> > We use them sometimes when nesting several preprocessor check
patch attached.
0001-MAINTAINER-add-myself-for-Motion-Estimation-and-Inte.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
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 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.
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: Binar
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 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
On Fri, Aug 19, 2016 at 1:50 AM Moritz Barsnick wrote:
> On Thu, Aug 18, 2016 at 19:26:39 +0000, Davinder Singh wrote:
>
> > +@table @option
> > +@item algo
> > +Set the algorithm to be used. Accepts one of the following values:
> > +
> > +@table @samp
&
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 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 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:
> >>
> >>> [...]
> >>
> &g
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 sc
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 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 fo
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/1ad40c3f40
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 possibl
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
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:
On Wed, Jul 27, 2016 at 4:50 PM Michael Niedermayer
wrote:
> On Tue, Jul 26, 2016 at 07:30:14PM +0000, Davinder Singh wrote:
> > hi
> >
> > On Mon, Jul 25, 2016 at 9:55 PM Ronald S. Bultje
> wrote:
> >
> > > Hi,
> > >
> > > On Mon, Jul 25
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,
> >
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
>
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 +0000, 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
On Sat, Jun 18, 2016 at 3:16 AM Michael Niedermayer
wrote:
> On Fri, Jun 17, 2016 at 08:19:00AM +0000, 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 tryi
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 metho
On Mon, May 30, 2016 at 1:45 PM Michael Niedermayer
wrote:
> On Mon, May 23, 2016 at 05:09:35PM +0000, Davinder Singh wrote:
> > vf_codecview.c | 55
> +--
> > 1 file changed, 45 insertion
On Thu, Jun 2, 2016 at 5:18 PM Michael Niedermayer
wrote:
> On Sun, May 22, 2016 at 01:51:05AM +0000, Davinder Singh wrote:
> [...]
>
> > vf_hwdownload.c |6 --
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> > 5eb7416fececde847414f37de9a78a4e
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 Estimation Methods:
Direct Methods: In direct methods we calculate optical flow
On Mon, May 23, 2016 at 10:15 PM Davinder Singh wrote:
> On Sun, May 15, 2016 at 1:26 AM Michael Niedermayer
> wrote:
>
>> it would be better if the previous syntax would still work, in addition
>> to any new things
>>
>> bug reports, mailing list posts, user
On Mon, May 23, 2016 at 10:35 PM Davinder Singh wrote:
> minor change:
> removed frame type condition (... || s->frame_type) from PATCH line 62 and
> 81, as specifying only frame_type won't do anything.
>
> Thanks,
> DSM_
>
in attached patch.
0001-vf_code
On Sun, May 15, 2016 at 1:26 AM Michael Niedermayer
wrote:
> it would be better if the previous syntax would still work, in addition
> to any new things
>
> bug reports, mailing list posts, user experience and scripts may
> use the old syntax
>
>
> [...]
>
>
> --
> Michael GnuPG fingerprint:
On Sun, May 22, 2016 at 2:09 AM Michael Niedermayer
wrote:
> On Sat, May 21, 2016 at 02:21:17PM +0000, Davinder Singh wrote:
> > hi,
> >
> > this patch fixes following compiler warnings:
> >
> > libavcodec/cfhd.c:346:78: warning: format specifies type 'un
2 more:
libavcodec/pngenc.c:274:25: warning: assigning to 'Bytef *' (aka 'unsigned
char *') from 'const uint8_t *' (aka 'const unsigned char *') discards
qualifiers
[-Wincompatible-pointer-types-discards-qualifiers]
s->zstream.next_in = data;
^
libavcodec
hi,
this patch fixes following compiler warnings:
libavcodec/cfhd.c:346:78: warning: format specifies type 'unsigned short'
but the argument has type 'int' [-Wformat]
av_log(avctx, AV_LOG_DEBUG, "Small chunk length %"PRIu16"
%s\n", data * 4, tag < 0 ? "optional" : "required");
On Fri, May 13, 2016 at 11:35 PM Davinder Singh wrote:
> should fix fate :)
>
*attached patch in that mail should fix fate.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
should fix fate :)
On Wed, May 11, 2016 at 6:32 PM Michael Niedermayer
wrote:
> On Wed, May 11, 2016 at 12:41:43PM +0000, Davinder Singh wrote:
> > single patch
> >
> > On Sun, May 8, 2016 at 1:18 AM Davinder Singh
> wrote:
> >
> > > separated motion
single patch
On Sun, May 8, 2016 at 1:18 AM Davinder Singh wrote:
> separated motion vector types (forward or backward) from frame picture
> types as MVs are associated with picture types only in video coding.
>
> option `mv` can have two values:
> forward predicted or bac
May 07, 2016 at 19:48:31 +0000, Davinder Singh wrote:
>
> > -{ "frames", "set frame types to display MVs of", OFFSET(frames),
> AV_OPT_TYPE_FLAGS, {.i64=3}, 0, INT_MAX, FLAGS, "frames" },
> > +{ "frames", "set frame types to
separated motion vector types (forward or backward) from frame picture
types as MVs are associated with picture types only in video coding.
option `mv` can have two values:
forward predicted or backward predicted.
option `frames` can have three values:
p-frames, i-frames and b-frames.
ex:
only f
hi,
change the confusing "source" var to "ref" of AVMotionVector.
define two constants AV_MV_REF_FRAME_PREVIOUS and AV_MV_REF_FRAME_NEXT
all changes:
https://github.com/dsmudhar/FFmpeg/commit/33b5ad805cccd7b48a6b0d643c39e8dd26f0e98b
please confirm this:
snowdec.c
Line 96: BlockNode *bn...
...
Line
vectors at for certain blocks.
DSM_
On Tue, Apr 12, 2016 at 5:44 AM Michael Niedermayer
wrote:
> On Sat, Apr 09, 2016 at 11:50:07PM +0000, Davinder Singh wrote:
> > ok, applied the changes. with new closest vector condition. will add
> > threshold now.
>
> it may be bey
here are samples:
big buck bunny: (block=16:search=16:step=2)
http://www.mediafire.com/download/iy35rcr6d66733o/output1.mp4
matrixbench: (block=16:search=7)
http://www.mediafire.com/download/ii3n9sn42bwp3sg/output_matrix.mp4
On Sun, Apr 10, 2016 at 5:20 AM Davinder Singh wrote:
> ok, appl
ok, applied the changes. with new closest vector condition. will add
threshold now.
On Sun, Apr 10, 2016 at 12:47 AM Paul B Mahol wrote:
> On 4/9/16, Davinder Singh wrote:
> > hi
> > here's the new patch.
> >
> > changes: fixed bugs, added documentation
>
hi
here's the new patch.
changes: fixed bugs, added documentation
added a step option, by default, while searching for macro-block, it moves
by 1 px in search area. this can be increased now.
uses absolute values instead of squares.
vector starts from center of macro-block, before it was at top-le
sorry about that,
here is recreated patch.
DSM_
On Sun, Apr 3, 2016 at 11:09 PM Davinder Singh wrote:
> Qualification task for Motion interpolation project.
>
> here is basic motion estimation filter which uses block matching
> technique, does full search in (default) 7 px region
Qualification task for Motion interpolation project.
here is basic motion estimation filter which uses block matching technique,
does full search in (default) 7 px region by 1px step.
Thanks,
DSM_
0001-added-motion-estimattion-filter.patch
Description: Binary data
__
63 matches
Mail list logo