On 2021-04-08 04:56, Nicolas George wrote:
Adrian Cable (12021-04-08):
Mark – yes – you’re understanding exactly right! I was thinking
specifically of the encoder ‘throttle’ being a frame rate control, but
other forms of quality control that could be self-adjusted by the
encoder to keep up with
Adrian Cable (12021-04-08):
> Mark – yes – you’re understanding exactly right! I was thinking
> specifically of the encoder ‘throttle’ being a frame rate control, but
> other forms of quality control that could be self-adjusted by the
> encoder to keep up with the input would also work for me.
>
On 2021-04-07 22:33, Adrian Cable wrote:
Mark – yes – you’re understanding exactly right! I was thinking specifically of
the encoder ‘throttle’ being a frame rate control, but other forms of quality
control that could be self-adjusted by the encoder to keep up with the input
would also work
Mark – yes – you’re understanding exactly right! I was thinking specifically of
the encoder ‘throttle’ being a frame rate control, but other forms of quality
control that could be self-adjusted by the encoder to keep up with the input
would also work for me.
I did look through the history here
On 2021-04-07 21:51, Adrian Cable wrote:
Mark,
Sorry, I thought XXX referred to the output -- -vf fps=fps=XXX is *output*
frame rate. To the best
of my knowledge, the input frame rate of VFR video can't be specified.
I’m referring to XXX as the maximum *output* frame rate that the pipeline
Mark,
> Sorry, I thought XXX referred to the output -- -vf fps=fps=XXX is *output*
> frame rate. To the best
> of my knowledge, the input frame rate of VFR video can't be specified.
I’m referring to XXX as the maximum *output* frame rate that the pipeline can
support at a given time, while
On 2021-04-07 10:10, Adrian Cable wrote:
Mark – sorry if I wasn’t clear in my original email. The problem I am
describing is real, not theoretical. I have enormous respect for the time of
everyone on this list, and would not have emailed if my problem could be solved
with “-vsync cfr” or
Am Di., 6. Apr. 2021 um 03:02 Uhr schrieb Adrian Cable :
>
> The problem/question is: how do I get ffmpeg to drop frames as required to
> keep the pipeline running real time?
This is not possible with ffmpeg, the application.
Did you look at the x264 presets?
Carl Eugen
Mark – sorry if I wasn’t clear in my original email. The problem I am
describing is real, not theoretical. I have enormous respect for the time of
everyone on this list, and would not have emailed if my problem could be solved
with “-vsync cfr” or anything as straightforward and as well
On 2021-04-05 21:02, Adrian Cable wrote:
Hi,
I have a question that I thought should have an ‘easy’ answer – I have spent a
lot of time searching and I cannot find it, so thought I would ask here.
My application sounds simple. I have an input RTSP stream, which I need to
transcode and output
Hi,
I have a question that I thought should have an ‘easy’ answer – I have spent a
lot of time searching and I cannot find it, so thought I would ask here.
My application sounds simple. I have an input RTSP stream, which I need to
transcode and output as an RTP stream. Command line is very
11 matches
Mail list logo
