On Mon, Mar 25, 2024 at 4:10 PM Niklas Haas wrote:
> From: Niklas Haas
>
> Doing this with REDUCE_FORMATS() instead of swap_color_*() is not only
> shorter, but more importantly comes with the benefit of being done
> inside a loop, allowing us to correctly propagate complex graphs
> involving
On Mon, Mar 25, 2024 at 2:40 PM Niklas Haas wrote:
> > ffmpeg -i in.mp4 -vf
> > "scale='width=1920:height=1080',zscale='width=1920:height=1080'" out.mp4
> > ffmpeg -i in.jpg -vf "zscale='width=1920:height=1080'" out.jpg
> >
> > it doesn't need a specific mp4 or jpg file.
>
> I cannot reproduce
On Sun, Mar 24, 2024 at 6:53 PM Niklas Haas wrote:
> But wait - aren't all filter's lists set to the same reference? Isn't that
> the
> point of the design? If they share the same format list, they will all
> inherit the correct setting (via pick_format). Except for filters like
> vf_scale which
On Sun, Mar 24, 2024 at 2:14 PM Niklas Haas wrote:
> On Sun, 24 Mar 2024 13:49:04 +0100 Damiano Galassi
> wrote:
> > AVFilterLink colorspace and color_range are first set in
> > avfiltergraph.c pick_format(),
> > so in ff_filter_config_links() they will
There two new fields were never sent down the filter chain,
and no filter after the first had colorspace and color_range set,
causing breakage in zscale and possible other filters.
---
libavfilter/avfilter.c | 4
libavfilter/buffersrc.c | 2 ++
2 files changed, 6 insertions(+)
diff --git
On Sat, Mar 23, 2024 at 1:11 PM Niklas Haas wrote:
> On Fri, 22 Mar 2024 22:02:39 +0100 Damiano Galassi
> wrote:
> > There two new fields were never sent down the filter chain, and no
> filter after the first had colorspace and color_range set, causing breakage
> in zscale
There two new fields were never sent down the filter chain, and no filter after
the first had colorspace and color_range set, causing breakage in zscale and
possible other filters.
---
libavfilter/avfilter.c | 4
libavfilter/buffersrc.c | 2 ++
2 files changed, 6 insertions(+)
diff --git
Ping
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
---
libavformat/dump.c | 15 +++
libavformat/isom.h | 3 +++
libavformat/mov.c| 36
libavformat/movenc.c | 22 ++
4 files changed, 76 insertions(+)
diff --git a/libavformat/dump.c b/libavformat/dump.c
index
---
fftools/ffprobe.c | 3 +++
libavcodec/avpacket.c | 1 +
libavcodec/decode.c | 1 +
libavcodec/packet.h | 7 +++
4 files changed, 12 insertions(+)
diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c
index 1ff76ce809..9f17567897 100644
--- a/fftools/ffprobe.c
+++ b/fftools/ffprobe.c
On Tue, Jul 11, 2023 at 6:45 PM Anton Khirnov wrote:
> A FATE test would be much appreciated.
>
Is there some documentation on how to write a FATE test? I've got a small
sample (2 bytes) ready, but I am not too sure how to write the test.
___
On Tue, Jul 11, 2023 at 6:53 PM James Almer wrote:
> On 7/11/2023 4:41 AM, Damiano Galassi wrote:
> > AVDictionaryEntry *encoder;
> > @@ -2430,6 +2451,7 @@ static int mov_write_video_tag(AVFormatContext *s,
> AVIOContext *pb, MOVMuxContex
> > if (track-&g
---
libavformat/dump.c | 15 +++
libavformat/isom.h | 2 ++
libavformat/mov.c| 36
libavformat/movenc.c | 22 ++
4 files changed, 75 insertions(+)
diff --git a/libavformat/dump.c b/libavformat/dump.c
index
---
fftools/ffprobe.c | 3 +++
libavcodec/avpacket.c | 1 +
libavcodec/decode.c | 1 +
libavcodec/packet.h | 7 +++
4 files changed, 12 insertions(+)
diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c
index 1ff76ce809..9f17567897 100644
--- a/fftools/ffprobe.c
+++ b/fftools/ffprobe.c
14 matches
Mail list logo
