> On Wednesday, October 29, 2014 1:33 PM, Carl Eugen Hoyos
> wrote:
> > Nicholas Robbins ffmpeg.org> writes:
>
>> Not now, but later, I would be interested in helping to
>> adapt decimate to do what we want. A detectfps filter
>> might be useful too, and would be a subset of the work.
>
Nicholas Robbins ffmpeg.org> writes:
> Not now, but later, I would be interested in helping to
> adapt decimate to do what we want. A detectfps filter
> might be useful too, and would be a subset of the work.
I believe if decimate just detects 23.9 -> 29.97 and
29.97 -> 23.9 it will fix nearl
> On Wednesday, October 29, 2014 12:25 PM, Carl Eugen Hoyos
> wrote:
> > Calvin Walton kepstin.ca> writes:
>
>> For content that was in mpeg2 with field flags set
>> appropriate for display on an interlaced TV
>
> This is unrelated to this issue:
> FFmpeg simply ignores the flag and inter
Calvin Walton kepstin.ca> writes:
> For content that was in mpeg2 with field flags set
> appropriate for display on an interlaced TV
This is unrelated to this issue:
FFmpeg simply ignores the flag and interprets the
input as progressive.
> which basically accounts for all DVD content
I live
On Sat, 2014-10-25 at 12:22 +, Carl Eugen Hoyos wrote:
> Clément Bœsch pkh.me> writes:
>
> > > +The filter only works for constant frame rate input. If your
> > > input
> > > +has mixed telecined and progressive content with changing
> > > framerate,
> > > +try the ref{pullup} filter.
> >
Clément Bœsch pkh.me> writes:
> > +The filter only works for constant frame rate input. If your input
> > +has mixed telecined and progressive content with changing framerate,
> > +try the ref{pullup} filter.
>
> Well I don't mind much but then... how is pullup making
> any difference here ac
Clément Bœsch pkh.me> writes:
> > +The filter only works for constant frame rate input. If your input
> > +has mixed telecined and progressive content with changing framerate,
> > +try the ref{pullup} filter.
>
> Well I don't mind much but then... how is pullup making
> any difference here ac
On Thu, Oct 23, 2014 at 05:58:48PM +0200, Carl Eugen Hoyos wrote:
> On Thursday 23 October 2014 10:05:07 am Clément Bœsch wrote:
> > > +The filter only works for strictly constant frame rate input. If your
> > > input +has variable frame rate, try the @ref{pullup} filter.
> > > +
> >
> > Well... is
On 23/10/14 17:06, Dave Rice wrote:
> On Oct 23, 2014, at 4:05 AM, Clément Bœsch wrote:
>> On Tue, Oct 21, 2014 at 09:32:39AM +0200, Carl Eugen Hoyos wrote:
>>> Hi!
>>>
>>> It appears to me that we all know that fieldmatch needs cfr input,
>>> but it isn't mentioned in the documentation.
>>> Rela
On Oct 23, 2014, at 4:05 AM, Clément Bœsch wrote:
> On Tue, Oct 21, 2014 at 09:32:39AM +0200, Carl Eugen Hoyos wrote:
>> Hi!
>>
>> It appears to me that we all know that fieldmatch needs cfr input,
>> but it isn't mentioned in the documentation.
>> Related to ticket #3968.
>>
>> Please comment,
On Thursday 23 October 2014 10:05:07 am Clément Bœsch wrote:
> > +The filter only works for strictly constant frame rate input. If your
> > input +has variable frame rate, try the @ref{pullup} filter.
> > +
>
> Well... isn't telecined content supposed to be CFR anyway?
Patch updated.
Thank you, C
On Tue, Oct 21, 2014 at 09:32:39AM +0200, Carl Eugen Hoyos wrote:
> Hi!
>
> It appears to me that we all know that fieldmatch needs cfr input,
> but it isn't mentioned in the documentation.
> Related to ticket #3968.
>
> Please comment, Carl Eugen
> diff --git a/doc/filters.texi b/doc/filters.t
Derek Buitenhuis gmail.com> writes:
> On 10/21/2014 8:32 AM, Carl Eugen Hoyos wrote:
> > +The filter only works for strictly constant frame rate input.
I removed "strictly" locally.
> > If your input
> > +has variable frame rate, try the ref{pullup} filter.
>
> Perhaps the filter should ou
On 10/21/2014 8:32 AM, Carl Eugen Hoyos wrote:
> +The filter only works for strictly constant frame rate input. If your input
> +has variable frame rate, try the @ref{pullup} filter.
Perhaps the filter should output a warning as well?
- Derek
___
ffmpeg
Hi!
It appears to me that we all know that fieldmatch needs cfr input,
but it isn't mentioned in the documentation.
Related to ticket #3968.
Please comment, Carl Eugen
diff --git a/doc/filters.texi b/doc/filters.texi
index c70ddf3..bc77623 100644
--- a/doc/filters.texi
+++ b/doc/filters.texi
@@
15 matches
Mail list logo
