Clément Bœsch u at 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 at ref{pullup} filter.
Well I don't mind much but then... how is pullup making
any difference here
On Sat, 2014-10-25 at 12:22 +, Carl Eugen Hoyos wrote:
Clément Bœsch u at 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 at ref{pullup} filter.
Well I
Calvin Walton calvin.walton at 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
On Wednesday, October 29, 2014 12:25 PM, Carl Eugen Hoyos ceho...@ag.or.at
wrote:
Calvin Walton calvin.walton at 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
Nicholas Robbins nickrobbins-at-yahoo.com at 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 -
Clément Bœsch u at 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 at ref{pullup} filter.
Well I don't mind much but then... how is pullup making
any difference here
On 23/10/14 17:06, Dave Rice wrote:
On Oct 23, 2014, at 4:05 AM, Clément Bœsch u...@pkh.me 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
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... isn't telecined
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.texi
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, Carl
On Oct 23, 2014, at 4:05 AM, Clément Bœsch u...@pkh.me 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 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
___
Derek Buitenhuis derek.buitenhuis at 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 at ref{pullup} filter.
Perhaps the filter
13 matches
Mail list logo
