On Wed, Jan 15, 2020 at 21:43:47 -0500, Andrew Brezovsky wrote:
> However, ffmpeg seems to be discarding the handler_name field and replacing
> it with a generic "SoundHandler" value.
I can't reproduce, at least not with my command line.
> Here is the command I'm trying to use:
> ffmpeg -i myster
On 16-01-2020 05:12 am, Daniel Oberhoff via ffmpeg-user wrote:
Hello,
We would like to run the image2 output format with the update flag, such that
it continuously updates a single image (very useful for website thumbnails…)
but we can’t for the death of us not find out how to specify it. Ca
I have been trying to modify the handler_name metadata field of an audio
stream in a video file within an mp4 container.
However, ffmpeg seems to be discarding the handler_name field and replacing
it with a generic "SoundHandler" value.
While the values in the input and output read-outs are correct
Hello,
We would like to run the image2 output format with the update flag, such that
it continuously updates a single image (very useful for website thumbnails…)
but we can’t for the death of us not find out how to specify it. Can anyone
help?
we have tried it like this:
ffmpeg -f lavfi -i t
On 15-01-2020 11:25 pm, Yellow Penguin wrote:
Not as far as I know. You can test each step individually to get an
estimate. On Linux, you can use the 'time' command for this. On all
platforms, you could use the '-report' option. This will create a report
that contains the starting time. The dif
Not as far as I know. You can test each step individually to get an
estimate. On Linux, you can use the 'time' command for this. On all
platforms, you could use the '-report' option. This will create a report
that contains the starting time. The difference between that and the last
modification tim
Is there a way to know how much processor time is going to encoding and
each of the filters? It would help me in making my commands more efficient
if I knew which parts were slow.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mail
I think you need to add -target pal-dv to the last step, so
ffmpeg -i ProblemFileAudio.wav -i Merged\ProblemFileFixed_%05d.png -vf
tinterlace=0 -aspect 4/3 -target pal-dv ProblemFileFixed.dv
On Wed, Jan 15, 2020 at 12:43 PM Thomas Mechau
wrote:
> Hello,
>
> I have kind of a legacy problem:
>
>
Hello,
I have kind of a legacy problem:
Several years ago I had some Super 8 cine material transferred
professionally to miniDV cassettes. I then imported that DV video as
native PAL DV AVI files, i.e. 50i video with a resolution of 720x576
(non-square) pixels.
Since one section of the foot
