The filter calls pthreads functions unconditionally.
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index d67855c729..12184c7f26 100755
--- a/configure
+++ b/configure
@@ -3667,7 +3667,7 @@ eq_filter_deps="gpl"
erosion_opencl_filter_deps="o
Quoting Gyan Doshi (2023-02-04 11:01:21)
> Prior to 2d924b3a630, ffmpeg would exit if any packet write failed.
> After the switch to threaded mode for muxing, ffmpeg only closes that
> OutputStream instead of closng the file. This happens because EOF
> returned by write_packet isn't distinguished f
On 2023-02-07 01:39 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2023-02-04 11:01:21)
Prior to 2d924b3a630, ffmpeg would exit if any packet write failed.
After the switch to threaded mode for muxing, ffmpeg only closes that
OutputStream instead of closng the file. This happens because EOF
ret
Quoting Gyan Doshi (2023-02-07 09:18:22)
>
>
> On 2023-02-07 01:39 pm, Anton Khirnov wrote:
> > Quoting Gyan Doshi (2023-02-04 11:01:21)
> >> Prior to 2d924b3a630, ffmpeg would exit if any packet write failed.
> >> After the switch to threaded mode for muxing, ffmpeg only closes that
> >> OutputS
On 2023-02-07 02:03 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2023-02-07 09:18:22)
On 2023-02-07 01:39 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2023-02-04 11:01:21)
Prior to 2d924b3a630, ffmpeg would exit if any packet write failed.
After the switch to threaded mode for muxing, ffmp
On 2023-02-05 04:35 pm, Gyan Doshi wrote:
On 2023-02-05 04:07 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2023-02-04 11:11:12)
On 2023-02-03 09:04 pm, Andreas Rheinhardt wrote:
What does this achieve that can't be achieved by other means
(namely by
an API-user updating the relevant meta
Useful to keep track of what timebase the packet's timestamps are in.
---
fftools/ffmpeg.c | 33 -
fftools/ffmpeg_mux.c | 7 ---
2 files changed, 24 insertions(+), 16 deletions(-)
diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
index 743bc0c6b6..32e0c3feb
Analogous to -enc_stats*, but happens right before muxing. Useful
because bitstream filters and the sync queue can modify packets after
encoding and before muxing. Also has access to the muxing timebase.
---
Changelog | 3 ++-
doc/ffmpeg.texi | 13 +
fftools/
Also, I'm wondering if we shouldn't rename the options to
-stats_{mux,enc_pre,enc_post}[_fmt] for consistency.
They were added just recently, so it should be fine if done before the
release.
Opinions?
--
Anton Khirnov
___
ffmpeg-devel mailing list
ffm
Am 07.02.23 um 10:41 schrieb Anton Khirnov:
Also, I'm wondering if we shouldn't rename the options to
-stats_{mux,enc_pre,enc_post}[_fmt] for consistency.
They were added just recently, so it should be fine if done before the
release.
Opinions?
I'd like that. Can't comment on the code itself
Needed to transfer programs in parent muxing contexts to child muxers,
like in hls, segment, tee muxers.
---
doc/APIchanges | 3 +++
libavformat/avformat.c | 52 ++
libavformat/avformat.h | 2 ++
libavformat/version.h | 2 +-
4 files changed, 58
---
libavformat/hlsenc.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index 39df9becc7..bfad1eef90 100644
--- a/libavformat/hlsenc.c
+++ b/libavformat/hlsenc.c
@@ -907,6 +907,12 @@ static int hls_mux_init(AVFormatContext *s, VariantStream
*
---
libavformat/segment.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavformat/segment.c b/libavformat/segment.c
index 80e4bf851c..a5acc28dfd 100644
--- a/libavformat/segment.c
+++ b/libavformat/segment.c
@@ -182,6 +182,12 @@ static int segment_mux_init(AVFormatContext *s)
---
libavformat/tee.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavformat/tee.c b/libavformat/tee.c
index dd408dd096..fd1b17ce7c 100644
--- a/libavformat/tee.c
+++ b/libavformat/tee.c
@@ -291,6 +291,12 @@ static int open_slave(AVFormatContext *avf, char *slave,
TeeSlave *tee_sla
On 2/5/23, Paul B Mahol wrote:
> On 2/5/23, Michael Niedermayer wrote:
>> On Sat, Feb 04, 2023 at 09:48:38PM +0100, Paul B Mahol wrote:
>>> Patch attached.
>>
>>> af_pan.c |3 +++
>>> 1 file changed, 3 insertions(+)
>>> bf878b3bd193e6462d1babf5e6e45a056a3a0f65
>>> 0001-avfilter-af_pan-fix-re
> > Am 07.02.23 um 10:41 schrieb Anton Khirnov:
> > Also, I'm wondering if we shouldn't rename the options to
> > -stats_{mux,enc_pre,enc_post}[_fmt] for consistency.
> > They were added just recently, so it should be fine if done before the
> > release.
> >
> > Opinions?
>
> I'd like that. Can't
On 2/6/23, Paul B Mahol wrote:
> Patch attached.
>
Better patch attached.
From 15f004ccb196e39c6c429e2c93041444c1a1e419 Mon Sep 17 00:00:00 2001
From: Paul B Mahol
Date: Mon, 6 Feb 2023 14:57:50 +0100
Subject: [PATCH] avfilter: use ff_inlink_make_frame_writable()
Signed-off-by: Paul B Mahol
--
On 2/2/23 10:09, Leo Izen wrote:
We parse the fallback cHRM on decode and correctly determine that we
have BT.709 primaries, but unknown TRC. This causes us to write cICP
where we shouldn't. Primaries without transfer can be handled entirely
by cHRM, so we should only write cICP if we actually kn
On Mon, Feb 6, 2023 at 6:24 AM Thilo Borgmann wrote:
> Martin pointed out we don't need an M2 for FATE as the instruction sets are
> equal on both machines.
It may be worth noting that while the M1 and M2 have the same
instruction set, there is no guarantee the video processing blocks are
identi
Am 07.02.23 um 21:19 schrieb Devin Heitmueller:
On Mon, Feb 6, 2023 at 6:24 AM Thilo Borgmann wrote:
Martin pointed out we don't need an M2 for FATE as the instruction sets are
equal on both machines.
It may be worth noting that while the M1 and M2 have the same
instruction set, there is no
ISOBMFF (14496-12) made this field ('channelcount') in the
AudioSampleEntry structure non-template¹ somewhere before the
release of the 2022 edition. As for ETSI TS 126 244 AKA 3GPP
file format (V16.1.0, 2020-10), it does not seem contain any
references limiting the channelcount entry in AudioSampl
Hi Devin, Thilo,
On Tue, 7 Feb 2023, Thilo Borgmann wrote:
Am 07.02.23 um 21:19 schrieb Devin Heitmueller:
On Mon, Feb 6, 2023 at 6:24 AM Thilo Borgmann
wrote:
Martin pointed out we don't need an M2 for FATE as the instruction sets
are equal on both machines.
It may be worth noting that wh
---
libavcodec/vp9.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libavcodec/vp9.c b/libavcodec/vp9.c
index 7c0a246446..ebb89a413c 100644
--- a/libavcodec/vp9.c
+++ b/libavcodec/vp9.c
@@ -1371,7 +1371,7 @@ static int decode_tiles(AVCodecContext *avctx,
}
From: Haihao Xiang
The next commit and other commits in future may support more mfxPayload
for encoding
Signed-off-by: Haihao Xiang
---
libavcodec/qsv_internal.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/qsv_internal.h b/libavcodec/qsv_internal.h
index 5119
From: Haihao Xiang
option udu_sei is added, user should set udu_sei to true|on|1 if user
data unregistered SEI is expected.
Verify user data unregistered SEI with commands below:
$ ffmpeg -y -f lavfi -i testsrc -vf "format=nv12" -c:v libx264 -frames:v 1
a.h264
$ ffmpeg -y -init_hw_device qsv -i
On 2023-02-04 03:36 pm, Gyan Doshi wrote:
Some files, likely due to faulty packetization or muxing, can have AUDs
at other positions besides the head unit of a packet. Remove these too.
Plan to push in 24h if no more comments.
---
libavcodec/h264_metadata_bsf.c | 13 +++--
1 file
On Tue, 7 Feb 2023, Paul B Mahol wrote:
ffmpeg | branch: master | Paul B Mahol | Sat Feb 4 21:46:15
2023 +0100| [93a9ee7afd7bf2e019490117f1bada30724a0200] | committer: Paul B Mahol
avfilter/af_pan: fix regression introduced with switch to new channel layout API
Fixes #10168
http://git.vid
On 2022-10-21 02:49 pm, Steven Liu wrote:
gnattu 于2022年10月20日周四 20:12写道：
Current HLS implementation simply skip a failed segment to catch up
the stream, but this is not optimal for some use cases like livestream
recording.
Add an option to retry a failed segment to ensure the output file is
a
28 matches
Mail list logo
