Hi,
> How can I determine the pixel formats that ffmpeg has chosen for the filters'
> input and output pads?
I'm not sure "chosen" is the best way to describe it, but inserting the
showinfo filter will print the format of each frame at that point in the
filterchain. But as format conversions
Am 13.09.2020 um 17:27 schrieb amin...@mailbox.org:
On Sun, Sep 13, 2020 at 07:06:56AM -0400, Edward Park wrote:
Hi,
ffprobe now reports out.mov being yuv420p. Is this an implicit conversion to a
lower bit depth?
It's just the default output format for overlay. It's commonly used for stuff
On Sun, Sep 13, 2020 at 07:06:56AM -0400, Edward Park wrote:
> Hi,
>
> > ffprobe now reports out.mov being yuv420p. Is this an implicit conversion
> > to a lower bit depth?
>
> It's just the default output format for overlay. It's commonly used for stuff
> across colorspaces (like yuv420p
amin...@mailbox.org (12020-09-12):
> But if I create a trivial filter:
^^^
>
> ffmpeg -i a.mov -i b.mov -filter_complex '[0:v][1:v]overlay' out.mov
^^^
There's your problem: your filter is not trivial at all. Overlay
requires
Hi,
> ffprobe now reports out.mov being yuv420p. Is this an implicit conversion to
> a lower bit depth?
It's just the default output format for overlay. It's commonly used for stuff
across colorspaces (like yuv420p video and argb png logos overlaid) especially
with alpha.
You can set format
I have two videos (call them a.mov and b.mov) with the same width, height,
pixel format, etc.
ffprobe reports them as having 'yuv420p10le' pixel format.
If I do a trivial conversion:
ffmpeg -i a.mov out.mov
ffprobe reports out.mov as still being yuv420p10le.
But if I create a trivial
