On Fri, Oct 27, 2023 at 10:06 AM Niklas Haas wrote:
> From: Niklas Haas
>
> When using vf_scale to force a specific output color space, also tag
> this on the AVFrame. (Mirroring existing logic for output range)
> ---
> libavfilter/vf_scale.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff
On Fri, Oct 27, 2023 at 10:05 AM Niklas Haas wrote:
> From: Niklas Haas
>
> Alpha planes are explicitly full range, even for limited range YUVA
> formats. Mark them as such.
> ---
> libavfilter/vf_extractplanes.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git
On Fri, Oct 27, 2023 at 7:54 PM Nicolas George wrote:
> Paul B Mahol (12023-10-27):
> > As OOM scenarios are bad, will apply this fix soon.
>
> This bug, if it is a bug, has been here for quite some time already, a
> few days more will not change anything. I want to analyze this properly,
> do
On Tue, Oct 24, 2023 at 1:56 PM Kyle Swanson wrote:
> I broke the libvmaf_cuda build after
> 6028728bb829c04cc68c66c846c75a70bf4c0613. Fix is attached. I will
> merge this patch soon.
Pushed.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
On Fri, Oct 27, 2023 at 07:04:39PM +0200, Niklas Haas wrote:
> From: Niklas Haas
>
> More commonly, this fixes the case of sws_setColorspaceDetails after
> sws_getContext, since the latter implies sws_init_context.
>
> The problem here is that sws_init_context sets up the range conversion
> and
---
libavformat/hlsenc.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index 4ef84c05c1..e59a38b497 100644
--- a/libavformat/hlsenc.c
+++ b/libavformat/hlsenc.c
@@ -1538,7 +1538,7 @@ static int hls_window(AVFormatContext
On Fri, Oct 27, 2023 at 4:58 AM wrote:
> On 27 Oct 2023, at 5:59, Dave Johansen wrote:
> > @item second_level_segment_index
> > Makes it possible to use segment indexes as %%d in hls_segment_filename
> expression
> > besides date/time values when strftime is on.
> > diff --git
On Fri, Oct 27, 2023 at 07:04:41PM +0200, Niklas Haas wrote:
> From: Niklas Haas
>
> Alpha planes must always be full range, so complain loudly if fed
> limited range grayscale input.
> ---
> libavfilter/vf_alphamerge.c | 6 ++
> 1 file changed, 6 insertions(+)
should be ok
[...]
thx
--
---
libavformat/hlsenc.c | 26 +++---
1 file changed, 19 insertions(+), 7 deletions(-)
diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
index f613e35984..e1714d4eed 100644
--- a/libavformat/hlsenc.c
+++ b/libavformat/hlsenc.c
@@ -1253,9 +1253,11 @@ static int
On Fri, Oct 27, 2023 at 07:04:42PM +0200, Niklas Haas wrote:
> From: Niklas Haas
>
> This code, as written, skips sws_init_context if scale->in_range was not
> set, even if scale->in_frame_range is set to something. So this would
> hit the 'no sws context' fast path in scale_frame and skip color
This allows some optimizations in driver, such as not having to read
back the data if write-only mapping is requested.
---
v4: overwrite + note about vaMapBuffer libva fallback
libavutil/hwcontext_vaapi.c | 12
1 file changed, 12 insertions(+)
diff --git
On Fri, Oct 27, 2023 at 1:33 AM Steven Liu wrote:
> David Johansen 于2023年10月27日周五 12:03写道：
> >
> > >
> > > LGTM
> > >
> > >
> > > Thanks
> > > Steven
> > >
> >
> > I'm new to ffmpeg development so what's the process for this to be
> merged?
> > Do I need to do something or is it taken care of
On Fri, Oct 27, 2023 at 10:15:49AM +0200, Dawid Kozinski/Multimedia (PLT)
/SRPOL/Staff Engineer/Samsung Electronics wrote:
>
>
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Michael Niedermayer
> > Sent: czwartek, 5 października 2023 00:59
> > To: FFmpeg
On Fri, Oct 27, 2023 at 10:07:38AM +0200, Dawid Kozinski/Multimedia (PLT)
/SRPOL/Staff Engineer/Samsung Electronics wrote:
>
>
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Michael Niedermayer
> > Sent: czwartek, 5 października 2023 00:59
> > To: FFmpeg
---
libavcodec/riscv/idctdsp_rvv.S | 25 +
1 file changed, 9 insertions(+), 16 deletions(-)
diff --git a/libavcodec/riscv/idctdsp_rvv.S b/libavcodec/riscv/idctdsp_rvv.S
index fafdddb174..e93e6b5e7a 100644
--- a/libavcodec/riscv/idctdsp_rvv.S
+++
---
libavcodec/riscv/idctdsp_rvv.S | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/libavcodec/riscv/idctdsp_rvv.S b/libavcodec/riscv/idctdsp_rvv.S
index 4ff72f48d2..fafdddb174 100644
--- a/libavcodec/riscv/idctdsp_rvv.S
+++
This follows the same idea as with pixblockdsp, but applied at the
other end, whilst writing data at the end of the function.
---
libavcodec/riscv/idctdsp_rvv.S | 27 +--
1 file changed, 9 insertions(+), 18 deletions(-)
diff --git a/libavcodec/riscv/idctdsp_rvv.S
This will be required for the following changesets.
---
libavcodec/riscv/idctdsp_init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/riscv/idctdsp_init.c b/libavcodec/riscv/idctdsp_init.c
index e6e616a555..4106d90c55 100644
--- a/libavcodec/riscv/idctdsp_init.c
---
libavcodec/riscv/pixblockdsp_init.c | 26 +++---
libavcodec/riscv/pixblockdsp_rvv.S | 6 +++---
2 files changed, 18 insertions(+), 14 deletions(-)
diff --git a/libavcodec/riscv/pixblockdsp_init.c
b/libavcodec/riscv/pixblockdsp_init.c
index aa39a8a665..8f24281217 100644
If the scan lines are aligned, we can load each row as a 64-bit value,
thus avoiding segmentation. And then we can factor the conversion or
subtraction.
In principle, the same optimisation should be possible for high depth,
but would require 128-bit elements, for which no FFmpeg CPU flag
exists.
On 27/10/2023 19:46, David Rosca wrote:
On Fri, Oct 27, 2023 at 7:14 PM Mark Thompson wrote:
On 27/10/2023 11:00, David Rosca wrote:
This allows some optimizations in driver, such as not having to read
back the data if write-only mapping is requested.
---
v3: Fix another warning
Fixes #10617
---
libavformat/smacker.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/libavformat/smacker.c b/libavformat/smacker.c
index 1d54e8e917..d04c8b91a6 100644
--- a/libavformat/smacker.c
+++ b/libavformat/smacker.c
@@ -34,6 +34,8 @@
#define SMACKER_PAL 0x01
#define
> On Oct 27, 2023, at 12:00 PM, Rémi Denis-Courmont wrote:
>
> Le perjantaina 27. lokakuuta 2023, 21.52.51 EEST Cosmin Stejerean via ffmpeg-
> devel a écrit :
>> With a list of FFLabs consultants the "what they work on" can be extracted
>> from the git log or mailing list patches. Not who is
Le perjantaina 27. lokakuuta 2023, 21.52.51 EEST Cosmin Stejerean via ffmpeg-
devel a écrit :
> With a list of FFLabs consultants the "what they work on" can be extracted
> from the git log or mailing list patches. Not who is paying for the work or
> how much is being paid, but certainly the what
> On Oct 27, 2023, at 9:14 AM, Rémi Denis-Courmont wrote:
>
>> Consider FFlabs, you can look at who is being paid by FFlabs, its being
>> mentioned in various places.
>> Then look at what these people do, so you know what they are paid for.
>
> I don't know if FFlabs publishes the payments it
On Fri, Oct 27, 2023 at 7:14 PM Mark Thompson wrote:
>
> On 27/10/2023 11:00, David Rosca wrote:
> > This allows some optimizations in driver, such as not having to read
> > back the data if write-only mapping is requested.
> > ---
> > v3: Fix another warning
> >
> > libavutil/hwcontext_vaapi.c
On Fri, Oct 27, 2023 at 05:10:32AM +0200, Andreas Rheinhardt wrote:
> Michael Niedermayer:
> > Signed-off-by: Michael Niedermayer
> > ---
> > libavcodec/get_bits.h | 8 ++--
> > 1 file changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/libavcodec/get_bits.h
> On Oct 27, 2023, at 5:39 AM, Thilo Borgmann via ffmpeg-devel
> wrote:
>
>> I'll try to post a patch today either inverting their order (which
>> hopefully outputs my community member e-mail), or - since this e-mail
>> is never supposed to apply to any committer cases - removing it.
>
>
> On Oct 27, 2023, at 5:39 AM, Thilo Borgmann via ffmpeg-devel
> wrote:
>
>> I'll try to post a patch today either inverting their order (which
>> hopefully outputs my community member e-mail), or - since this e-mail
>> is never supposed to apply to any committer cases - removing it.
>
>
On Fri, Oct 27, 2023 at 10:06 AM Niklas Haas wrote:
> From: Niklas Haas
>
> PGMYUV seems to be always limited range. This was a format originally
> invented by FFmpeg at a time when YUVJ distinguished limited from full
> range YUV, and this codec never appeared to output YUVJ in any
>
On Fri, Oct 27, 2023 at 07:46:31AM -0400, quietvoid wrote:
>
> On 26/10/2023 17.44, Michael Niedermayer wrote:
> > On Wed, Aug 09, 2023 at 01:46:57PM -0400, quietvoid wrote:
> > > The Dolby Vision RPU contains a CRC32 to validate the payload against.
> > > The implementation is CRC32/MPEG-2.
> >
Paul B Mahol (12023-10-27):
> As OOM scenarios are bad, will apply this fix soon.
This bug, if it is a bug, has been here for quite some time already, a
few days more will not change anything. I want to analyze this properly,
do not push before please.
Regards,
--
Nicolas George
On Fri, Oct 27, 2023 at 02:44:10PM +0200, Michael Koch wrote:
> Is it possible to make the "Bad Content" page invisible? It would be better
> if the spammer can't see the filtering rules.
everything is possible but its not a standard feature of trac that
i know of.
you would have to change trac,
On Fri, Oct 27, 2023 at 3:18 PM Paul B Mahol wrote:
>
>
> On Fri, Oct 27, 2023 at 3:02 PM Nicolas George wrote:
>
>> Paul B Mahol (12023-10-27):
>> > Both patches are required to fix out of memory scenario with this use
>> case:
>>
>> Then please attach an analysis of the fix in the commit
On 27/10/2023 11:00, David Rosca wrote:
This allows some optimizations in driver, such as not having to read
back the data if write-only mapping is requested.
---
v3: Fix another warning
libavutil/hwcontext_vaapi.c | 11 +++
1 file changed, 11 insertions(+)
diff --git
From: Niklas Haas
PGMYUV seems to be always limited range. This was a format originally
invented by FFmpeg at a time when YUVJ distinguished limited from full
range YUV, and this codec never appeared to output YUVJ in any
circumstance, so hard-coding limited range preserves the status quo.
The
From: Niklas Haas
No need to write a custom string parser when we can just use an integer
option with preset values. The various bits of fallback logic are wholly
redundant with equivalent logic already inside sws_getCoefficients.
---
libavfilter/vf_scale.c | 60
From: Niklas Haas
When using vf_scale to force a specific output color space, also tag
this on the AVFrame. (Mirroring existing logic for output range)
---
libavfilter/vf_scale.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/libavfilter/vf_scale.c b/libavfilter/vf_scale.c
index
From: Niklas Haas
YUV->YUV conversions should preserve input range, if the output range is
unspecified. Ensures full-range YUV input comes out as full-range YUV
output by default, even through YUV->YUV pixel format conversions.
---
libavfilter/vf_scale.c | 24
1 file
From: Niklas Haas
This code, as written, skips sws_init_context if scale->in_range was not
set, even if scale->in_frame_range is set to something. So this would
hit the 'no sws context' fast path in scale_frame and skip color range
conversion even where technically required. This had the effect
From: Niklas Haas
Alpha planes must always be full range, so complain loudly if fed
limited range grayscale input.
---
libavfilter/vf_alphamerge.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/libavfilter/vf_alphamerge.c b/libavfilter/vf_alphamerge.c
index 4bbc06da36..b814aa64f0
From: Niklas Haas
Alpha planes are explicitly full range, even for limited range YUVA
formats. Mark them as such.
---
libavfilter/vf_extractplanes.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/libavfilter/vf_extractplanes.c b/libavfilter/vf_extractplanes.c
index 7b7149ab24..ca406ff323
From: Niklas Haas
More commonly, this fixes the case of sws_setColorspaceDetails after
sws_getContext, since the latter implies sws_init_context.
The problem here is that sws_init_context sets up the range conversion
and fast path tables based on the values of srcRange/dstRange at init
time.
On 27/10/2023 16:37, Zhao Zhili wrote:
From: Zhao Zhili
av_hwframe_transfer_data try with src_ctx first. If the operation
failed with AVERROR(ENOSYS), it will try again with dst_ctx. Return
AVERROR(EINVAL) makes the second step being skipped.
---
libavutil/hwcontext_vaapi.c | 10 +-
Thank you. I have emailed the samples to samples-requ...@ffmpeg.org. I will
ping this thread once they are uploaded.
Could somebody please help upload the sample files sent to
samples-requ...@ffmpeg.org so that this patch can be merged? Thank
you!
Done, sorry for delay.
Same for the
On Fri, 27 Oct 2023 12:00:10 +0200
David Rosca wrote:
> This allows some optimizations in driver, such as not having to read
> back the data if write-only mapping is requested.
> ---
> v3: Fix another warning
>
> libavutil/hwcontext_vaapi.c | 11 +++
> 1 file changed, 11 insertions(+)
On Fri, 27 Oct 2023 23:37:01 +0800
Zhao Zhili wrote:
> From: Zhao Zhili
>
> av_hwframe_transfer_data try with src_ctx first. If the operation
> failed with AVERROR(ENOSYS), it will try again with dst_ctx. Return
> AVERROR(EINVAL) makes the second step being skipped.
> ---
>
On Fri, 27 Oct 2023 23:37:00 +0800
Zhao Zhili wrote:
> From: Zhao Zhili
>
> Move it to transfer_get_formats.
> ---
> libavutil/hwcontext_vulkan.c | 25 +
> 1 file changed, 13 insertions(+), 12 deletions(-)
>
> diff --git a/libavutil/hwcontext_vulkan.c
>
Le perjantaina 27. lokakuuta 2023, 19.05.51 EEST Michael Niedermayer a écrit :
> > This is about the funding organisation(s) and the recipient developer(s)
> > in
> > need of sustainable funding. While my income is public (if you know where
> > to look), I sincerely doubt that many people *here*
Hi,
FFmpeg is the winner of the 2nd ZEISS FOSS Funding Award [1]!
We have received $1,001.40 that comes with this award in our SPI account.
-Thilo
[1]
https://blogs.zeiss.com/digital-innovation/en/zeiss-strengthens-engagement-in-foss-community/
On Fri, Oct 27, 2023 at 06:24:58PM +0300, Rémi Denis-Courmont wrote:
>Hi,
>
> Le perjantaina 27. lokakuuta 2023, 15.24.38 EEST Thilo Borgmann via ffmpeg-
> devel a écrit :
> > >>> Why should it be via SPI? What's the benefit of that hypothetical
> > >>> future
> additional funding going via
Le perjantaina 27. lokakuuta 2023, 18.08.54 EEST Thilo Borgmann via ffmpeg-
devel a écrit :
> > Do you seriously think this project will have a sudden outbreak of
> > professionalism and suddenly start producing detailed contracts and
> > statements of work?
>
> The current level appear appealing
Hi,
Le perjantaina 27. lokakuuta 2023, 15.24.38 EEST Thilo Borgmann via ffmpeg-
devel a écrit :
> >>> Why should it be via SPI? What's the benefit of that hypothetical future
additional funding going via SPI, as opposed to:
> >> obviously transparency and community control. None of which is
Am 27.10.23 um 15:38 schrieb Kieran Kunhya:
On Fri, 27 Oct 2023 at 03:23, Thilo Borgmann via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
Am 27.10.23 um 03:28 schrieb Kieran Kunhya:
Hi,
On Thu, 26 Oct 2023 at 12:41, Thilo Borgmann via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
Of
On Fri, Oct 27, 2023 at 06:46:42AM -0700, Kieran Kunhya wrote:
> On Fri, 27 Oct 2023 at 05:32, Michael Niedermayer
> wrote:
>
> > On Fri, Oct 27, 2023 at 01:43:34PM +0300, Rémi Denis-Courmont wrote:
> > >
> > >
> > > Le 26 octobre 2023 18:45:23 GMT+03:00, Michael Niedermayer <
> >
On Fri, 27 Oct 2023 at 05:32, Michael Niedermayer
wrote:
> On Fri, Oct 27, 2023 at 01:43:34PM +0300, Rémi Denis-Courmont wrote:
> >
> >
> > Le 26 octobre 2023 18:45:23 GMT+03:00, Michael Niedermayer <
> mich...@niedermayer.cc> a écrit :
> [...]
> > >* If you have some flashy FFmpeg project you
On Fri, 27 Oct 2023 at 03:23, Thilo Borgmann via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> Am 27.10.23 um 03:28 schrieb Kieran Kunhya:
> > Hi,
> >
> > On Thu, 26 Oct 2023 at 12:41, Thilo Borgmann via ffmpeg-devel <
> > ffmpeg-devel@ffmpeg.org> wrote:
> >
> >> Of course. FFmpeg has a
On Fri, Oct 27, 2023 at 3:02 PM Nicolas George wrote:
> Paul B Mahol (12023-10-27):
> > Both patches are required to fix out of memory scenario with this use
> case:
>
> Then please attach an analysis of the fix in the commit messages. Bugs
> that just disappear when you rework the code
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Michael Niedermayer
> Sent: piątek, 13 października 2023 01:28
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] [PATCH 3/3] avcodec/evc_parse: Check tid
>
> The check is based on not infinite
Paul B Mahol (12023-10-27):
> Both patches are required to fix out of memory scenario with this use case:
Then please attach an analysis of the fix in the commit messages. Bugs
that just disappear when you rework the code completely are not fixed.
Regards,
--
Nicolas George
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Michael Niedermayer
> Sent: czwartek, 5 października 2023 00:59
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] [PATCH 4/4] avcodec/evc_parse: Check tid
>
> The check is based on not infinite
On Fri, Oct 27, 2023 at 2:54 PM Nicolas George wrote:
> Paul B Mahol (12023-10-27):
> > Subject: [PATCH 1/2] avfilter/buffersrc: switch to activate
> >
> > Signed-off-by: Paul B Mahol
> > ---
> > libavfilter/buffersrc.c | 25 -
> > 1 file changed, 16 insertions(+), 9
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Michael Niedermayer
> Sent: piątek, 13 października 2023 01:28
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] [PATCH 3/3] avcodec/evc_parse: Check tid
>
> The check is based on not infinite
Paul B Mahol (12023-10-27):
> Subject: [PATCH 1/2] avfilter/buffersrc: switch to activate
>
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/buffersrc.c | 25 -
> 1 file changed, 16 insertions(+), 9 deletions(-)
What would be the benefit?
> if (s->eof)
> -
Is it possible to make the "Bad Content" page invisible? It would be
better if the spammer can't see the filtering rules.
Michael
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe,
Am 27.10.23 um 13:24 schrieb Jan Ekström:
On Wed, Oct 25, 2023 at 4:14 PM Thilo Borgmann via ffmpeg-devel
wrote:
Hi,
Am 24.10.23 um 23:15 schrieb Anton Khirnov:
Hi all,
as discussed at the dev meeting at VDD, we need to have a series of
votes, the first of which concerns defining when is
On Fri, Oct 27, 2023 at 01:43:34PM +0300, Rémi Denis-Courmont wrote:
>
>
> Le 26 octobre 2023 18:45:23 GMT+03:00, Michael Niedermayer
> a écrit :
[...]
> >* If you have some flashy FFmpeg project you want to work on with a cost of
> > between 5-15k $ then propose it on the mailing list, make
Patches attached.
From 8cbfb1beddcdede7c50a0879ac21654cba02f6b5 Mon Sep 17 00:00:00 2001
From: Paul B Mahol
Date: Fri, 27 Oct 2023 14:26:50 +0200
Subject: [PATCH 1/2] avfilter/buffersrc: switch to activate
Signed-off-by: Paul B Mahol
---
libavfilter/buffersrc.c | 25 -
On Fri, Oct 27, 2023 at 01:10:15PM +0200, Thilo Borgmann via ffmpeg-devel wrote:
> Hi,
>
> Am 27.10.23 um 12:43 schrieb Rémi Denis-Courmont:
> >
> >
> > Le 26 octobre 2023 18:45:23 GMT+03:00, Michael Niedermayer
> > a écrit :
> > > This is financial sustainability Plan A (SPI)
> > > ATM SPI
Am 27.10.23 um 13:30 schrieb Rémi Denis-Courmont:
Hi,
Le 27 octobre 2023 14:10:15 GMT+03:00, Thilo Borgmann via ffmpeg-devel
a écrit :
Le 26 octobre 2023 18:45:23 GMT+03:00, Michael Niedermayer
a écrit :
This is financial sustainability Plan A (SPI)
ATM SPI has like 150k $, we do not
On Thu, Oct 26, 2023 at 06:28:25PM -0700, Kieran Kunhya wrote:
> Hi,
>
> On Thu, 26 Oct 2023 at 12:41, Thilo Borgmann via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> wrote:
>
> > Of course. FFmpeg has a donations account. So the money is already there
> > and
> > already used for the reimbursement
On 26/10/2023 17.44, Michael Niedermayer wrote:
On Wed, Aug 09, 2023 at 01:46:57PM -0400, quietvoid wrote:
The Dolby Vision RPU contains a CRC32 to validate the payload against.
The implementation is CRC32/MPEG-2.
The CRC is only verified with the AV_EF_CRCCHECK flag.
Signed-off-by:
Hi,
Le 27 octobre 2023 14:10:15 GMT+03:00, Thilo Borgmann via ffmpeg-devel
a écrit :
>> Le 26 octobre 2023 18:45:23 GMT+03:00, Michael Niedermayer
>> a écrit :
>>> This is financial sustainability Plan A (SPI)
>>> ATM SPI has like 150k $, we do not activly seek donations, we do not
>>>
On Wed, Oct 25, 2023 at 4:14 PM Thilo Borgmann via ffmpeg-devel
wrote:
>
> Hi,
>
> Am 24.10.23 um 23:15 schrieb Anton Khirnov:
> > Hi all,
> > as discussed at the dev meeting at VDD, we need to have a series of
> > votes, the first of which concerns defining when is the GA voter list to
> > be
Hi,
Am 27.10.23 um 12:43 schrieb Rémi Denis-Courmont:
Le 26 octobre 2023 18:45:23 GMT+03:00, Michael Niedermayer
a écrit :
This is financial sustainability Plan A (SPI)
ATM SPI has like 150k $, we do not activly seek donations, we do not currently
use SPI money to fund any development. SPI
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Michael Niedermayer
> Sent: piątek, 13 października 2023 01:28
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] [PATCH 3/3] avcodec/evc_parse: Check tid
>
> The check is based on not infinite
On 27 Oct 2023, at 5:59, Dave Johansen wrote:
> ---
> doc/muxers.texi | 3 +++
> libavformat/hlsenc.c | 41 +
> 2 files changed, 28 insertions(+), 16 deletions(-)
>
Thanks for the revised patch!
> diff --git a/doc/muxers.texi b/doc/muxers.texi
>
Le 26 octobre 2023 18:45:23 GMT+03:00, Michael Niedermayer
a écrit :
>This is financial sustainability Plan A (SPI)
>ATM SPI has like 150k $, we do not activly seek donations, we do not currently
>use SPI money to fund any development. SPI money is ultimately controlled by
>the FFmpeg
Am 27.10.23 um 03:28 schrieb Kieran Kunhya:
Hi,
On Thu, 26 Oct 2023 at 12:41, Thilo Borgmann via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
Of course. FFmpeg has a donations account. So the money is already there
and
already used for the reimbursement requests. Whatever we spent it for
This allows some optimizations in driver, such as not having to read
back the data if write-only mapping is requested.
---
v3: Fix another warning
libavutil/hwcontext_vaapi.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/libavutil/hwcontext_vaapi.c
It has also occurred to me that in case that the first or last option
wins, the lists would not get updated until January. That means we would
either need to postpone TC/CC elections until then, or vote using the
old lists, both of which seem suboptimal to me.
We could add wording to options 1
This allows some optimizations in driver, such as not having to read
back the data if write-only mapping is requested.
---
v2: Fix warning
libavutil/hwcontext_vaapi.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/libavutil/hwcontext_vaapi.c b/libavutil/hwcontext_vaapi.c
index
Quoting Michael Niedermayer (2023-10-25 21:30:10)
> Hi Anton
>
> first let me say, this looks much better setup than the previous attempt by jb
>
> On Tue, Oct 24, 2023 at 11:15:19PM +0200, Anton Khirnov wrote:
> > Hi all,
> > as discussed at the dev meeting at VDD, we need to have a series of
>
This allows some optimizations in driver, such as not having to read
back the data if write-only mapping is requested.
---
libavutil/hwcontext_vaapi.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/libavutil/hwcontext_vaapi.c b/libavutil/hwcontext_vaapi.c
index
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Michael Niedermayer
> Sent: czwartek, 5 października 2023 00:59
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] [PATCH 3/4] avcodec/evc_parse: remove pow() and
> log2()
>
> The use of float based
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Michael Niedermayer
> Sent: czwartek, 5 października 2023 00:59
> To: FFmpeg development discussions and patches
> Subject: [FFmpeg-devel] [PATCH 2/4] avcodec/evc_parse: Check
> num_remaining_tiles_in_slice_minus1
>
> Fixes:
Dave Johansen 于2023年10月27日周五 12:00写道：
>
> ---
> libavformat/hlsenc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavformat/hlsenc.c b/libavformat/hlsenc.c
> index 24a0304f78..93c47b631b 100644
> --- a/libavformat/hlsenc.c
> +++ b/libavformat/hlsenc.c
> @@
From: Zhao Zhili
av_hwframe_transfer_data try with src_ctx first. If the operation
failed with AVERROR(ENOSYS), it will try again with dst_ctx. Return
AVERROR(EINVAL) makes the second step being skipped.
---
libavutil/hwcontext_vaapi.c | 10 +-
1 file changed, 5 insertions(+), 5
From: Zhao Zhili
Move it to transfer_get_formats.
---
libavutil/hwcontext_vulkan.c | 25 +
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/libavutil/hwcontext_vulkan.c b/libavutil/hwcontext_vulkan.c
index 8dd40cb66f..8481427b42 100644
---
David Johansen 于2023年10月27日周五 12:03写道：
>
> >
> > LGTM
> >
> >
> > Thanks
> > Steven
> >
>
> I'm new to ffmpeg development so what's the process for this to be merged?
> Do I need to do something or is it taken care of by a different
> process/someone else?
Nothing, just leave enough time for
90 matches
Mail list logo
