Re: [FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

On Thu, Jun 09, 2016 at 01:24:57PM +, Davinder Singh wrote: > On Mon, May 30, 2016 at 1:45 PM Michael Niedermayer > wrote: > > > On Mon, May 23, 2016 at 05:09:35PM +, Davinder Singh wrote: > > > vf_codecview.c | 55 > >

Re: [FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

On Mon, May 30, 2016 at 1:45 PM Michael Niedermayer wrote: > On Mon, May 23, 2016 at 05:09:35PM +, Davinder Singh wrote: > > vf_codecview.c | 55 > +-- > > 1 file changed, 45 insertions(+), 10 deletions(-) > >

Re: [FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

On Mon, May 23, 2016 at 05:09:35PM +, Davinder Singh wrote: > vf_codecview.c | 55 +-- > 1 file changed, 45 insertions(+), 10 deletions(-) > 464b23c4638d1a408e8237651facf327994945bf > 0001-vf_codecview-added-new-options.patch > From

Re: [FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

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

Re: [FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

On Fri, May 13, 2016 at 06:05:26PM +, Davinder Singh wrote: > should fix fate :) > > On Wed, May 11, 2016 at 6:32 PM Michael Niedermayer > wrote: > > > On Wed, May 11, 2016 at 12:41:43PM +, Davinder Singh wrote: > > > single patch > > > > > > On Sun, May 8, 2016

Re: [FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

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

Re: [FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

should fix fate :) On Wed, May 11, 2016 at 6:32 PM Michael Niedermayer wrote: > On Wed, May 11, 2016 at 12:41:43PM +, Davinder Singh wrote: > > single patch > > > > On Sun, May 8, 2016 at 1:18 AM Davinder Singh > wrote: > > > > > separated

Re: [FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

On Wed, May 11, 2016 at 12:41:43PM +, Davinder Singh wrote: > 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

Re: [FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

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

Re: [FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

changed default value of `frames` to zero, if `frames` option is not set, it ignore and check only direction, this way all picture types are considered if we are drawing MVs for ME, since there are more frame types available. On Sun, May 8, 2016 at 3:02 AM Moritz Barsnick

Re: [FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

On Sat, May 07, 2016 at 19:48:31 +, 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 display MVs of", OFFSET(frames), > AV_OPT_TYPE_FLAGS,

[FFmpeg-devel] [PATCH][libavfilter] codecview: improved options

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