On 2024-04-14 21:24 +0200, Nicolas George wrote:
> Nicolas George (12024-04-14):
> > Either we find options to make ffplay display frames as fast as
> > possible, or we must document to the user that no adequate replacement
> > exists.
>
> Please add “-vf setpts=0”. It still has a little more laten
Nicolas George (12024-04-14):
> Either we find options to make ffplay display frames as fast as
> possible, or we must document to the user that no adequate replacement
> exists.
Please add “-vf setpts=0”. It still has a little more latency than a
built-in device, but at least the feature is not *
Alexander Strasser via ffmpeg-devel (12024-04-14):
> When piping ffmpeg into ffplay both programs write a status line in
> the terminal. That causes flickering and invisibility of one or the
> other status line.
The suggestion of piping to ffplay to replace opengl is inadequate: the
muxing, pipe,
When piping ffmpeg into ffplay both programs write a status line in
the terminal. That causes flickering and invisibility of one or the
other status line.
As compromise set ffplay log level to warning, so it doesn't show
the status line.
The user is usually testing ffmpeg command lines and want's
