On Sat, Jan 30, 2021 at 1:02 AM Mark Filipak (ffmpeg)
wrote:
> On 01/29/2021 07:10 PM, Carl Eugen Hoyos wrote:
> > Am Sa., 30. Jan. 2021 um 01:00 Uhr schrieb Mark Filipak (ffmpeg)
> > :
> >
> >> I don't know what you mean by "This does not look like the input file
> from your command line"
> >
>
Am Sa., 30. Jan. 2021 um 02:19 Uhr schrieb Mark Filipak (ffmpeg)
:
> Then you said that I should always submit the input
> (which I eventually did).
Sorry, I missed this:
Where can I find the input file?
Carl Eugen
___
ffmpeg-user mailing list
On Sat, Jan 30, 2021 at 11:46 AM Phil Rhodes via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
>
>
> On Saturday, 30 January 2021, 08:24:10 GMT, Moritz Barsnick <
> barsn...@gmx.net> wrote:
> > Please don't throw dirt around here. Carl Eugen is trying to help.
>
> I think it's worth being
On Saturday, 30 January 2021, 08:24:10 GMT, Moritz Barsnick
wrote:
> Please don't throw dirt around here. Carl Eugen is trying to help.
I think it's worth being clear that it sometimes isn't very easy to tell
whether Carl Eugen is trying to help.
P
On Fri, Jan 29, 2021 at 20:16:12 -0500, Mark Filipak (ffmpeg) wrote:
> Carl Eugen, it appears you're sniping at me. It appears you're throwing dirt
> in the air in the hope that some of it will land on me. It appears that
> you're trying to discredit me. Carl Eugen, the dirt lands on both of us.
On 01/29/2021 07:10 PM, Carl Eugen Hoyos wrote:
Am Sa., 30. Jan. 2021 um 01:00 Uhr schrieb Mark Filipak (ffmpeg)
:
I don't know what you mean by "This does not look like the input file from your
command line"
I meant that you provided the output file but you should (always) provide
the
On 01/29/2021 07:10 PM, Carl Eugen Hoyos wrote:
Am Sa., 30. Jan. 2021 um 01:00 Uhr schrieb Mark Filipak (ffmpeg)
:
I don't know what you mean by "This does not look like the input file from your
command line"
I meant that you provided the output file but you should (always) provide
the
Am Sa., 30. Jan. 2021 um 01:00 Uhr schrieb Mark Filipak (ffmpeg)
:
> I don't know what you mean by "This does not look like the input file from
> your command line"
I meant that you provided the output file but you should (always) provide
the input file. The output file is very, very rarely
On 01/29/2021 06:49 PM, Carl Eugen Hoyos wrote:
Am Sa., 30. Jan. 2021 um 00:48 Uhr schrieb Mark Filipak (ffmpeg)
:
On 01/29/2021 04:49 PM, Carl Eugen Hoyos wrote:
Am Do., 28. Jan. 2021 um 20:40 Uhr schrieb Mark Filipak (ffmpeg)
:
On 01/28/2021 02:05 AM, Carl Eugen Hoyos wrote:
Am
Am Sa., 30. Jan. 2021 um 00:48 Uhr schrieb Mark Filipak (ffmpeg)
:
>
> On 01/29/2021 04:49 PM, Carl Eugen Hoyos wrote:
> > Am Do., 28. Jan. 2021 um 20:40 Uhr schrieb Mark Filipak (ffmpeg)
> > :
> >>
> >> On 01/28/2021 02:05 AM, Carl Eugen Hoyos wrote:
> >>>
> Am 28.01.2021 um 07:26 schrieb
On 01/29/2021 04:49 PM, Carl Eugen Hoyos wrote:
Am Do., 28. Jan. 2021 um 20:40 Uhr schrieb Mark Filipak (ffmpeg)
:
On 01/28/2021 02:05 AM, Carl Eugen Hoyos wrote:
Am 28.01.2021 um 07:26 schrieb Mark Filipak (ffmpeg) :
I'm seeing problems with minterpolate that manifest as occasional visual
Am Do., 28. Jan. 2021 um 20:40 Uhr schrieb Mark Filipak (ffmpeg)
:
>
> On 01/28/2021 02:05 AM, Carl Eugen Hoyos wrote:
> >
> >> Am 28.01.2021 um 07:26 schrieb Mark Filipak (ffmpeg) :
> >>
> >> I'm seeing problems with minterpolate that manifest as occasional visual
> >> errors in particular
Hello administrators, please ban this corporate evangelist from here,
thanks.
On Fri, Jan 29, 2021 at 4:02 PM Phil Rhodes via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
> >You can technically, but minterpolate is not very user friendly - It's
> too> slow for real work and feedback, and you
>You can technically, but minterpolate is not very user friendly - It's too>
>slow for real work and feedback, and you cannot keyframe the settings on>
>different scenes very easily. It's barely usable unless you program your own>
>GUI around libavfilter
Yes - this is somewhere that
pdr0 wrote
> More settings would help too - maybe you can improve the filter. I'll post
> an example later similar to one posted by Mark, where it's "solvable"
> using
> other methods, but not using minterpolate. Minterpolate maxes out at a
> block
> size of 16, and that causes problems in that
Paul B Mahol wrote
>> The problem is ffmpeg minterpolate is s slow, and you have no usable
>> preview. Some of the other methods mentioned earlier do have previews -
>> so
>> you can tweak settings, preview, readjust etc
>>
>>
>
> Why you ignore fact that libavfilter also allows usable
--
Sent from: http://ffmpeg-users.933282.n4.nabble.com/
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject
On Fri, Jan 29, 2021 at 2:01 AM pdr0 wrote:
> Mark Filipak (ffmpeg) wrote
> > I've never heard of "optical flow errors". What could they be? (Got any
> > links to
> > explanations?)
>
> The artifacts in your video are optical flow errors :)
>
> If you've ever used it - you'd recognize these
Mark Filipak (ffmpeg) wrote
> I've never heard of "optical flow errors". What could they be? (Got any
> links to
> explanations?)
The artifacts in your video are optical flow errors :)
If you've ever used it - you'd recognize these artifacts. There are very
common
There are about a dozen
On 01/28/2021 02:55 PM, pdr0 wrote:
Mark Filipak (ffmpeg) wrote
In the video,
Look at the behavior of the dots on the gate behind the police here:
0:5.422 to 0:10.127.
Look especially at the top of roof of the building here: 0:12.012 to
0:12.179, for apparent
macroblock errors.
Here's the
Mark Filipak (ffmpeg) wrote
>
> In the video,
>
> Look at the behavior of the dots on the gate behind the police here:
> 0:5.422 to 0:10.127.
>
> Look especially at the top of roof of the building here: 0:12.012 to
> 0:12.179, for apparent
> macroblock errors.
>
> Here's the video:
>
>
On 01/28/2021 02:05 AM, Carl Eugen Hoyos wrote:
Am 28.01.2021 um 07:26 schrieb Mark Filipak (ffmpeg) :
I'm seeing problems with minterpolate that manifest as occasional visual errors
in particular areas.
Command line, complete, uncut console output and an input file missing.
Carl Eugen
> Am 28.01.2021 um 07:26 schrieb Mark Filipak (ffmpeg) :
>
> I'm seeing problems with minterpolate that manifest as occasional visual
> errors in particular areas.
Command line, complete, uncut console output and an input file missing.
Carl Eugen
I'm seeing problems with minterpolate that manifest as occasional visual errors in particular areas.
Visually, the issue looks like a math error diddling macroblocks. But there's some strangeness.
The scene is a camera pan to the right and up. The strangeness appears at the top of the frame (as
24 matches
Mail list logo