Hi,
On Fri, May 17, 2024 at 9:50 AM Michael Niedermayer
wrote:
> * Fund professional real live presence on multimedia / FOSS / buisness
> related
> events. we already refund individuals but i think we are lacking on the
> organizational
> side. We should also have on these events at least on
Hi,
On Tue, May 14, 2024 at 4:40 PM Stone Chen wrote:
> Implements AVX2 DMVR (decoder-side motion vector refinement) SAD
> functions. DMVR SAD is only calculated if w >= 8, h >= 8, and w * h > 128.
> To reduce complexity, SAD is only calculated on even rows. This is
> calculated for all video bi
Hi,
On Fri, May 17, 2024 at 11:59 PM Michael Niedermayer
wrote:
> Fixes: CID1507483 Unchecked return value
>
> Sponsored-by: Sovereign Tech Fund
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/vp8.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/libavcodec/v
Hi,
On Tue, May 14, 2024 at 4:40 PM Stone Chen wrote:
> +vvc_sad_8:
> +.loop_height:
> +movu xm0, [src1q]
> +movu xm1, [src2q]
> +MIN_MAX_SAD xm2, xm0, xm1
> +vpmovzxwd m1, xm1
> +vpaddd m3,
Hi,
This is mostly good, the following is tiny nitpicks.
On Sun, May 19, 2024 at 8:46 PM Stone Chen wrote:
> +%macro INIT_OFFSET 6 ; src1, src2, dxq, dyq, off1, off2
>
The macro is only used once, so you could inline it in the calling function.
>
> +imul%5, 128
> +imul
Hi,
one more, I forgot.
On Sun, May 19, 2024 at 8:46 PM Stone Chen wrote:
> +pw_1: dw 1
>
[..]
> +vpbroadcastw m4, [pw_1]
>
We typically suggest to use vpbroadcastd, not w (and then pw_1: times 2 dw
1). agner shows that on e.g. Haswell, the former (d) is 1 uops with 5
cycles latency
Hi,
On Sun, May 19, 2024 at 8:55 PM Stone Chen wrote:
> Adds checkasm for DMVR SAD AVX2 implementation.
>
> Benchmarks ( AMD 7940HS )
> vvc_sad_8x8_c: 70.0
> vvc_sad_8x8_avx2: 10.0
> vvc_sad_16x16_c: 280.0
> vvc_sad_16x16_avx2: 20.0
> vvc_sad_32x32_c: 1020.0
> vvc_sad_32x32_avx2: 70.0
> vvc_sad_
Hi,
On Tue, May 21, 2024 at 8:01 PM Stone Chen wrote:
> Implements AVX2 DMVR (decoder-side motion vector refinement) SAD
> functions. DMVR SAD is only calculated if w >= 8, h >= 8, and w * h > 128.
> To reduce complexity, SAD is only calculated on even rows. This is
> calculated for all video bi
Hi,
On Tue, May 21, 2024 at 8:01 PM Stone Chen wrote:
> Adds checkasm for DMVR SAD AVX2 implementation.
>
> Benchmarks ( AMD 7940HS )
> vvc_sad_8x8_c: 50.3
> vvc_sad_8x8_avx2: 0.3
> vvc_sad_16x16_c: 250.3
> vvc_sad_16x16_avx2: 10.3
> vvc_sad_32x32_c: 1020.3
> vvc_sad_32x32_avx2: 60.3
> vvc_sad_6
Hi,
On Wed, May 22, 2024 at 10:36 AM Hendrik Leppkes
wrote:
> On Thu, Feb 29, 2024 at 7:19 AM llyyr wrote:
> >
> > segmentation.update_map is never reset to 0 on a new frame, and retains
> > the value from the previous frame. This bugs out a bunch of hwaccel
> > drivers when segmentation.enable
Hi,
On Wed, May 22, 2024 at 1:28 PM Hendrik Leppkes wrote:
> On Wed, May 22, 2024 at 7:16 PM Lynne via ffmpeg-devel
> wrote:
> > I'd hate to apply fixes with no information in shared code. This can get
> > removed with no information about what relies on it.
>
> Changing 5 different hwaccel mod
Hi,
On Fri, May 24, 2024 at 7:39 AM Andrey Turkin
wrote:
> Have to say, this issue has been a long grievance of mine. There is no
> reason to delay frames when the decoder is set up to ignore B frames
> as there is no reordering to be done
>
Frame threading?
Ronald
Hi,
On Wed, May 29, 2024 at 11:38 AM wrote:
> +%else
> +vpunpcklqdq m11, m2, m2
> +vpunpckhqdq m12, m2, m2
> +vpunpcklwd m11, m11, m14
> +vpunpcklwd m12, m12, m14
> +paddd m0, m11
> +paddd m1, m12
> +packssdw m0,
Hi,
On Wed, May 29, 2024 at 3:44 PM Wu Jianhua wrote:
> Ronald S. Bultje:
> > On Wed, May 29, 2024 at 11:38 AM toq...@outlook.com>> wrote:
> > +%else
> > +vpunpcklqdq m11, m2, m2
> > +vpunpckhqdq m12, m2, m2
> > +vpunpcklwd
Hi,
On Thu, May 30, 2024 at 12:28 PM wrote:
> From: Wu Jianhua
>
> Some tests fails with certain seeds
>
> tests/checkasm/checkasm 2325607578 --test=vvc_alf
> checkasm: using random seed 2325607578
> AVX2:
> vvc_alf_filter_luma_120x20_12_avx2 (vvc_alf.c:104)
> vvc_alf_filter_luma_120x24
Hi Andreas,
On Thu, May 30, 2024 at 2:33 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> toq...@outlook.com:
> > From: Wu Jianhua
> >
> > Some tests fails with certain seeds
> >
> > tests/checkasm/checkasm 2325607578 --test=vvc_alf
> > checkasm: using random seed 2325607578
> >
Hi,
On Thu, May 30, 2024 at 10:03 AM Tomas Härdin wrote:
> tor 2024-05-30 klockan 16:06 +0300 skrev Rémi Denis-Courmont:
> >
> >
> > Le 30 mai 2024 12:50:05 GMT+03:00, "Tomas Härdin" a
> > écrit :
> > > tor 2024-05-30 klockan 10:54 +0300 skrev Rémi Denis-Courmont:
> > > > Can't we just use the
Hi,
On Sun, Jun 2, 2024 at 9:12 AM James Almer wrote:
> On 6/2/2024 10:06 AM, James Almer wrote:
> > On 6/2/2024 9:14 AM, Kacper Michajłow wrote:
> >> Fixes runtime error: member access within misaligned address
> >> for type 'av_alias64', which requires 8 byte alignment.
> >>
> >> VP9mv is ali
Hi,
On Sun, Jun 2, 2024 at 6:43 PM Kacper Michajlow wrote:
> On Sun, 2 Jun 2024 at 23:17, Ronald S. Bultje wrote:
> >
> > Hi,
> >
> > On Sun, Jun 2, 2024 at 9:12 AM James Almer wrote:
> >
> > > On 6/2/2024 10:06 AM, James Almer wrote:
> >
Hi,
On Mon, Jun 3, 2024 at 12:14 PM Zhao Zhili wrote:
>
>
> > On Jun 3, 2024, at 22:17, Rémi Denis-Courmont wrote:
> >
> > Le maanantaina 3. kesäkuuta 2024, 16.11.15 EEST Zhao Zhili a écrit :
> >>> See https://github.com/mstorsjo/FFmpeg/actions/runs/9346228714 for one
> >>> example run of these
Hi all,
Anton resigned from the CC [1], leaving an empty spot. The remaining
members of the CC agreed it would be best to fill the spot with the next
runner-up from the last CC Elections. The last CC election results [2] had
Steven Liu as next runner-up, so we've asked him to fill Anton's spot for
Hi,
On Wed, Jun 5, 2024 at 9:44 AM Andrew Sayers
wrote:
> On Wed, Jun 05, 2024 at 03:34:50PM +0200, Paul B Mahol wrote:
> > On Wed, Jun 5, 2024 at 3:18 PM Andrew Sayers <
> ffmpeg-de...@pileofstuff.org>
> > wrote:
> >
> > > An external API developer might think they can use AVOptions to modify
>
Hi,
On Mon, Jun 10, 2024 at 3:20 PM Rémi Denis-Courmont wrote:
> Although checkasm does not verify this, the decoder requires that the
> transform updates the input block exactly like the C code does.
>
Would it be possible to update the checkasm test to verify this?
Ronald
___
Hi Thomas,
On Fri, Oct 29, 2021 at 9:12 AM Tomas Härdin wrote:
> tor 2021-10-28 klockan 21:09 +0200 skrev Paul B Mahol:
> > +const uint16_t *src = (const uint16_t *)ssrc;
>
> This is not -fstrict-aliasing safe
>
I don't believe that is correct. It's true we're not allowed to cast
between tw
Hi,
On Sat, Oct 30, 2021 at 4:57 AM Tomas Härdin wrote:
> Maybe we should upgrade to C11 then? This gives us access to more
> useful language features. Type-generic expressions look very useful
>
https://stackoverflow.com/a/7005988 (same thread, further down) appears to
suggest the exact same l
Hi,
On Fri, Nov 26, 2021 at 4:52 PM John-Paul Stewart <
jpstew...@personalprojects.net> wrote:
> There were no single channel examples and no 8 bit
> examples.
>
> I have created four clips with SGI's original 'moviemaker' utility (so
> they are guaranteed to be correctly formatted) to reverse en
Hi John-Paul,
On Sat, Nov 27, 2021 at 8:22 PM John-Paul Stewart <
jpstew...@personalprojects.net> wrote:
> On 2021-11-27 8:51 a.m., Ronald S. Bultje wrote:
> > Hi,
> >
> > On Fri, Nov 26, 2021 at 4:52 PM John-Paul Stewart <
> > jpstew...@personalprojects.net&g
Hi,
On Sat, Oct 14, 2023 at 11:16 AM Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> On Sat, Oct 14, 2023 at 9:11 AM Lynne wrote:
> > colorspace doesn't make it impossible to introduce all that is needed.
> > It's a cleaner codebase that we can extend.
>
> * that only works on a subset o
Hi,
On Fri, Oct 20, 2023 at 12:14 PM Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> tbh while it's great that this functionality exists *somewhere* in ffmpeg,
> this is really something that should belong to the scaler filter (whichever
> implementation)
>
I agree. The reason this was d
Hi,
On Thu, Oct 26, 2023 at 11:45 AM Michael Niedermayer
wrote:
> 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 communi
Hi Thilo,
On Sat, Oct 28, 2023 at 11:31 AM Thilo Borgmann via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> What this is about, is to set up a way to properly spend the SPI money
> aside
> from travel & hw. Why we should not do it because some companies
> beurocracy, I
> cannot see.
>
I since
Hi Nicolas,
On Sun, Oct 29, 2023 at 12:47 PM Nicolas George wrote:
> Rémi Denis-Courmont (12023-10-29):
> > And unfortunately, I do believe that Ronald is correct in pointing out
> > that big companies will want oversight in exchange for money.
>
> And this is why the only acceptable answer is:
On Sun, Oct 29, 2023 at 3:46 PM Nicolas George wrote:
> Ronald S. Bultje (12023-10-29):
> > *You* may well end up not accepting their offered help, and that's your
> > call to make. But if others in our community end up accepting their
> offered
> > help, there&#x
Hi,
On Sun, Nov 5, 2023 at 4:24 AM Anton Khirnov wrote:
> Please suggest candidates in replies to this email, with a short
> description of how they contribute to the project.
>
Myself, please. I currently maintain the VP8/VP9 decoders and sometimes
review AV1-related work also, although James
Hi,
On Sun, Nov 5, 2023 at 6:25 PM James Almer wrote:
> On 11/5/2023 4:57 PM, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Sun, Nov 5, 2023 at 4:24 AM Anton Khirnov wrote:
> >
> >> Please suggest candidates in replies to this email, with a short
> >&
Hi,
On Sun, Nov 5, 2023 at 7:56 PM Dai, Jianhui J <
jianhui.j.dai-at-intel@ffmpeg.org> wrote:
> This commit adds support for VP8 bitstream read methods to the cbs
> codec. This enables the trace_headers bitstream filter to support VP8,
> in addition to AV1, H.264, H.265, and VP9. This can be
Hi,
On Sun, Nov 5, 2023 at 11:13 PM Dai, Jianhui J <
jianhui.j.dai-at-intel@ffmpeg.org> wrote:
> > > +static const uint8_t vp8_token_update_probs[4][8][3][11] = {
> >
> > It would be nice if these symbols could be re-used from the existing vp8
> > native decoder, instead of duplicating them?
Hi,
On Mon, Nov 6, 2023 at 7:07 AM Ronald S. Bultje wrote:
> On Sun, Nov 5, 2023 at 11:13 PM Dai, Jianhui J <
> jianhui.j.dai-at-intel@ffmpeg.org> wrote:
>
>> > > +static const uint8_t vp8_token_update_probs[4][8][3][11] = {
>> >
>> > It would b
Hi,
On Tue, Nov 7, 2023 at 12:01 AM Dai, Jianhui J <
jianhui.j.dai-at-intel@ffmpeg.org> wrote:
>
>
> > -Original Message-
> > From: ffmpeg-devel On Behalf Of
> > Ronald S. Bultje
> > Sent: Monday, November 6, 2023 8:08 PM
> > To: FFmpeg
Hi Jianhui,
On Tue, Nov 7, 2023 at 8:52 PM Dai, Jianhui J <
jianhui.j.dai-at-intel@ffmpeg.org> wrote:
> The smaller delta patch to export the variable:
> https://patchwork.ffmpeg.org/project/ffmpeg/patch/dm6pr11mb268186349e600824e1577dfdb1...@dm6pr11mb2681.namprd11.prod.outlook.com/
> Persona
Hi,
On Wed, Nov 8, 2023 at 10:55 AM Ronald S. Bultje wrote:
> Hi Jianhui,
>
> On Tue, Nov 7, 2023 at 8:52 PM Dai, Jianhui J <
> jianhui.j.dai-at-intel@ffmpeg.org> wrote:
>
>> The smaller delta patch to export the variable:
>> https://patchwor
Hi,
On Mon, Nov 13, 2023 at 2:55 AM Dai, Jianhui J <
jianhui.j.dai-at-intel@ffmpeg.org> wrote:
> Oh, this is the preceding patch of:
> `[FFmpeg-devel,v6] avcodec/cbs_vp8: Add support for VP8 codec bitstream`
>
> Probably, I need merge these two together.
>
It's ok like this, for me. I'll let
Hi,
On Tue, Nov 14, 2023 at 1:44 PM Nicolas George wrote:
> Nothing prevents their boss from telling them how to vote, even if the
> ballots are secret.
>
How is this not just unsubstantiated FUD? We're discussing concerns that
are randomly thrown in without evidence that they're relevant or re
On Tue, Nov 14, 2023 at 2:28 PM Nicolas George wrote:
> but nobody here knows
>
Unsubstantiated FUD.
Move on.
Ronald
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link ab
Hi,
On Mon, Nov 13, 2023 at 8:43 AM Ronald S. Bultje wrote:
> Hi,
>
> On Mon, Nov 13, 2023 at 2:55 AM Dai, Jianhui J <
> jianhui.j.dai-at-intel@ffmpeg.org> wrote:
>
>> Oh, this is the preceding patch of:
>> `[FFmpeg-devel,v6] avcodec/cbs_vp8: Ad
Hi,
On Sun, Nov 12, 2023 at 8:53 PM Dai, Jianhui J <
jianhui.j.dai-at-intel@ffmpeg.org> wrote:
> TESTS: ffmpeg -i fate-suite/vp8/frame_size_change.webm -vcodec copy
> -bsf:v trace_headers -f null -
>
(I've merged this already.)
I don't think a fate test was added to prevent regressions. Wou
Hi,
On Fri, Nov 24, 2023 at 4:39 AM Paul B Mahol wrote:
> Can not access irc anymore.
>
If my understanding is correct, this was caused by the +r channel mode,
which means your nick needs to be registered with channel services before
you can join the channel.
We (me & Anton, mostly) decided to
Hi,
On Tue, Nov 28, 2023 at 6:58 AM Anton Khirnov wrote:
> There are reports from people on IRC that they got confused by the
> change and voted the reverse of what they meant. Sadly there is no way
> to change your vote after it's been case, so if there is a nontrivial
> number of such people,
Hi,
On Wed, Nov 29, 2023 at 7:01 PM Cosmin Stejerean via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> > 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
> > I
Hi,
On Sun, Dec 3, 2023 at 3:10 PM Timo Rothenpieler
wrote:
> So if the compiler does a copy
> in decode_cpe() with avx instructions, but ffmpeg is built with
> --disable-avx
>
Ehm... What? That seems like the core bug then?
Ronald
___
ffmpeg-devel m
Hi,
On Wed, Dec 6, 2023 at 3:23 AM Marton Balint wrote:
> Signed-off-by: Marton Balint
> ---
> doc/APIchanges | 3 +++
> doc/codecs.texi| 14 ++
> libavcodec/avcodec.h | 4
> libavcodec/decode.c| 6 ++
> libavcodec/options_table.h |
Hi,
On Thu, Dec 7, 2023 at 7:33 AM Michael Niedermayer
wrote:
> On Thu, Dec 07, 2023 at 08:29:14AM +0100, Paul B Mahol wrote:
> > Attached.
>
> > MAINTAINERS | 55
> ---
> > 1 file changed, 55 deletions(-)
> > 57486b662b3460fe6704e2ec236b0cd
Hi Nicolas,
On Tue, Dec 12, 2023 at 1:04 PM Nicolas George wrote:
> But do not expect it to be fixed, they have hated lavd for ever and now
> they have all the control.
>
Your message promotes conspiracy theories ("they have all control", "they
have hated lavd for ever", etc.) and suggests that
Hi,
On Sat, Mar 30, 2019 at 11:04 AM Thilo Borgmann
wrote:
> Am 23.03.19 um 16:11 schrieb Thilo Borgmann:
> > Hi,
> >
> >> FFmpeg has been accepted for CLT 2019 in Chemnitz, Germany!
> >> This "Chemnitzer Linux Tage" will take place on 16th and 17th of March.
> >> You can find more details on th
Hi,
On Fri, Mar 29, 2019 at 12:15 PM Yufei He wrote:
> Hi
>
> This is the fixed version of this patch that follows the way other
> companies do on supporting FFmpeg.
I would like to propose that we delay further consideration of this patch
until Thilo has organized the vote [1] on whether we w
Hi,
On Sat, Apr 6, 2019 at 12:42 PM Balint Marton wrote:
> Hi All
>
> Here is a call for the people in the voting committee [1] on the decision
> of extending it.
>
> Using the same guidelines as in the second extension [2], the following
> candidates were found:
>
> git log libav/master..master
Hi,
On Sun, Apr 28, 2019 at 8:14 PM Marton Balint wrote:
> On Sun, 28 Apr 2019, Jean-Baptiste Kempf wrote:
> > On Mon, 29 Apr 2019, at 00:23, Marton Balint wrote:
> >> >> On Sun, 28 Apr 2019, at 22:02, Marton Balint wrote:
> >> >>> 2) Should patches using closed source libraries which are not
>
Hi,
On Mon, Apr 29, 2019 at 10:03 PM Yan Cen wrote:
> From: Yan Cen
>
> There is no need all reference frame demension is valid in libvpx.
I think you're touching on a bigger issue here: libvpx allows having
invalid (or even missing) references, and we don't. Note that this means we
lack per-
Hi,
On Sun, Apr 28, 2019 at 4:02 PM Marton Balint wrote:
> Hi All,
>
> There has been discussion on the mailing list several times about the
> inclusion of support for closed source components (codecs, formats,
> filters, etc) in the main ffmpeg codebase.
>
> Also the removal of libNDI happened
Hi,
On Sun, May 19, 2019 at 7:05 PM Yan Cen wrote:
> From: yancen
>
> There is no need all reference frame demension is valid in libvpx.
>
> So this change contains three part:
> 1. Change each judgement's loglevel from "ERROR" to "WARNING"
> 2. Make sure at least one of frames that this frame
Hi,
On Wed, May 22, 2019 at 2:12 AM Yan, CenX wrote:
> Hi, Ronald
>
>
>
> Sorry to reply late.
>
>
>
> For you question, “we lack per-block reference validity checks in the
> block reconstruction code”, would you mean encode process need validity
> checks?
>
No. The decoder needs validity check
Hi guys,
On Wed, May 22, 2019 at 11:14 PM 严小复 wrote:
> code”, I'm little confused about the red word,would you mean encode process
> need validity checks or there need to check the reference id of each frame?
>
> And this patch will act on decode process, all references have already been
> appoi
Hi,
On Mon, Jul 8, 2019 at 6:23 PM Yan Cen wrote:
> From: yancen
>
> There is no need all reference frame demension is valid in libvpx.
>
Haven't we discussed this before? Anyway, it seems you're really eager to
get this in, so I'll drop my objection. (I still think this could cause
issues in
Hi,
On Tue, Jul 9, 2019 at 7:22 AM Ronald S. Bultje wrote:
> Hi,
>
> On Mon, Jul 8, 2019 at 6:23 PM Yan Cen wrote:
>
>> From: yancen
>>
>> There is no need all reference frame demension is valid in libvpx.
>>
>
> Haven't we discussed this before
Hi,
On Tue, Dec 4, 2018 at 4:56 PM Martin Vignali
wrote:
> Le mar. 4 déc. 2018 à 16:12, Jean-Baptiste Kempf a
> écrit :
>
> > But then, you will get absolutely all the integration from ALL the
> various
> > non-open source multimedia libraries, because it is useful to someone.
> > Including shim
Hi,
On Tue, Mar 17, 2020 at 10:59 AM Linjie Fu wrote:
> With the description in frame size with refs semantics (SPEC 7.2.5),
> it is a requirement of bitstream conformance that for at least one
> reference frame has the valid dimensions.
>
> Modify the check to make sure the decoder works well i
Hi,
On Sat, Apr 18, 2020 at 6:15 AM Anton Khirnov wrote:
> ---
> libavcodec/vp9.c | 36
> 1 file changed, 16 insertions(+), 20 deletions(-)
ok.
Ronald
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https:
---
libavformat/ivfenc.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/libavformat/ivfenc.c b/libavformat/ivfenc.c
index 0951f56..e22625b 100644
--- a/libavformat/ivfenc.c
+++ b/libavformat/ivfenc.c
@@ -23,7 +23,7 @@
typedef struct IVFEncContext {
unsigned
Hi,
On Tue, Mar 2, 2021 at 11:20 AM Andreas Rheinhardt <
andreas.rheinha...@gmail.com> wrote:
> Ronald S. Bultje:
> > ---
> > libavformat/ivfenc.c | 11 ---
> > 1 file changed, 8 insertions(+), 3 deletions(-)
> >
> > diff --git a/libavformat/iv
---
libavformat/ivfenc.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/libavformat/ivfenc.c b/libavformat/ivfenc.c
index 0951f56..889c004 100644
--- a/libavformat/ivfenc.c
+++ b/libavformat/ivfenc.c
@@ -23,7 +23,7 @@
typedef struct IVFEncContext {
unsigned
Hi,
On Tue, Mar 2, 2021 at 1:59 PM Andreas Rheinhardt <
andreas.rheinha...@gmail.com> wrote:
> Ronald S. Bultje:
> > ---
> > libavformat/ivfenc.c | 10 +++---
> > 1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/libavformat/iv
Hi,
On Wed, Apr 29, 2020 at 8:08 AM Fu, Linjie wrote:
> > From: ffmpeg-devel On Behalf Of Fu,
> > Linjie
> > Sent: Friday, March 20, 2020 09:49
> > To: Ronald S. Bultje ; FFmpeg development
> > discussions and patches
> > Subject: Re: [FFmpeg-devel] [PATC
Hi,
On Sat, Jun 13, 2020 at 12:11 PM Kieran Kunhya wrote:
> Hello,
>
> I have run the following commands on the following CPU which is 7 years
> old:
> Intel(R) Xeon(R) CPU E3-1265L v3
>
> ffmpeg_g -i matrixbench_mpeg2.mpg -f null -
> and
> ffmpeg_g -flags2 fast -i matrixbench_mpeg2.mpg -f null
Hi,
On Sat, Sep 21, 2019 at 10:07 AM Nicolas George wrote:
> Carl Eugen Hoyos (12019-09-21):
> > I now wonder if this isn't much nicer than "You may use this FDK AAC
> > Codec software or modifications thereto only for purposes that are
> > authorized by appropriate patent licenses."
> > (In the
Hi,
On Sat, Sep 21, 2019 at 11:05 AM Carl Eugen Hoyos
wrote:
> Am Sa., 21. Sept. 2019 um 16:51 Uhr schrieb Ronald S. Bultje
> :
>
> > So it appears, from the discussion (..), that although there is source
> > code, it is not actually "open" in the sense that it&
Hi,
On Sat, Sep 21, 2019 at 11:53 AM Ronald S. Bultje
wrote:
> Hi,
>
> On Sat, Sep 21, 2019 at 11:05 AM Carl Eugen Hoyos
> wrote:
>
>> Am Sa., 21. Sept. 2019 um 16:51 Uhr schrieb Ronald S. Bultje
>> :
>>
>> > So it appears, from the discussion (..), t
Hi,
On Mon, Nov 11, 2019 at 9:17 PM James Almer wrote:
> +static int leb(AVIOContext *pb, uint32_t *len) {
>
this can overflow, should be uint64_t.
> +unsigned bits;
>
Same.
Ronald
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
htt
Hi,
On Tue, Nov 12, 2019 at 8:09 AM James Almer wrote:
> On 11/12/2019 2:52 AM, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Mon, Nov 11, 2019 at 9:17 PM James Almer wrote:
> >
> >> +static int leb(AVIOContext *pb, uint32_t *len) {
> >>
&
Hi,
On Wed, Nov 13, 2019 at 2:00 AM wrote:
> From: Zhao Zhili
>
> vp7 decoder doesn't set update_thread_context field
> ---
> libavcodec/vp8.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/libavcodec/vp8.c b/libavcodec/vp8.c
> index eb51d1f3c9..b4deb3ed67 100644
>
Hi,
On Thu, Nov 14, 2019 at 2:12 PM Andrey Semashev
wrote:
> I think there needs to be some consistency across different lavc
> decoders. If we consider that lavc should produce one decoded frame per
> one encoded one, even if the encoded one contains multiple layers, then
> that should be true
Hi,
On Fri, Nov 15, 2019 at 1:44 PM James Almer wrote:
> Signed-off-by: James Almer
> ---
> libavcodec/cbs_av1_syntax_template.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavcodec/cbs_av1_syntax_template.c
> b/libavcodec/cbs_av1_syntax_template.c
> index 80
Hi,
On Wed, Nov 27, 2019 at 3:28 PM Sebastian Pop wrote:
> On Wed, Nov 27, 2019 at 2:13 PM Clément Bœsch wrote:
> > Yeah I will by the end of the week. I wrote that a few years ago so I
> need
> > to take some time to get back in the context.
>
> Thanks Clément for your help.
>
> >
> > BTW, tha
Hi,
On Thu, Nov 28, 2019 at 2:08 AM Ronald S. Bultje wrote:
> Hi,
>
> On Wed, Nov 27, 2019 at 3:28 PM Sebastian Pop wrote:
>
>> On Wed, Nov 27, 2019 at 2:13 PM Clément Bœsch wrote:
>> > Yeah I will by the end of the week. I wrote that a few years ago so I
>> n
Dear all,
below are the notes I took of the 2019/12/9 FFmpeg developer meeting. The
meeting was held on a Google Meet, and there was an IRC proxy channel
(#ffmpeg-meeting) also.
Kind regards,
Ronald
- jb opens, agenda for this meeting
o what happened at last meeting (at VDD)
o various next steps
Hi,
On Wed, Dec 11, 2019 at 5:00 PM James Almer wrote:
> Taking into account the code
>
> fb(2, ar_coeff_lag);
> num_pos_luma = 2 * current->ar_coeff_lag * (current->ar_coeff_lag + 1);
> if (current->num_y_points)
> num_pos_chroma = num_pos_luma + 1;
> else
> num_pos_chroma = num_pos_lum
Hi,
On Sat, Jan 18, 2020 at 9:49 PM Fu, Ting wrote:
> Since NASM function will get only the address of SwsConext c ( in order to
> be compatible with yuv2rgb_c function in parameters), not the address of
> c->redDither nor the c->dstW. I have no way to get the value of c->dstW by
> using address
Hi,
On Thu, Feb 13, 2020 at 10:41 PM Guo, Yejun wrote:
> For some cases, the regions of interest do not change, it is not
> convenient to always prepare the roi data for every frame.
Since side-data is refcounted, can't you just keep the "last" one in memory
and refcount it? That way, if you w
Hi,
On Sun, Jun 6, 2021 at 10:42 PM James Almer wrote:
> From: Matthieu Patou
>
> The function name iszero() may collide with a function in glibc.
>
> Suggested-by: ffm...@fb.com
> Signed-off-by: James Almer
> ---
> tests/checkasm/vp9dsp.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 dele
Hi Alan,
On Mon, Jun 14, 2021 at 7:20 AM Alan Kelly <
alankelly-at-google@ffmpeg.org> wrote:
> Broadwell and later have fast gather instructions.
> ---
> This is so that the avx2 version of ff_hscale8to15X which uses gather
> instructions is only selected on machines where it will actually
Hi Alan,
On Fri, Jun 25, 2021 at 3:59 AM Alan Kelly <
alankelly-at-google@ffmpeg.org> wrote:
> These functions replace all ff_hscale8to15_*_ssse3 when avx2 is available.
>
Re-asking a question I asked before in the other thread:
Also, what is the cycle count of ssse3/avx2 implementation for
Hi Alan,
On Fri, Jun 25, 2021 at 7:53 AM Alan Kelly wrote:
>
>
> On Fri, Jun 25, 2021 at 1:26 PM Ronald S. Bultje
> wrote:
>
>> Hi Alan,
>>
>> On Fri, Jun 25, 2021 at 3:59 AM Alan Kelly <
>> alankelly-at-google@ffmpeg.org> wrote:
>>
>
Hi Lauri,
On Mon, Jan 7, 2019 at 3:15 AM Lauri Kasanen wrote:
> If you were to design a video codec for a very low-end decoder, what
> would it look like?
>
Have you considered vp8? It may sound weird but this is basically what vp8
was great at: being really simple to decode.
Ronald
__
Hi,
On Mon, Jan 7, 2019 at 12:22 PM Lauri Kasanen wrote:
> On Mon, 7 Jan 2019 12:02:58 -0500
> "Ronald S. Bultje" wrote:
>
> > Have you considered vp8? It may sound weird but this is basically what
> vp8
> > was great at: being really simple to decode.
>
Hi,
On Thu, Jan 10, 2019 at 2:41 PM Carl Eugen Hoyos wrote:
> 2019-01-07 18:37 GMT+01:00, Ronald S. Bultje :
> > Hi,
> >
> > On Mon, Jan 7, 2019 at 12:22 PM Lauri Kasanen wrote:
> >
> >> On Mon, 7 Jan 2019 12:02:58 -0500
> >> "Ronald S. Bultj
Hi,
On Sun, Jan 13, 2019 at 4:39 AM Gyan wrote:
> When someone submits a patch, it is implicit, unless stated otherwise,
> that it is of their own initiative (and their own work), and thus they
> are free to assign copyright. When work is performed for hire, the
> copyright may belong to the emp
On Sun, Jan 13, 2019 at 9:38 AM Nicolas George wrote:
> Derek Buitenhuis (12019-01-13):
> > This is a policy change, not a techncal change.
>
> Policy changes need to be motivated too.
>
Wait, what? *You* are suggesting a policy change, not me/us. There is no
burden of proof on me. You have to c
Hi,
On Mon, Jan 14, 2019 at 11:13 AM Nicolas George wrote:
> Ronald S. Bultje (12019-01-13):
> > Wait, what? *You* are suggesting a policy change, not me/us. There is no
> > burden of proof on me. You have to convince me (and us) that your problem
> > is important and you
Hi Pranap,
On Sat, Feb 16, 2019 at 11:43 AM Pranav Nutalapati <
pranavnutalap...@gmail.com> wrote:
> I’ve been trying to compile ffmpeg with NDI support on macOS and kept on
> running into the error
>
> ld: library not found for -lndi
>
> when compiling. Having no experience with compiling th
Hi Pranav,
On Sat, Feb 16, 2019 at 9:14 PM Pranav Nutalapati <
pranavnutalap...@gmail.com> wrote:
> Okay, so it’s a problem with my personal installation of NDI?
>
Yes.
Ronald
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mai
Hi,
On Sat, Mar 9, 2019 at 4:02 PM Martin Vignali
wrote:
> They have not responded to any communications:
> > https://trac.ffmpeg.org/ticket/7589
> >
> >
> I still do not understand the link between the ticket and the removal of
> lib ndi.
> Is it plan to remove all features used by people who d
1 - 100 of 2074 matches
Mail list logo
