Le 3 août 2025 14:41:53 GMT+07:00, Michael Niedermayer
a écrit :
>Hi
>
>can we have a tag that causes "automerge on approve" ?
>
>so that if i open a pr i can set that tag and if someone approves it, its
>merged and i dont have to come back and click that button ?
IMO, merging should be an exp
Le 26 juillet 2025 23:14:08 GMT+03:00, Timo Rothenpieler
a écrit :
>> You do it once, decisively, with no point where it is both dev paths
>> simultaniously.
>> VideoLAN managed it, and countless companies and other projects have managed
>> it with
>> no overlap. Many of which I have experien
Le perjantaina 25. heinäkuuta 2025, 14.41.05 Itä-Euroopan kesäaika Nicolas
George a écrit :
> In short and imaged, I see you arguing that screws are too difficult to
> use and we should use twisted vines instead, but the real issue is that
> you are using a Playskool Plastic Tool Set instead of a
Le 30 juillet 2025 00:42:41 GMT+03:00, Romain Beauxis
a écrit :
>Hi all,
>
>Are there any recommendations on how to best get attention to some
>patches/changes?
>
>With the introduction of the new forgejo workflow (which I personally
>welcome!), I am wondering how casual contributors like mysel
G
but some people may not be comfortable voting in public like that.
___
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
Hi,
I'm aware that this patch is being held an inappropriate amount of time
waiting for review, but as I said before, I have NO experience dealing with
such a large transform, and I am kinda busy.
Note that I don't really see the point in specialising the code by VLEN.
Properly designed hardwa
Le tiistaina 1. heinäkuuta 2025, 13.58.23 Itä-Euroopan kesäaika Alexander
Strasser via ffmpeg-devel a écrit :
> (...) I want this thread to start a discussion, that eventually leads
> to a policy about submitting and integrating "AI" generated content.
Well, you can define a policy and/or make a
Le sunnuntai 29. kesäkuuta 2025, 14.04.38 Itä-Euroopan kesäaika Kacper
Michajlow a écrit :
> I made a quick experiment and while there are things to improve/fix, I
> don't see _Generic being one of those issues.
> https://code.ffmpeg.org/kasper93/FFmpeg/commit/0cf27668aa3496bb7e5f45c08e88a
> 03798
n
spite of the pointer values. The problem is, at that point, some FFmpeg
sources caused GCC to crash on OOM.
I don't know what else I can add.
--
Rémi Denis-Courmont
Tapiolan uusi kaupunki, Uudenmaan entinen Suomen tasavalta
___
ffmpeg-devel mai
Le lauantaina 28. kesäkuuta 2025, 17.35.17 Itä-Euroopan kesäaika Kacper
Michajlow a écrit :
> On Mon, 2 Jun 2025 at 17:06, Rémi Denis-Courmont wrote:
> > Le 31 mai 2025 20:40:40 GMT+03:00, Marton Balint a écrit :
> > >On Sat, 31 May 2025, Michael Niedermayer wrote:
> >
sh single and double, and risk accidentally down- or up-converting.
In any case, thanks for working on this.
--
Rémi Denis-Courmont
Tapio's place new town, former Finnish Republic of Uusimaa
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
ht
redistributors, as it would become too difficult and/or risky to distinguish
what is and what is not LGPL-compatible.
At the same time, I expect that this proposal pissed Paul off, and merging
would piss him off even harder. So I don't really see the point in this effort:
pissing Paul off, upset
Le tiistaina 3. kesäkuuta 2025, 20.07.18 Itä-Euroopan kesäaika softworkz . a
écrit :
> Given the preceding conversations, it is pretty safe to assume
> that these comments are based on personal sentiments rather than
> technical expertise.
I won't deny the fact that several people have raised no
Le 3 juin 2025 19:15:57 GMT+03:00, Niklas Haas a écrit :
>On Mon, 02 Jun 2025 15:41:33 -0300 James Almer wrote:
>> GCC/Clang is smart enough to emit minss/maxss the same way as these
>> functions.
>> The only theoretical benefit was in x86_32, where x87 floats are used, but
>> the
>> penalty
Le 3 juin 2025 19:14:16 GMT+03:00, Niklas Haas a écrit :
>We have an open bug in swscale on 32-bit platforms where the use of x87 causes
>non-bitexact results in 32-bit platforms, resolved by setting -mfpu=sse at
>build time.
>
>Maybe we should think about setting this flag globally?
Enabling S
else {
> +av_bprintf(&bp, "[%s]", host);
> +}
> +} else {
> +// Host is not an IPv6 address, so just use as-is
> +av_bprintf(&bp, "%s", host);
> +}
This looks like reverse abstraction and kinda sketchy. Ho
Le perjantaina 30. toukokuuta 2025, 10.40.45 Itä-Euroopan kesäaika
daichengr...@iscas.ac.cn a écrit :
> From: daichengrong
>
> On Banana PI F3:
> hevc_idct_32x32_8_c:118807.4 (
> 1.00x) hevc_idct_32x32_8_rvv_i64: 13853.3 (
> 8.58x
Hi,
On that note, we should keep in mind that FFmpeg also uses (or abuses) FFMIN
and FFMAX for pointer arithmetic. It feels a bit of an abuse to refer to
pointers as integers.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mai
Hi,
>If paul wants them to be GPL he can change these headers at any time.
I agree with your implication that Paul *should* have modified the license
headers either globally or as he modified files.
But that does not make the top-level license statement moot.
>And the "explicit license notice
Le 31 mai 2025 20:40:40 GMT+03:00, Marton Balint a écrit :
>
>
>On Sat, 31 May 2025, Michael Niedermayer wrote:
>
>> This allows adjusting them to exactly match whatever is fastest on
>> a given CPU for each type.
>
>Did you use some tool to make this patch, or it was just manual work?
>
>Can't
Le 29 mai 2025 19:02:24 GMT+03:00, Michael Niedermayer
a écrit :
>can gcc or clang not build code like our runtime cpudetect ?
You can, on some versions and some architectures, select the target CPU per
function, but you can't select multiple targets, nor have the compiler
automatically sele
Le 30 mai 2025 03:46:05 GMT+03:00, Michael Niedermayer
a écrit :
>On Mon, May 26, 2025 at 11:43:15AM +0300, Rémi Denis-Courmont wrote:
>>
>>
>> Le 26 mai 2025 00:37:08 GMT+03:00, Michael Niedermayer
>> a écrit :
>> >Hi Rémi
>> >
>> &g
Hi,
Whatever glibc does or doesn't do is kinda irrelevant. FFmpeg is supposed to be
portable and that makes `system()` a non-starter given how bad it *can* be.
With that said, and with my CC hat on, if you would consider a portably safer
alternative, I can only say that considering what strong
Hi,
Le 26 mai 2025 12:27:17 GMT+03:00, "softworkz ."
a écrit :
>
>
>> -Original Message-
>> From: ffmpeg-devel On Behalf Of Rémi Denis-
>> Courmont
>> Sent: Montag, 26. Mai 2025 10:01
>> To: FFmpeg development discussions and patches
Hi,
Le 25 mai 2025 22:22:52 GMT+03:00, Michael Niedermayer
a écrit :
>Note the license of this code is a bit wonky. The files have one
>license and theres another one in LICENSE.md.
>While I belives legally this allows one to choose either. I suggest
>you check this with a lawyer.
You do realis
Le 26 mai 2025 00:37:08 GMT+03:00, Michael Niedermayer
a écrit :
>Hi Rémi
>
>On Sat, May 24, 2025 at 07:10:57PM +0300, Rémi Denis-Courmont wrote:
>> Le torstaina 22. toukokuuta 2025, 9.32.18 Itä-Euroopan kesäaika Jiawei a
>> écrit
>> :
>> > > The RIS
Le perjantaina 23. toukokuuta 2025, 17.53.02 Itä-Euroopan kesäaika Timothy
Allen via ffmpeg-devel a écrit :
> This commit closes trac ticket 10679.
>
> Signed-off-by: Timothy Allen
> ---
> libavformat/hls.c | 9 +
> libavformat/url.c | 35 +++
> libavfor
Le tiistaina 20. toukokuuta 2025, 10.58.06 Itä-Euroopan kesäaika
daichengr...@iscas.ac.cn a écrit :
> From: daichengrong
>
> Since there are no comments for v2 and v3, we have continued to optimize
> according to the comments of v1. We spilled the slide to memory to help
> improve performance,an
Le torstaina 22. toukokuuta 2025, 9.32.18 Itä-Euroopan kesäaika Jiawei a écrit
:
> > The RISC-V autovectorised output looks like it has a warning "Odd
> > rotation angle" which is not present in the non-autovectorised output.
>
> I found this occured when using '-ffast-math' in RISC-V, also occur
Le perjantaina 16. toukokuuta 2025, 3.54.21 Itä-Euroopan kesäaika Michael
Niedermayer a écrit :
> 1. lets all calm down, so far we have a civil and productive discussion
>maybe we can simply find a solution everyone is happy with!
>
> 2. all security issues must be fixed if there are some
sy
Le perjantaina 16. toukokuuta 2025, 1.19.15 Itä-Euroopan kesäaika softworkz .
a écrit :
> of course I understand that.
> But it isn't constructed from untrusted input.
You're being ridiculous. `system()` has a long history of causign bugs, many
of them security related, and many not fixable.
I
Hi,
Le 21 mai 2025 09:17:50 GMT+03:00, Jiawei a écrit :
>This patch modifies the FFmpeg build system to remove the explicit disabling
>of GCC's auto-vectorization feature.
>
>Modern GCC versions (>= 10.0) have demonstrated stable auto-vectorization
>capabilities through extensive optimizations in
Hi,
Le 14 mai 2025 13:55:09 GMT+03:00, Michael Niedermayer
a écrit :
>Simple script to merge all source plugins.
>
>Signed-off-by: Michael Niedermayer
>---
> INSTALL.md | 3 +++
> tools/merge-all-source-plugins | 3 +++
> 2 files changed, 6 insertions(+)
> create mode 100644 t
Hi,
This looks like a kludge to me. If static variables are too far away, then the
assembler code that refers to them needs to be fixed, and that's all that there
is to it.
You can't just magically make the data and the code closer, especially if
FFmpeg is compiled as a static library (a very
Le 6 mai 2025 04:21:58 GMT+03:00, daichengrong a
écrit :
>
>ping~
See comments against v1. No point pinging.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or
Le lauantaina 26. huhtikuuta 2025, 18.10.27 Itä-Euroopan kesäaika Michael
Niedermayer a écrit :
> This is just an announcement that the TC has been asked to look into
> avutil/log: Add log flag to control printing of memory addresses
> GitHub:https://github.com/ffstaging/FFmpeg/pull/59
Le tiistaina 22. huhtikuuta 2025, 7.20.26 Itä-Euroopan kesäaika softworkz . a
écrit :
> Hi Stefano, Andreas, Nicolas
> and of course, anybody who's interested in the AVTextFormat APIs,
>
>
> let me start by saying that I have no intention to rush the
> publicization of those APIs. I think there'
are on Arm or x86. RVV requires spilling to
the intermediate values from the first DCT dimension to memory, to transpose
them before the second DCT dimension. That being the case, the penalty for not
fitting the entire matrix in the vector register bank is comparatively much
smaller.
And yes, please d
Hi,
I answered, but the position of the CC is such that there is nothing we can do
about NG in general.
Suspension will not achieve anything (and in this particular case, seems a bit
heavy-handed), and permanent ban is not something that the CC can do under the
current CoC.
Br,
Le 25 mars 20
Hi,
Le 25 mars 2025 10:55:35 GMT+02:00, Nicolas George a écrit :
>Kieran Kunhya via ffmpeg-devel (HE12025-03-25):
>> The server belongs to @Jean-Baptiste Kempf
>
>Are you saying that the tweet that says “giving ***us*** a 160-core ARM
>server” (emphasis mine) is a lie?
By that logic, any claim
v a0, t1
> +ret
> +endfunc
> \ No newline at end of file
> diff --git a/libswresample/swresample_internal.h
> b/libswresample/swresample_internal.h index 7e46b16fb2..257f69f6dd 100644
> --- a/libswresample/swresample_internal.h
> +++ b/libswresa
Hi,
Le 21 mars 2025 04:12:14 GMT+02:00, daichengrong a
écrit :
>
>在 2025/3/20 19:17:21, Rémi Denis-Courmont :
>> Hi,
>>
>> Le 20 mars 2025 11:27:39 GMT+02:00, daichengrong
>> a écrit :
>>>>> Availability of RVV and ZVBB should be determi
Hi,
Le 20 mars 2025 11:27:39 GMT+02:00, daichengrong a
écrit :
>>> Availability of RVV and ZVBB should be determined with dl_hwcap.
>> No. That's completely superfluous since we already check for kernel support
>> with hwprobe().
>No. If the operating system does not enable dl_hwcap support for
Hi,
I shouldn't need to point this out, but please do not resend patches without
addressing comments from previous versions in any apparent way.
-1
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Hi,
Le 14 mars 2025 17:32:57 GMT+07:00, daichengr...@iscas.ac.cn a écrit :
>From: daichengrong
>
>Availability of RVV and ZVBB should be determined with dl_hwcap.
No. That's completely superfluous since we already check for kernel support
with hwprobe().
And we can't check for Zb* and Zv* with
Le 10 mars 2025 15:14:46 GMT+02:00, Niklas Haas a écrit :
>On Sun, 09 Mar 2025 17:57:48 -0700 Rémi Denis-Courmont wrote:
>>
>>
>> Le 9 mars 2025 12:57:47 GMT-07:00, Niklas Haas a écrit :
>> >On Sun, 09 Mar 2025 11:18:04 -0700 Rémi Denis-Courmont
>> >
Le 9 mars 2025 12:57:47 GMT-07:00, Niklas Haas a écrit :
>On Sun, 09 Mar 2025 11:18:04 -0700 Rémi Denis-Courmont wrote:
>> Hi,
>>
>> Le 8 mars 2025 14:53:42 GMT-08:00, Niklas Haas a écrit :
>> >https://github.com/haasn/FFmpeg/blob/swscale3/doc/swscale-v2.txt
Hi,
Le 8 mars 2025 14:53:42 GMT-08:00, Niklas Haas a écrit :
>https://github.com/haasn/FFmpeg/blob/swscale3/doc/swscale-v2.txt
>I have spent the past week or so ironing
>I wanted to post it here to gather some feedback on the approach. Where does
>it fall on the "madness" scale? Is the new oper
Le 4 mars 2025 17:56:20 GMT+02:00, Kieran Kunhya via ffmpeg-devel
a écrit :
>>
>> Nevertheless, the CC does issue a warning regarding unnecessarily
>> offensive recent comments by Kieran on other topics, as well as for
>> initially failing to provide background and context regarding Paul’s
>> a
C and TC aliases are private. Snooping on
them or archiving them on the FFmpeg MTA would actually be illegal. Thus we
cannot and will not get access to the discussions of previous CC either.
--
Rémi Denis-Courmont
Hagalund ny stad, f.d. Finska
Le 27 février 2025 23:01:45 GMT+02:00, Michael Niedermayer
a écrit :
>we have a memleak, a use after free, a aliasing violation,
>some invalid pointer and a out of array read
>
>a safe language should not allow any of this
>C++ allows all of it, its not safe, switching to C++ doesnt help
To be
Hi,
Le 26 février 2025 16:18:20 GMT+02:00, Zhao Zhili
a écrit :
>
>
>> On Feb 26, 2025, at 21:50, Tomas Härdin wrote:
>>
>> fre 2025-02-21 klockan 20:10 + skrev Soft Works:
>>>
>>>
>>> From: Kieran Kunhya
>>> Sent: Freitag, 21. Februar 2025 20:27
>>> To: Soft Works
>>> Cc: FFmpeg devel
Hi,
Le 23 février 2025 23:30:03 GMT+02:00, "Tomas Härdin" a écrit
:
>lör 2025-02-22 klockan 14:57 +0200 skrev Rémi Denis-Courmont:
>> Le perjantaina 21. helmikuuta 2025, 20.02.16 UTC+2 Tomas Härdin a écrit :
>> > The above said, I'm not against Rust. It has
It probably won't make any difference in the end, but I find it better to admit
that we don't do what we don't do than to give false hopes.
--
Rémi Denis-Courmont
Villeneuve de Tapiola, ex-République finlandaise d´Uusimaa
___
ffmpeg-
s but that does not mean we should ban Cargo altogether.
> We used to link to OpenCV. The only reason why we dropped it was because
> we used the C interface, which was removed, and no one wanted to or was
> interested in rewriting it.
I agree that we should not depend on externa
n
> rolling our own.
Yikes. Rust is actually way saner for type-generic programming than C++.
--
Rémi Denis-Courmont
Villeneuve de Tapiola, ex-République finlandaise d´Uusimaa
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org
Le 16 février 2025 21:20:59 GMT+02:00, Soft Works
a écrit :
>
>
>> -Original Message-
>> From: ffmpeg-devel On Behalf Of Rémi
>> Denis-Courmont
>> Sent: Sonntag, 16. Februar 2025 18:59
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: Re: [FFmpeg-d
ing.
--
Rémi Denis-Courmont
Tapio's place new town, former Finnish Republic of Uusimaa
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel
; CLI.
>
> I'm afraid, but from my point of view, this doesn't match the objective.
Do you really expect to develop FFmpeg without using a CLI? In the first place,
FFmpeg is a set of library and CLI tools.
As far as the Git CLI is concerned, I believe that the main objecti
does this again, the CC
may very well take action.
--
Rémi Denis-Courmont
Villeneuve de Tapiola, ex-République finlandaise d´Uusimaa
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscri
ly into taking
> their trash for granted.
I am not alone in thinking that your anger here is completely justified.
But still, please watch your language, especially whilst confusing things
(LLM and LLVM).
--
Rémi Denis-Courmont
Tapio's place new town, former Finni
Le 7 février 2025 13:53:22 GMT+02:00, Zhao Zhili a
écrit :
>
>
>> On Feb 7, 2025, at 19:46, Zhao Zhili
>> wrote:
>>
>>
>>
>>> On Feb 7, 2025, at 19:39, Andreas Rheinhardt
>>> wrote:
>>>
>>> Andreas Rheinhardt:
Ronald S. Bultje:
> Fixes #11456.
> ---
> libavcodec/threadp
olerate having some level of public mockery at my expense. But
violating the CoC is not OK even if your opponent also might have.
(The CC reserves the option of further actions.)
--
Rémi Denis-Courmont
Tapio's place new town, former Finnish
, and James and Anton left for the time being blaming you, leaving
Marth alone. I hope to make some progress within the next week and report
before the winter vacation season.
--
Rémi Denis-Courmont
Villeneuve de Tapiola, ex-République finlandaise d´Uusimaa
__
ing this up
underlines the argument.
--
Rémi Denis-Courmont
Tapiolan uusi kaupunki, Uudenmaan entinen Suomen tasavalta
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or e
Le lauantaina 25. tammikuuta 2025, 22.26.44 UTC+2 Michael Niedermayer a écrit
:
> On Fri, Jan 24, 2025 at 09:36:50PM +0200, Rémi Denis-Courmont wrote:
> I have not complained about "FFmpeg community members attending conferences
> and discussing FFmpeg". Your statement suggest
Merged, thanks.
--
レミ・デニ-クールモン
http://www.remlab.net/
___
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 "unsubs
experience with moving over to Gitlab in other projects,
it is absolutely essential that simple, concise and functional documentation
be made available to all developers and reviewers.
The workings may seem obvious to those use to whichever tool is picked, but
they probably won't be
Le 24 janvier 2025 23:02:05 GMT+02:00, Nicolas George a écrit
:
>Rémi Denis-Courmont (12025-01-24):
>> For the record, those are just suggestions for future reference, not
>> personal
>> attacks.
>
>Rule of thumb: messages that needs to clarify they are not per
Le maanantaina 20. tammikuuta 2025, 20.14.41 UTC+2 Gyan Doshi a écrit :
> On 2025-01-20 11:14 pm, Soft Works wrote:
> > - An indication that the aim and direction of the contribution is
> >
> >generally acceptable
>
> This the crux of the matter. There appear to be two camps at odds with
> on
Hello,
Le tiistaina 21. tammikuuta 2025, 2.36.47 UTC+2 Michael Niedermayer a écrit :
> Hi
>
> On Mon, Jan 20, 2025 at 10:38:17AM -0600, Marth64 wrote:
> > All this time people send back and forth emails attacking each other or
> > the
> > project could have spent toward investing in modern DevOps
Le 13 janvier 2025 17:01:01 GMT+08:00, "myp...@gmail.com" a
écrit :
>On Sun, Jan 12, 2025 at 10:11 PM Rémi Denis-Courmont wrote:
>>
>>
>>
>> Le 8 janvier 2025 19:42:15 GMT+08:00, Jun Zhao a écrit :
>> >From: Jun Zhao
>> >
>> &
Le 8 janvier 2025 19:42:15 GMT+08:00, Jun Zhao a écrit :
>From: Jun Zhao
>
>fix R-V HAVE_RVV scope issue
>
>Signed-off-by: Jun Zhao
>---
> libavcodec/riscv/ac3dsp_init.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>diff --git a/libavcodec/riscv/ac3dsp_init.c b/libavcodec/riscv/ac3
Hi,
Le 7 janvier 2025 21:54:06 GMT+02:00, Leo Izen a écrit :
>On 1/7/25 1:20 PM, Rémi Denis-Courmont wrote:
>> Le tiistaina 7. tammikuuta 2025, 6.46.24 UTC+2 Vittorio Giovara a écrit :
>>> S not to poke a bee's nest, but what's going on here? Are there any
>>
Le maanantaina 23. joulukuuta 2024, 17.01.32 UTC+2 uk7b-at-
foxmail@ffmpeg.org a écrit :
> From: sunyuechi
>
> ---
> libavcodec/riscv/h26x/asm.S| 36 +-
> libavcodec/riscv/vvc/sad_rvv.S | 2 +-
> 2 files changed, 19 insertions(+), 19 deletions(-)
>
> dif
.. So far
there have been two complaints, one from you, which you withdrew, and another
one which came just today.
The new CC members such as I myself don't have access to previous
communications and deliberations, at least not that I'd know.
--
Rémi
Le 3 janvier 2025 11:43:48 GMT+02:00, Nicolas George a écrit :
>> Rémi Denis-Courmont (12025-01-03):
>>> Cc: c...@ffmpeg.org
>
>Oh, I had not noticed that attempt at weaponizing the CC.
I don't condone that choice of words, which is not mine. IIRC those are Anton&#x
Happy new year,
Le 3 janvier 2025 00:12:45 GMT+02:00, Nicolas George a écrit :
>Rémi Denis-Courmont (12025-01-02):
>> > > Besides, it is obvious from the rest that the true purpose of your
>> > > proposal is for you to monopolise power
>
>> For the rec
Le torstaina 2. tammikuuta 2025, 21.50.32 UTC+2 Nicolas George a écrit :
> Rémi Denis-Courmont (12025-01-02):
> > So what? I pay far more taxes than most people do, and yet I don't have
> > more voting power than other people.
>
> Note that even people who never paye
Le torstaina 2. tammikuuta 2025, 20.10.31 UTC+2 Michael Niedermayer a écrit :
> Let me provide several independant arguments here.
>
> in the GA system
> someone spending 2 days to submit 20 patches and not caring about FFmpeg has
> 1 vote
Someone who does not care about FFmpeg will not use their
Le torstaina 2. tammikuuta 2025, 16.17.31 EET Michael Niedermayer a écrit :
> People will have shares proportional to their contribution to FFmpeg.
That would be a giant step backward in terms of "democratisation". In
democracy, people have one vote. In terms of democratisation, you can argue
Hi,
Le 31 décembre 2024 20:40:36 GMT+02:00, Alexander Strasser via ffmpeg-devel
a écrit :
>With the current culminations, and the stress and influx of mails
>it caused for all subscribers espescially in this for many of us
>rather busy time of the family year, I would like to see a pause
>of all
Le maanantaina 30. joulukuuta 2024, 18.57.49 EET Michael Niedermayer a écrit :
> After months of public harassment and accusations
> it appears the attacks against me shift to private mail.
You can't *publicly* accuse people of harrassment without proof,. That would
literally constitute defamatio
dy else,
if they have the time, expertise and attention to do so. Unfortunately, while
there are several other RISC-V-capable developers here, none of them seem
really both willing and able to review Sunyuechi (or my) patches.
--
Rémi Denis-Courmont
http://www.remlab.net/
__
Le 23 décembre 2024 14:23:54 GMT+01:00, "Ronald S. Bultje"
a écrit :
>Hi,
>
>On Mon, Dec 23, 2024 at 8:22 AM Nicolas George wrote:
>
>> Could you all stop ganging against Michael? It is reminiscent of the
>> bullying he was subjected to in the months leading to the fork that
>> convinced him t
Le dimanche 22 décembre 2024, 17:13:50 EET Michael Niedermayer a écrit :
> Hi Rémi
>
> On Sat, Dec 21, 2024 at 03:47:50PM +0200, Rémi Denis-Courmont wrote:
> > Hi,
> >
> > Le 21 décembre 2024 05:57:26 GMT+02:00, Michael Niedermayer
a écrit :
> > >Hi Anton
&
Le mardi 17 décembre 2024, 11:50:26 EET flow gg a écrit :
> > Don't clobber v8 here.
> > Use vsub.vv here to avoid the sequential dependency.
>
> Thanks, I will update later
>
> > Are you sure this does not require tail-undisturbed mode? I think you're
> > setting tail-agnostic mode up.
>
> I’m
Hello,
I remember agreeing to rename files. I do not remember agreeing to merging this
new functionality. To the contrary, this patch had objections from me, and not
just about performance. The functional issues are not even addressed here.
Why the heck was this broken SAD code merged when the
Hi,
Le 21 décembre 2024 05:57:26 GMT+02:00, Michael Niedermayer
a écrit :
>Hi Anton
>
>On Fri, Dec 20, 2024 at 06:24:46AM +0100, Anton Khirnov wrote:
>> Quoting Michael Niedermayer (2024-12-19 20:52:39)
>> > This was a brave decission and IMO it was the correct decission.
>> > You saw people fig
Hi
The RISC-V bits look ok. No opinion on x86.
___
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".
Le sunnuntaina 15. joulukuuta 2024, 17.56.34 EET uk7b-at-foxmail@ffmpeg.org
a écrit :
> From: sunyuechi
>
> k230 banana_f3
> sad_8x16_c: 387.7 ( 1.00x)394.9 ( 1.00x)
> sad_8x16_rvv_i32: 109.7 ( 3.53x)103.5 ( 3.82x)
>
Le sunnuntaina 15. joulukuuta 2024, 22.17.27 EET Alexander Strasser via ffmpeg-
devel a écrit :
> Hi Rémi!
>
> On 2024-11-19 19:10 +0200, Rémi Denis-Courmont wrote:
> > I plan to solicit an FFmpeg booth at SCaLE 22x to be held early next
> > March.
> > Booths for open-
Le 13 décembre 2024 12:14:43 GMT+02:00, Nicolas George a
écrit :
>Kieran Kunhya via ffmpeg-devel (12024-12-13):
>> Then the conclusion in your example is wrong.
>
>No it is not. Either you misunderstood what I explained
Rather what you wrote ("wave") is not what you meant, presumably "PCM". As
is no
> point in holding a vote. I therefore propose to wait a week. If any new
> candidates appear in that time, we hold a vote; otherwise the above
> people are appointed as the CC.
I self-nominate for the CC election.
Vote for me or else vote for me.
--
Rémi
Le 6 décembre 2024 13:19:29 GMT+01:00, Niklas Haas a écrit :
>On Thu, 05 Dec 2024 21:41:51 +0800 uk7b-at-foxmail@ffmpeg.org wrote:
>> From: sunyuechi
>>
>> ---
>> libavcodec/riscv/rv40dsp_rvv.S | 116 ++---
>> 1 file changed, 78 insertions(+), 38 deletions(-)
>>
As with the inter loop filter, performance metrics seem to be biased in
favour of the C implementation because checkasm inputs almost always
fall in the no-op case.
h264_h_loop_filter_chroma_intra_8bpp_c: 82.8 ( 1.00x)
h264_h_loop_filter_chroma_intra_8bpp_rvv_i32: 72.6 (
Le keskiviikkona 27. marraskuuta 2024, 14.35.08 EET Zhao Zhili a écrit :
> Ping.
I don't like that we use intrinsics, especially in this case, but I don't
volunteer to rewrite the code as assembler.
--
レミ・デニ-クールモン
http://www.remlab.net/
___
ffmpeg-
e used here.
Clobbering the frame pointer is best avoided to ease debugging.
--
Rémi Denis-Courmont
http://www.remlab.net/
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit lin
Le tiistaina 26. marraskuuta 2024, 5.01.56 EET flow gg a écrit :
> Updated them.
If you update a patchset, resend the series and add a version number like
others do. It's just too complicated to track series over email otherwise.
--
Rémi Denis-Courmont
http://www.re
vwmulu.vx v10, v12, a6
>.ifc \type,avg
> vle8.v v18, (a5)
> -manual_avg v8, v8, v18
> + vaaddu.vv v8, v8, v18
>.endif
> vse8.v v8, (a5)
> add a5, a5, a2
> -vncl
1 - 100 of 1195 matches
Mail list logo
