On 11/15/2020 9:41 AM, Tom Worster wrote:
What can I do to prevent this and get ffmpeg to write files with the
atclocktime? instead of what I assume is the actual time when the file is
written.
Depending on the actual implementation, you might not be able to- it's
common to write into a tem
I'm using ffmpeg to connect to an icecast server and save its AAC audio
stream to m4a files each 5 minutes long.
Occasionally, about 1 in 15 or 20 files, the name of the file has
timestamp one second after the desired atclocktime, like
name-20201115T144500Z.m4a
name-20201115T145000Z.m4a
name-
> yadif and bwdif were set to output one frame for each field. I found bwdif
> somewhat better than yadif which leaves some minor "ripple" artifacts to the
> movie.
Thanks for the comparison advice, I will take a look at the bwdif filter.
___
ffmpeg-u
Am So., 15. Nov. 2020 um 14:36 Uhr schrieb Matti Haveri
:
> BTW, I guess I could skip scaling and set the output .mp4 pixel aspect
> ratio the same as in the input PAL .dv 128/117 but I prefer to convert to
> square pixels.
You should simply not set it.
Carl Eugen
___
On Sun, Nov 15, 2020 at 2:00 PM adam smith via ffmpeg-user <
ffmpeg-user@ffmpeg.org> wrote:
>> 25fps vs 50fps difference is there but not so great as I expected.
> You might find that ffmpeg is duplicating each deinterlaced frame to
> output 50fps from the 25fps source.
Most of the footage was int
25fps vs 50fps difference is there but not so great as I expected.
You might find that ffmpeg is duplicating each deinterlaced frame to output
50fps from the 25fps source. If you use yadif filter and configure to output a
frame per field of interlaced source the resulting motion is dramatically
