On 02/01/2021 11:03 AM, Paul B Mahol wrote:
People your age enjoy their life. You should too. Why you want to dealt
with digital video...
I enjoy it.
--
Someone's sneaking in and turning up the range so that my food burns.
I'm sure of it.
And the older I get, the more sure of it I become.
___
On Mon, Feb 1, 2021 at 3:49 AM Mark Filipak (ffmpeg)
wrote:
> Developers, kindly pay attention to this post...
>
> On 01/31/2021 10:24 AM, Phil Rhodes via ffmpeg-user wrote:
> > On Sunday, 31 January 2021, 13:24:39 GMT, Rodney Baker <
> rodney.ba...@iinet.net.au> wrote:
> >
> >> See man ffmpeg
Developers, kindly pay attention to this post...
On 01/31/2021 10:24 AM, Phil Rhodes via ffmpeg-user wrote:
On Sunday, 31 January 2021, 13:24:39 GMT, Rodney Baker
wrote:
See man ffmpeg for detailed description of the options... > try typing "man ffmpeg" into a google
search and see what
On Sunday, 31 January 2021, 13:24:39 GMT, Rodney Baker
wrote:
> See man ffmpeg for detailed description of the options... > try typing "man
> ffmpeg" into a google search and see what comes up... >
> http://manpages.org/ffmpeg...> Look for the section titled "Generic Options".
> > There you
On Friday, 29 January 2021 20:09:54 ACDT Mark Filipak (ffmpeg) wrote:
> On 01/29/2021 04:23 AM, Moritz Barsnick wrote:
> > On Wed, Jan 27, 2021 at 14:16:16 +, Phil Rhodes via ffmpeg-user wrote:
> >> > I didn't know I could get help on individual filters.
> >>
> >> To be completely fair, that
On Friday, 29 January 2021 21:12:06 ACDT Phil Rhodes via ffmpeg-user wrote:
> On Friday, 29 January 2021, 09:43:09 GMT, Mark Filipak (ffmpeg)
wrote:
> > Try 'ffmpeg -h type=filter.
> > It fails. Why? Because "filter" is a "type", not a "name" -- never mind
> > that the details says "... named
On Friday, 29 January 2021, 09:43:09 GMT, Mark Filipak (ffmpeg)
wrote:
> Try 'ffmpeg -h type=filter.
> It fails. Why? Because "filter" is a "type", not a "name" -- never mind that
> the details says "...
> named decoder/encoder ..."
Yes, this is the sort of thing that causes the proble
On 01/29/2021 04:23 AM, Moritz Barsnick wrote:
On Wed, Jan 27, 2021 at 14:16:16 +, Phil Rhodes via ffmpeg-user wrote:
> I didn't know I could get help on individual filters.
To be completely fair, that is actually in the docs, but it's not exactly on
the front page.
Good point.
It is a
On Wed, Jan 27, 2021 at 14:16:16 +, Phil Rhodes via ffmpeg-user wrote:
> > I didn't know I could get help on individual filters.
> To be completely fair, that is actually in the docs, but it's not exactly on
> the front page.
Good point.
It is at the very top of the output of "ffmpeg -h" t
On 01/27/2021 03:16 AM, list+ffmpeg-u...@jdlh.com wrote:
This is the part of the minterpolate video filter which defines the options:
https://github.com/FFmpeg/FFmpeg/blob/master/libavfilter/vf_minterpolate.c#L205-L235
[The following looks better in a fixed-pitch font.]
static const AVOption mi
On Thu, Jan 28, 2021 at 7:04 AM Mark Filipak (ffmpeg)
wrote:
> On 01/27/2021 05:47 PM, Carl Eugen Hoyos wrote:
> > Am Mi., 27. Jan. 2021 um 02:03 Uhr schrieb Mark Filipak (ffmpeg)
> > :
> >
> >> ffmpeg -i SOURCE -map 0 -filter_complex "split[1][2], \
> >> [1]telecine=pattern=55, select=not(eq(mod
On 01/27/2021 05:47 PM, Carl Eugen Hoyos wrote:
Am Mi., 27. Jan. 2021 um 02:03 Uhr schrieb Mark Filipak (ffmpeg)
:
ffmpeg -i SOURCE -map 0 -filter_complex "split[1][2], \
[1]telecine=pattern=55, select=not(eq(mod(n\,5)\,2))[3], \
[2]minterpolate=fps=6/1001:mi_mode=mci=mc_mode=obmc:scd=fdiff
Am Mi., 27. Jan. 2021 um 02:03 Uhr schrieb Mark Filipak (ffmpeg)
:
> ffmpeg -i SOURCE -map 0 -filter_complex "split[1][2], \
> [1]telecine=pattern=55, select=not(eq(mod(n\,5)\,2))[3], \
> [2]minterpolate=fps=6/1001:mi_mode=mci=mc_mode=obmc:scd=fdiff:scd_threshold=10,
> \
> select=eq(mod(n\,5)
> I didn't know I could get help on individual filters.
To be completely fair, that is actually in the docs, but it's not exactly on
the front page.
P
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
On 01/27/2021 05:31 AM, Paul B Mahol wrote:
On Wed, Jan 27, 2021 at 6:03 AM Mark Filipak (ffmpeg)
wrote:
I ask this because I think it can only be answered by looking at the
source code. I'm not competent
to do that.
Your thinking is invalid.
What part?
Is 'mi_mode=dup' or 'mi_mode=blend
On Wednesday, 27 January 2021, 10:31:35 GMT, Paul B Mahol
wrote:
> ffmpeg -h filter=minterpolate
Y'know, I've been using ffmpeg for a really long time, and I had no idea you
could do that.
P
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.o
On Wed, Jan 27, 2021 at 6:03 AM Mark Filipak (ffmpeg)
wrote:
> I ask this because I think it can only be answered by looking at the
> source code. I'm not competent
> to do that.
>
Your thinking is invalid.
>
> Is 'mi_mode=dup' or 'mi_mode=blend' or 'mi_mode=mci' the default?
>
ffmpeg -h fil
On 2021-01-26 20:05, Mark Filipak (ffmpeg) wrote:
On 01/26/2021 09:49 PM, pdr0 wrote:
Jim DeLaHunt-2 wrote
Perhaps the character between 'mci' and 'mc_mode' should be ':' instead
of '='?
That works for me
-vf
minterpolate=fps=6/1001:mi_mode=mci:mc_mode=obmc:scd=fdiff:scd_threshold=10
I ask this because I think it can only be answered by looking at the source code. I'm not competent
to do that.
Is 'mi_mode=dup' or 'mi_mode=blend' or 'mi_mode=mci' the default?
On 01/26/2021 09:49 PM, pdr0 wrote:
Jim DeLaHunt-2 wrote
Perhaps the character between 'mci' and 'mc_mode' should
On 01/26/2021 09:49 PM, pdr0 wrote:
Jim DeLaHunt-2 wrote
Perhaps the character between 'mci' and 'mc_mode' should be ':' instead
of '='?
That works for me
-vf
minterpolate=fps=6/1001:mi_mode=mci:mc_mode=obmc:scd=fdiff:scd_threshold=10
Each one is a separate option and argument
https://g
Jim DeLaHunt-2 wrote
> Perhaps the character between 'mci' and 'mc_mode' should be ':' instead
> of '='?
That works for me
-vf
minterpolate=fps=6/1001:mi_mode=mci:mc_mode=obmc:scd=fdiff:scd_threshold=10
Each one is a separate option and argument
https://github.com/FFmpeg/FFmpeg/blob/master
On 01/26/2021 08:39 PM, Jim DeLaHunt wrote:
On 2021-01-26 16:59, Mark Filipak (ffmpeg) wrote:
Note error at the end of the report.
I suspect the problem is that 'fps=6/1001:mi_mode=mci=mc_mode=obmc:scd=fdiff:scd_threshold=10'
needs some sort of internal delimiters, but I can't figure out w
On 01/26/2021 08:31 PM, Jim DeLaHunt wrote:
On 2021-01-26 16:59, Mark Filipak (ffmpeg) wrote:
Note error at the end of the report.
I suspect the problem is that 'fps=6/1001:mi_mode=mci=mc_mode=obmc:scd=fdiff:scd_threshold=10'
needs some sort of internal delimiters, but I can't figure out w
On 2021-01-26 16:59, Mark Filipak (ffmpeg) wrote:
Note error at the end of the report.
I suspect the problem is that
'fps=6/1001:mi_mode=mci=mc_mode=obmc:scd=fdiff:scd_threshold=10'
needs some sort of internal delimiters, but I can't figure out what
they would be.
ffmpeg -i SOURCE -map
On 2021-01-26 16:59, Mark Filipak (ffmpeg) wrote:
Note error at the end of the report.
I suspect the problem is that
'fps=6/1001:mi_mode=mci=mc_mode=obmc:scd=fdiff:scd_threshold=10'
needs some sort of internal delimiters, but I can't figure out what
they would be.
ffmpeg -i SOURCE -map
Note error at the end of the report.
I suspect the problem is that 'fps=6/1001:mi_mode=mci=mc_mode=obmc:scd=fdiff:scd_threshold=10'
needs some sort of internal delimiters, but I can't figure out what they would be.
ffmpeg -i SOURCE -map 0 -filter_complex "split[1][2], \
[1]telecine=pattern=
26 matches
Mail list logo
