> I don't use releases myself, but I always advise AV
> archivists, who implement FFmpeg in their workflow, to use
> the last release of an actively maintained branch. Why?
> Because for the people living outside our "gang" it is much
> easier to keep the software updated this way
So do you
On Fri, 14 Oct 2016, PSPunch wrote:
Hi Marton,
The suggested options fixed the sync issue in a snap.
Thank you, thank you, thank you!!
BTW, I understand from brief searching that the wallclock option is
relatively new. Just curious how FFmpeg users dealt with Decklink boards
until they
Moritz Barsnick wrote:
>Why do you need a release, anyway?
The question about the releases is asked from time to time.
I don't use releases myself, but I always advise AV
archivists, who implement FFmpeg in their workflow, to use
the last release of an actively maintained branch. Why?
Because
>
> "ffmpeg -loglevel verbose" at least shows you which segments are opened.
>
Well what do know, I should have tried that. Very useful on m3u8s.
> Why do you need a release, anyway? Do you rely on getting your ffmpeg
> from a distribution?
>
For development it doesn't really matter. For our
Hello!
I am trying to generate still image with silent audio-track to push it
to the DVB network. MPEG-ts stream is generating with this command:
~/bin/ffmpeg -loop 1 -i ~/image-mpeg4.jpg -f lavfi -i anullsrc -map 0:v -map
1:a -c:a mp2 -b:a 128k -c:v libx264 -preset medium -profile:v
On 13/10/16 14:01, tyt xtreme wrote:
And what can i do on Windows to check these capabilities?
Btw the GPU is a Gainward 6 Gb nVidia GTX 980 Ti so i think this should
support the above formats.
Any idea why this encoding doesn't work?
$ ffmpeg -i perspective.mp4 -c:v h264_nvenc -profile:v
