> On May 14, 2024, at 9:28 AM, Lynne via ffmpeg-devel
> wrote:
>
> On 14/05/2024 17:09, Christian Bartnik wrote:
>> From: Thomas Siedel
>> Add external decoder VVdeC for H266/VVC decoding.
>> Register new decoder libvvdec.
>> Add libvvdec to wrap the vvdec interface.
>> Enable decoder by addi
> On May 18, 2024, at 7:04 AM, Nuo Mi wrote:
>
> This happened many years ago. See the discussion here:
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/20201221060710.12230-6-nuomi2...@gmail.com/#60589
> Now that we have an internal vvc decoder, we can focus on improving it.
> As for the en
On May 18, 2024, at 10:48 PM, Rémi Denis-Courmont wrote:
Le 18 mai 2024 21:55:04 GMT+03:00, Cosmin Stejerean via ffmpeg-devel
mailto:ffmpeg-devel@ffmpeg.org> > a écrit :
On May 18, 2024, at 7:04 AM, Nuo Mi mailto:nuomi2...@gmail.com> > wrote:
This happened many years ago. See th
Trying again with better formatting, hopefully
> On May 18, 2024, at 10:48 PM, Rémi Denis-Courmont wrote:
>
> Hi,
>
> Le 18 mai 2024 21:55:04 GMT+03:00, Cosmin Stejerean via ffmpeg-devel
> a écrit :
>>
>>
>>> On May 18, 2024, at 7:04 AM, Nuo Mi wrote
> On May 20, 2024, at 11:03 AM, Rémi Denis-Courmont wrote:
>
> Le maanantaina 20. toukokuuta 2024, 19.33.43 EEST Cosmin Stejerean via ffmpeg-
> devel a écrit :
>
>> hwaccel decoding seems somewhat orthogonal
>
> How exactly will that work then? Either vvdec
> On May 20, 2024, at 12:01 PM, Rémi Denis-Courmont wrote:
>
> Le maanantaina 20. toukokuuta 2024, 21.39.18 EEST Cosmin Stejerean via ffmpeg-
> devel a écrit :
>> The same way using FDK-AAC as a decoder works, if you want to use it as the
>> *AAC decoder you have to
> On May 20, 2024, at 1:05 PM, Rémi Denis-Courmont wrote:
>
> Le maanantaina 20. toukokuuta 2024, 22.33.45 EEST Cosmin Stejerean via ffmpeg-
> devel a écrit :
>>> And again, you can't expect users to select decoders manually. If vvdec is
>>> the
>>&
From: Cosmin Stejerean
It looks like the el_bitdepth_minus8 value in the header can also encode
ext_mapping_idc in the upper 8 bits.
Samples having a non-zero ext_mapping_idc fail validation currently because the
value returned is out of range. This bypasses this by currently ignoring the
ext_ma
From: Cosmin Stejerean
Co-authored-by: Amir Naghdinezhad
Signed-off-by: Cosmin Stejerean
---
libavcodec/libsvtav1.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/libavcodec/libsvtav1.c b/libavcodec/libsvtav1.c
index 3b41f5a39e..1eda63200c 100644
--- a/libavcodec/libsvtav1.c
+
> On May 20, 2024, at 6:17 PM, Cosmin Stejerean via ffmpeg-devel
> wrote:
>
> From: Cosmin Stejerean
>
> Co-authored-by: Amir Naghdinezhad
> Signed-off-by: Cosmin Stejerean
> ---
> libavcodec/libsvtav1.c | 10 ++
> 1 file changed, 10 insertions(+)
From: Cosmin Stejerean
not all clients support metadata compression, make this an option and off by
default until we can verify output.
vdr_dm_metadata_changed = 0 case fails the DV verifier so force this to true
for now until we can determine the correct output format for this case.
---
liba
> On May 21, 2024, at 3:21 AM, Niklas Haas wrote:
>
> On Tue, 21 May 2024 01:17:32 +0000 Cosmin Stejerean via ffmpeg-devel
> wrote:
>> From: Cosmin Stejerean
>>
>> It looks like the el_bitdepth_minus8 value in the header can also encode
>>
From: Cosmin Stejerean
These two fields are coded together into a single 16 bit integer with upper 8
bits for ext_mapping_idc and lower 8 bits for el_bit_depth_minus8.
Furthermore ext_mapping_idc has two components, upper 3 bits and lower 5 bits.
---
libavcodec/dovi_rpudec.c | 7 ++-
libav
> On May 21, 2024, at 11:48 AM, Dennis Sädtler via ffmpeg-devel
> wrote:
>
>> From: Dennis Sädtler via ffmpeg-devel
>
> I wonder what happened here, did I make a mistake when submitting the
> original patch to the ML so the actual commit author name/email got
> lost?
>
> Should be the same
> On May 21, 2024, at 11:54 AM, Cosmin Stejerean via ffmpeg-devel
> wrote:
>
>
> However I've found a workaround. By setting my git send-email from to just
> "cos...@cosmin.at <mailto:cos...@cosmin.at>" rather than "Cosmin Stejerean
> mailto:
> On May 21, 2024, at 11:54 AM, Cosmin Stejerean via ffmpeg-devel
> wrote:
>
>
> However I've found a workaround. By setting my git send-email from to just
> "cos...@cosmin.at <mailto:cos...@cosmin.at>" rather than "Cosmin Stejerean
> mailto:
> On May 21, 2024, at 9:19 PM, Andreas Rheinhardt
> wrote:
>
> Cosmin Stejerean via ffmpeg-devel:
>> From: Cosmin Stejerean
>>
>> These two fields are coded together into a single 16 bit integer with upper 8
>> bits for ext_mapping_idc and
From: Cosmin Stejerean
---
libavutil/dovi_meta.h | 2 ++
libavutil/version.h | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavutil/dovi_meta.h b/libavutil/dovi_meta.h
index e10332f8d7..e168075a24 100644
--- a/libavutil/dovi_meta.h
+++ b/libavutil/dovi_meta.h
@@ -91,6
From: Cosmin Stejerean
These two fields are coded together into a single 16 bit integer with upper 8
bits for ext_mapping_idc and lower 8 bits for el_bit_depth_minus8.
Furthermore ext_mapping_idc has two components, upper 3 bits and lower 5 bits.
---
libavcodec/dovi_rpudec.c | 7 ++-
libavc
From: Cosmin Stejerean
Some DolbyVision samples fail to parse currently due to mis-reading the
el_bit_depth_minus8 field. Upon investigation it seems that the RPU syntax has
been extended in an as of yet undocumented way by adding ext_mapping_idc and
coding it together with el_bit_depth_minus8 to
> On May 21, 2024, at 3:19 AM, Niklas Haas wrote:
>
> On Tue, 21 May 2024 04:03:43 +0000 Cosmin Stejerean via ffmpeg-devel
> wrote:
>>
>> diff --git a/libavcodec/libaomenc.c b/libavcodec/libaomenc.c
>> index dec74ebecd..c6104f5522 100644
>> --- a/libavc
From: Cosmin Stejerean
not all clients support metadata compression, output when
vdr_dm_metadata_changed fails the DV verifier.
---
libavcodec/dovi_rpu.h| 10 ++
libavcodec/dovi_rpuenc.c | 8 ++--
libavcodec/libaomenc.c | 3 +--
libavcodec/libsvtav1.c | 3 +--
libavcodec/
From: Cosmin Stejerean
not all clients support metadata compression, output when
vdr_dm_metadata_changed fails the DV verifier.
Compared to v2 this makes the dovi field name a parameter of the
DOVI_ENCODING_OPTS macro as requested. It also splits up the commits into
introducing the macro, guar
From: Cosmin Stejerean
Add a field to enable or disable metadata compression since not all clients
support this.
Introduce DOVI_ENCODING_OPTS macro to faciliate exposing this as an option to
encoders.
---
libavcodec/dovi_rpu.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/
From: Cosmin Stejerean
Guard use_prev_vdr_rpu by the new enable_compression field since not all
clients support this.
Separately output when vdr_dm_metadata_changed == 0 fails the DV verifier so
turn that off unconditionally for now.
---
libavcodec/dovi_rpuenc.c | 8 ++--
1 file changed,
From: Cosmin Stejerean
---
libavcodec/libaomenc.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/libavcodec/libaomenc.c b/libavcodec/libaomenc.c
index dec74ebecd..22429717e8 100644
--- a/libavcodec/libaomenc.c
+++ b/libavcodec/libaomenc.c
@@ -1487,8 +1487,7 @@ static const
From: Cosmin Stejerean
---
libavcodec/libx265.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/libavcodec/libx265.c b/libavcodec/libx265.c
index ac1dbc4f97..70e447fc0e 100644
--- a/libavcodec/libx265.c
+++ b/libavcodec/libx265.c
@@ -951,8 +951,7 @@ static const AVOption op
From: Cosmin Stejerean
---
libavcodec/libsvtav1.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/libavcodec/libsvtav1.c b/libavcodec/libsvtav1.c
index 2fef8c8971..4a8cab4eb9 100644
--- a/libavcodec/libsvtav1.c
+++ b/libavcodec/libsvtav1.c
@@ -731,8 +731,7 @@ static const A
> On May 23, 2024, at 4:03 AM, Niklas Haas wrote:
>
> On Wed, 22 May 2024 15:50:43 +0000 Cosmin Stejerean via ffmpeg-devel
> wrote:
>> From: Cosmin Stejerean
>>
>> ---
>> libavutil/dovi_meta.h | 2 ++
>> libavutil/version.h | 2 +-
>&
> On Jun 3, 2024, at 12:55 AM, Rémi Denis-Courmont wrote:
>
> IBC is probably not as (cost-)problematic as NAB, w.r.t. setting up the booth
> or transportation
What was cost-problematic about NAB? As far as I know it cost ffmpeg $0. It
would be hard for IBC to be less cost-problematic than t
> On Jun 3, 2024, at 10:36 AM, Rémi Denis-Courmont wrote:
>
> Le 3 juin 2024 19:43:52 GMT+03:00, Cosmin Stejerean via ffmpeg-devel
> a écrit :
>>
>>
>>> On Jun 3, 2024, at 12:55 AM, Rémi Denis-Courmont wrote:
>>>
>>> IBC is probably not
> On Jun 3, 2024, at 11:18 AM, Rémi Denis-Courmont wrote:
>
> Le maanantaina 3. kesäkuuta 2024, 20.48.08 EEST Cosmin Stejerean via ffmpeg-
> devel a écrit :
>>>> What was cost-problematic about NAB? As far as I know it cost ffmpeg $0.
>>>> It would be hard
> On Jun 3, 2024, at 12:26 PM, Rémi Denis-Courmont wrote:
>
> Le maanantaina 3. kesäkuuta 2024, 21.58.48 EEST Cosmin Stejerean via ffmpeg-
> devel a écrit :
>> Not sure why you keep beating this dead horse.
>
> Err, I think that it is obvious why:
>
> 1) The qu
> On Jun 3, 2024, at 3:58 PM, Vittorio Giovara
> wrote:
>
> On Mon, Jun 3, 2024 at 10:57 PM Cosmin Stejerean via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> wrote:
>
>>
>>
>>> On Jun 3, 2024, at 12:26 PM, Rémi Denis-Courmont
>> wrote:
>&
> On Jun 3, 2024, at 11:53 PM, Vittorio Giovara
> wrote:
>
> On Tue, Jun 4, 2024 at 3:01 AM Cosmin Stejerean via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> wrote:
>
>>> Reposting my question/comment here since Thilo hasn't had a chance to
>>> re
> On Jun 5, 2024, at 5:23 AM, Niklas Haas wrote:
>
> On Wed, 05 Jun 2024 12:07:08 +0200 Andreas Rheinhardt
> wrote:
>> Niklas Haas:
>>> From: Niklas Haas
>>>
>>> This code was unnecessarily trying to be robust against downgrades of
>>> libavutil (relative to the version libavcodec was compil
> On Jun 19, 2024, at 3:21 AM, Niklas Haas wrote:
>
> On Thu, 23 May 2024 19:50:23 +0000 Cosmin Stejerean via ffmpeg-devel
> wrote:
>> From: Cosmin Stejerean
>>
>> not all clients support metadata compression, output when
>> vdr_dm_metadata_changed fa
From: Cosmin Stejerean
now that we are reading ext_mapping_idc as the upper 8 bits of
el_bit_depth_minus8 we need to use get_ue_golomb_long rather than
get_ue_golomb_31 for reading it
---
libavcodec/dovi_rpudec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/dov
> On Oct 13, 2023, at 4:00 PM, Vittorio Giovara
> wrote:
>
> TBF this is in part why i was suggesting a new library - I feel like sws is
> affected by bad brading because of these caching issues and imprecise
> conversion, and a new clean api in a new library would make a lot of sense
> in my
> On Oct 13, 2023, at 4:00 PM, Niklas Haas wrote:
>
> That said, if the status quo for the past decades is to for vf_scale
> treat unspecified chroma loc as center-aligned, I am no longer sure if
> suddenly changing this behavior is a good idea.
I'd say that the current default (jpeg chroma lo
> On Oct 17, 2023, at 7:36 AM, Michael Niedermayer
> wrote:
>
> On Sat, Oct 14, 2023 at 07:53:04PM +0200, Stefano Sabatini wrote:
>>
>> It would be useful at this point to define the process to accept the
>> proposal and potential candidates. We have a technical committee which
>> might take
> On Oct 20, 2023, at 10:53 AM, Michael Koch
> wrote:
>
>> should i add /pipermail/ffmpeg-trac to robots.txt ?
> is there anyone who googles in these ffmpeg trac archives ?
>
> I don't.
I'd imagine anyone wanting to search would search trac itself rather than the
mailing list archive. If i
> On Oct 25, 2023, at 10:39 AM, Rémi Denis-Courmont wrote:
>
> Objectively, it really does not matter insofar as we are dealing solely with
> non-GA members such as I. But if I were to play devil's advocate, you may be
> serving on a plate a pretext for some future dissatisfied voters to call
> 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.
>
> And
> 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.
>
> And
> 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 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 o
> On Oct 20, 2023, at 9:01 AM, Michael Niedermayer
> wrote:
>
> our downstream list shows no maintained users of that release
> https://trac.ffmpeg.org/wiki/Downstreams
I was trying to track down the status of OpenMandriva Lx 3 because it's listed
as a downstream for ffmpeg 4.0. While doing
Per http://ffmpeg.org/pipermail/ffmpeg-devel/2023-November/316480.html
a list of emails should not be published as the GA membership. To
facilitate publishing the GA list this updates the GA script to also
print names along with the emails in the format
```
Name
```
Cosmin Stejerean (1):
updat
Update GA script to print names in addition to emails since emails
should not be shared in all contexts, this makes it easier to publish
the current GA membership.
Signed-off-by: Cosmin Stejerean
---
tools/general_assembly.pl | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --g
> On Nov 3, 2023, at 11:40 AM, Nicolas George wrote:
>
> This is also changing the sort order. It might be acceptable but it
> might also not be.
It is and I probably should have called that out in the description. If the
goal is to publish mostly names and not emails in various places like
> On Nov 5, 2023, at 5:41 AM, Thilo Borgmann via ffmpeg-devel
> wrote:
>
> The script should output two files then, so that no manual editing is
> required.
> The voting system expects a file with mail addresses one per line and the ML
> then shall be given the very same list but with only
Per http://ffmpeg.org/pipermail/ffmpeg-devel/2023-November/316480.html
a list of emails should not be published as the GA membership. To
facilitate publishing the GA list this updates the GA script with
options to print only names, only emails (for voting) or both.
Changes since v1:
- added --emai
Signed-off-by: Cosmin Stejerean
---
tools/general_assembly.pl | 43 +--
1 file changed, 41 insertions(+), 2 deletions(-)
diff --git a/tools/general_assembly.pl b/tools/general_assembly.pl
index 898a6262ef..8204d89794 100644
--- a/tools/general_assembly.pl
+++
> On Nov 9, 2023, at 9:53 AM, Rémi Denis-Courmont wrote:
>
> The point is that, whether or not they are on the mailing list, people should
> not be volunteered to the GA by others, but on their own volition. The
> circumstances are different for those on the mailing list and those not, but
>
On Nov 20, 2023, at 5:14 PM, James Almer wrote:
On 11/20/2023 4:22 PM, Thilo Borgmann via ffmpeg-devel wrote:
+ if (*got_frame) {
+ if (!(s->vp8x_flags & VP8X_FLAG_ANIMATION)) {
+ // no animation, output the decoded frame
+ av_frame_move_ref(p, s->frame);
+
Fixes #10688
Signed-off-by: Cosmin Stejerean
---
libavfilter/vf_bwdif.c | 12
1 file changed, 12 insertions(+)
diff --git a/libavfilter/vf_bwdif.c b/libavfilter/vf_bwdif.c
index 137cd5ef13..bce11c39f7 100644
--- a/libavfilter/vf_bwdif.c
+++ b/libavfilter/vf_bwdif.c
@@ -197,6 +197,1
> On Nov 28, 2023, at 5:30 AM, Thomas Mundt wrote:
>
> Hi Cosmin,
>
> Cosmin Stejerean via ffmpeg-devel schrieb am Sa.,
> 25. Nov. 2023, 21:39:
>
>> Fixes #10688
>>
>> Signed-off-by: Cosmin Stejerean
>> ---
>> libavfilter/vf_bwdif.c
> On Nov 29, 2023, at 11:36 AM, Dennis Mungai wrote:
>
> On Wed, 29 Nov 2023 at 22:26, Cosmin Stejerean via ffmpeg-devel <
> ffmpeg-devel@ffmpeg.org> wrote:
>
>>
>>
>>> On Nov 28, 2023, at 5:30 AM, Thomas Mundt wrote:
>>>
>>> Hi
> On Nov 29, 2023, at 3:14 PM, Michael Niedermayer
> wrote:
>
> If you give Jerry a weight of 10 and give Tom a weight of 9, that means
> you prefer Jerry over Tom because 10 > 9
> If you give Spike a weight of 20 that would mean you not only prefer Spike
> over Tom OR Jerry but also over Tom
From: Cosmin Stejerean
This fixes the issue reported in #10688. In v2 the checks for chroma
plane are combined together and the fixes are extended to cover the
Vulkan and CUDA implementations of bwdif.
I have not had a chance to replicate the issue on CUDA or Vulkan but
based on the dimension ch
From: Cosmin Stejerean
Signed-off-by: Cosmin Stejerean
---
libavfilter/vf_bwdif_cuda.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/libavfilter/vf_bwdif_cuda.c b/libavfilter/vf_bwdif_cuda.c
index a5ecfbadb6..7d9bf861b7 100644
--- a/libavfilter/vf_bwdif_cuda
From: Cosmin Stejerean
Fixes #10688
Signed-off-by: Cosmin Stejerean
---
libavfilter/vf_bwdif.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/libavfilter/vf_bwdif.c b/libavfilter/vf_bwdif.c
index 137cd5ef13..80aa85a48b 100644
--- a/libavfilter/vf_bwdif.c
+++
From: Cosmin Stejerean
Signed-off-by: Cosmin Stejerean
---
libavfilter/vf_bwdif_vulkan.c | 14 ++
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/libavfilter/vf_bwdif_vulkan.c b/libavfilter/vf_bwdif_vulkan.c
index 690a89c4ba..6a886d11ac 100644
--- a/libavfilter/vf_bwd
> On Nov 29, 2023, at 5:42 PM, Ronald S. Bultje wrote:
>
> Does ranked voting allow expressing equal weight to multiple candidates?
> For example, I prefer Jerry and Tom equally, but I prefer either one over
> Spike.
In theory that could depend on the implementation of ranked voting, it could
> On Nov 30, 2023, at 03:07, Tomas Härdin wrote:
>
> tor 2023-11-30 klockan 01:49 +0100 skrev Stefano Sabatini:
>> This is meant to introduce functionality to handle QR codes.
>
> Why?
>
The why seems to be answered below the section you quoted in the original email
> QR codes are robust to
On Nov 30, 2023, at 04:37, Thomas Mundt wrote:
Am Do., 30. Nov. 2023 um 01:23 Uhr schrieb Cosmin Stejerean via ffmpeg-devel
mailto:ffmpeg-devel@ffmpeg.org> >:
From: Cosmin Stejerean mailto:cos...@cosmin.at> >
Fixes #10688
Signed-off-by: Cosmin Stejerean mailto:cos.
> On Dec 2, 2023, at 7:53 AM, Anton Khirnov wrote:
>
> Its author not only failed to add any tests, as is required by the
> development rules, but continues to actively refuse to do so.
>
> Untested decoders are worse than useless, so remove it.
While I agree that decoders (among other things
From: Cosmin Stejerean
This fixes the issue reported in #10688. In v3 only the chroma planes
are checked based on feedback for v2, since the chroma planes are
going to have the minimum dimension.
Cosmin Stejerean (3):
avfilter/vf_bwdif: consider chroma subsampling when enforcing minimum
di
From: Cosmin Stejerean
Signed-off-by: Cosmin Stejerean
---
libavfilter/vf_bwdif_cuda.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/libavfilter/vf_bwdif_cuda.c b/libavfilter/vf_bwdif_cuda.c
index a5ecfbadb6..418f15f989 100644
--- a/libavfilter/vf_bwdif_cuda.c
From: Cosmin Stejerean
Signed-off-by: Cosmin Stejerean
---
libavfilter/vf_bwdif_vulkan.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/libavfilter/vf_bwdif_vulkan.c b/libavfilter/vf_bwdif_vulkan.c
index 690a89c4ba..c51df9aa26 100644
--- a/libavfilter/vf_bwdif_v
From: Cosmin Stejerean
Fixes #10688
Signed-off-by: Cosmin Stejerean
---
libavfilter/vf_bwdif.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/libavfilter/vf_bwdif.c b/libavfilter/vf_bwdif.c
index 137cd5ef13..353cd0b61a 100644
--- a/libavfilter/vf_bwdif.c
+++ b/lib
From: Cosmin Stejerean
---
tests/Makefile | 1 +
tests/fate/qoa.mak | 12
tests/ref/fate/qoa-152 | 13
tests/ref/fate/qoa-278 | 135 +
tests/ref/fate/qoa-303 | 35 +++
5 files changed, 196 insertions(+)
create mode 10064
> On Dec 6, 2023, at 02:44, Philip Langdale via ffmpeg-devel
> wrote:
>
> On Sat, 2 Dec 2023 23:02:36 +0100
> Thomas Mundt wrote:
>
>>
>> LGTM, thanks.
>>
>
> I am going to squash the three commits and push. There's no real need
> to put each filter in a separate diff when the logical cha
> On Dec 6, 2023, at 11:36 AM, Anton Khirnov wrote:
>
>> In some cases the performance penalty because of threading is quite
>> significant:
>>
>> Example command line:
>>
>> ffmpeg -f lavfi -i sine -af volume=6dB -f null none
>>
>> After latest threading changes: speed=810x
>> Before lates
> On Dec 7, 2023, at 9:42 AM, Andreas Rheinhardt
> wrote:
>
> According to
> https://developers.google.com/speed/webp/docs/riff_container#extended_file_format
> metadata chunks are stored after the image data; if you split the data
> into packets, then the metadata while only become available
> On Dec 8, 2023, at 11:07 AM, Kalev Lember wrote:
>
> On Fri, Dec 8, 2023 at 4:59 PM James Almer wrote:
>
>> Does the configure check ensure a new enough openh264 version is the
>> minimum supported?
>>
>
> Hm, I'd say that configure minimum version check is mostly orthogonal to
> the patc
> On Mar 25, 2024, at 1:49 AM, Andrea Mastroberti via ffmpeg-devel
> wrote:
>
> Signed-off-by: Andrea Mastroberti <10736...@polimi.it>
> ---
> doc/filters.texi | 20 -
> libavfilter/version.h | 2 +-
> libavfilter/vf_smartblur.c | 44 ++
> On May 2, 2024, at 9:35 AM, Zhao Zhili wrote:
>
> I know a developer which have contributed to FFmpeg and stop doing so after
> losing his git-send-email environment.
I'm not surprised, getting git-send-email to work can be fairly daunting.
First you have to know enough about secure SMTP to
> On May 3, 2024, at 6:54 AM, Ronald S. Bultje wrote:
>
> On Fri, May 3, 2024 at 7:33 AM Rémi Denis-Courmont wrote:
>
>>
>> There is no technical plan how that would actually work in practice, and I
>> don't think it is even feasible. Not to speak of a realistic plan who would
>> actually im
> On Feb 20, 2024, at 12:41 PM, Michael Niedermayer
> wrote:
>
> On Tue, Feb 20, 2024 at 05:10:11PM +0100, Anton Khirnov wrote:
>> Quoting Michael Niedermayer (2024-02-20 15:01:11)
>>> On Tue, Feb 20, 2024 at 09:22:57AM +0100, Anton Khirnov wrote:
>>> [...]
their preferred wording, and th
From: Cosmin Stejerean
Co-authored-by: Amir Naghdinezhad
Signed-off-by: Cosmin Stejerean
---
libavcodec/libsvtav1.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/libavcodec/libsvtav1.c b/libavcodec/libsvtav1.c
index 3b41f5a39e..1eda63200c 100644
--- a/libavcodec/libsvtav1.c
+
> On Feb 27, 2024, at 1:19 PM, James Almer wrote:
>
> SVT-AV1 1.8.0 has this value set to 1.8.0, same as in the current git head
> commit. Is this in preparation for an upcoming release?
Yes, this is in preparation for release 2.0 which is targeted for next week.
https://gitlab.com/AOMediaCo
> On Feb 27, 2024, at 1:49 PM, James Almer wrote:
>
>>> SVT-AV1 1.8.0 has this value set to 1.8.0, same as in the current git head
>>> commit. Is this in preparation for an upcoming release?
>> Yes, this is in preparation for release 2.0 which is targeted for next week.
>> https://gitlab.com/
> On Feb 29, 2024, at 7:27 AM, Zhao Zhili wrote:
>
> Hi, I can't pull from main developer git server. Patchwork is slow to loading.
> I have tried two ISP. Anything happened?
Not sure if it's related but trac has also been very unreliable for me, with
frequent "Service Unavailable" errors fro
> On Feb 20, 2024, at 7:07 PM, wenbin.chen-at-intel@ffmpeg.org wrote:
>
> From: Wenbin Chen
>
> PyTorch is an open source machine learning framework that accelerates
> the path from research prototyping to production deployment. Official
> website: https://pytorch.org/. We call the C++ libr
> On Mar 2, 2024, at 11:01 AM, Ronald S. Bultje wrote:
>
> This recusal may be effected either directly by
>> the TC member, or by a vote of the Community Committee (CC)
>>
>
> The CC is for enforcement of behavioural guidelines (CoC), not for
> technical matters, so this strikes me as a bi
On Mar 19, 2024, at 10:21 AM, Kieran Kunhya wrote:
On Tue, 19 Mar 2024 at 15:27, James Almer mailto:jamr...@gmail.com> > wrote:
On 3/19/2024 12:20 PM, Kieran Kunhya wrote:From
https://github.com/v-novaltd/LCEVCdec
" This software is protected by copyrights and other intellectual
property
rights
> On Mar 19, 2024, at 2:39 PM, Derek Buitenhuis
> wrote:
>
> The reason I never implemented this back when I adde RPU side data is that
> there is a strong chance of generating broken files.
>
> That's because if we do anything to the video with swscale, etc., we're
> now encoding RPUs that a
> On Aug 17, 2023, at 11:36 PM, Damiano Galassi wrote:
>
> Ping
>
I believe this is still waiting for a FATE test to be added.
- Cosmin
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To uns
> On Sep 8, 2023, at 6:09 AM, Michael Niedermayer
> wrote:
>
> modern video encoders where no longer added to ffmpeg
Writing a good modern video encoder is a massive undertaking, and i think it's
likely that encoders are going to be mostly integrated via libraries.
Along those lines thoug
> On Sep 24, 2023, at 5:45 PM, Michael Niedermayer
> wrote:
>
> On Sun, Sep 24, 2023 at 04:10:00PM +0100, Ronald S. Bultje wrote:
>>
>>
>> I believe the GA should have sole control and ownership over the domain and
>> trademark. I suggested to kindly ask Fabrice to transfer ownership and/or
> On Sep 26, 2023, at 11:14 AM, Anton Khirnov wrote:
>
> From my perspective, the objections to SDR have been largely
> technical,
>From my perspective the objections against the current SDR implementation
>could be grouped into roughly 3 categories:
A) support for taking input from an SDR d
> On Oct 4, 2023, at 7:37 PM, Lynne wrote:
>
> 2048 is just more widely encountered. I'm posting these patches
> to get an opinion:
> - do we cut nothing at all (currently)
> - do we cut 1024 (required by the standard/algorithm, and currently what our
> AAC ENcoder outputs)
> - do we cut 2
> On Jul 16, 2024, at 1:23 PM, Niklas Haas wrote:
>
> From: Niklas Haas
>
> This field is used to signal the compression method in use.
> ---
> doc/APIchanges| 3 +++
> libavutil/dovi_meta.h | 9 +
> libavutil/version.h | 2 +-
> 3 files changed, 13 insertions(+), 1 deletion(-)
> On Jul 16, 2024, at 1:23 PM, Niklas Haas wrote:
>
> From: Niklas Haas
>
> ---
> fftools/ffprobe.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fftools/ffprobe.c b/fftools/ffprobe.c
> index 0b7d4ce0d7..265718467f 100644
> --- a/fftools/ffprobe.c
> +++ b/fftools/ffprobe.c
> @@ -26
> On Jul 16, 2024, at 1:23 PM, Niklas Haas wrote:
>
> From: Niklas Haas
>
> ---
> libavformat/dovi_isom.c | 19 +--
> 1 file changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/libavformat/dovi_isom.c b/libavformat/dovi_isom.c
> index d49aa5a75f..269374cff9 100644
> ---
> On Jul 16, 2024, at 1:23 PM, Niklas Haas wrote:
>
> From: Niklas Haas
>
> ---
> libavformat/mpegts.c | 8 ++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/libavformat/mpegts.c b/libavformat/mpegts.c
> index c66a1ea6ed..6b02187eb1 100644
> --- a/libavformat/mpegts.
> On Jul 16, 2024, at 1:23 PM, Niklas Haas wrote:
>
> From: Niklas Haas
>
> ---
> libavformat/dump.c | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/libavformat/dump.c b/libavformat/dump.c
> index 78b2481d90..5e1f367742 100644
> --- a/libavformat/dump.c
> +++ b/
> On Jul 16, 2024, at 4:58 PM, Zhao Zhili wrote:
>
>
>
>> On Jul 16, 2024, at 21:20, Matthieu Bouron wrote:
>>
>> On Wed, Jul 10, 2024 at 6:31 PM Matthieu Bouron
>> wrote:
>>>
>>> On Wed, Jul 10, 2024 at 4:04 PM Zhao Zhili wrote:
> On Jun 12, 2024, at 21:42, Matthieu Bour
1 - 100 of 125 matches
Mail list logo
