Hello again Carl,
First of all, apologies for top-posting. I had read about it and *thought* I'd
avoided it last time but clearly I hadn't. Hopefully what I've done this
time will have done the trick.
I have now simplified my command and tried it with the current ffmpeg git
head. More
On 5/11/2020 10:04 AM, Bruce Roberts wrote:
Thanks for getting back to me. I have tested with "ffmpeg version
96de7bf8df Copyright (c) 2000-2017 the FFmpeg developers" which, if not the
latest version, is only a month or two old and the result is exactly the
same.
The copyright date suggests
Am Mo., 11. Mai 2020 um 19:04 Uhr schrieb Bruce Roberts :
> Thanks for getting back to me. I have tested with "ffmpeg version
> 96de7bf8df Copyright (c) 2000-2017 the FFmpeg developers" which, if not the
> latest version, is only a month or two old and the result is exactly the
> same. Do you
Hi Carl,
Thanks for getting back to me. I have tested with "ffmpeg version
96de7bf8df Copyright (c) 2000-2017 the FFmpeg developers" which, if not the
latest version, is only a month or two old and the result is exactly the
same. Do you think this issue has been resolved since then?
Best
> Am 11.05.2020 um 13:34 schrieb Bruce Roberts :
>
> ffmpeg version 3.2.4
Please test current FFmpeg git head.
Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link
Thank you in advance for your help with this problem.
I have been experimenting with the various deinterlacing options and have
found that mcdeint produces excellent results.
As the ffmpeg filters documentation explains, mcdeint "needs one field per
frame as input and must thus be used together
