I have had a chance to test the issue on friends' laptops so here are two
more data points. They have only version 4.3.1 I believe, not the latest
HEAD. Their built-in mic sample rate is 48000Hz (I suppose more recent
laptops updated it?).
1) MacBook Pro (13-inch, 2018, Four Thunderbolt 3 Ports)
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
On Sun, Sep 13, 2020 at 4:14 PM Dennis Mungai wrote:
> Hello there,
>
> Can a standard complex filter graph (initialized via -filter_complex) be
> used with an audio filter (inserted via -af) in the same command?
>
> Take this rudimentary example snippet:
>
> ffmpeg -fflags +genpts -vsync 1 \
>
Hello there,
Can a standard complex filter graph (initialized via -filter_complex) be
used with an audio filter (inserted via -af) in the same command?
Take this rudimentary example snippet:
ffmpeg -fflags +genpts -vsync 1 \
-threads 1 -dn \
-i
Hello all,
I'm just testing the new -noauto_conversion_filters option.
As the first step, I'm running this command line (without the new option):
ffmpeg -v verbose -f lavfi -i testsrc2=s=svga:d=5,format=yuv422p10le -vf
lut3d="VLog_to_V709.cube" -pix_fmt yuv422p10le -c:v h264 -y out.mov
This
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
10 matches
Mail list logo