On Thu, 12 Sep 2024, at 02:59, James Almer wrote:
> Signed-off-by: James Almer
> ---
> Somewhat improved the glue, making it all internal to decode.c and no longer
> touching AVCodecInternal.
Seems a ton better, as far as I am concerned.
--
Jean-Baptiste Kempf - President
+33
Hello,
On Sat, 7 Sep 2024, at 22:46, Michael Niedermayer wrote:
> I intend to branch 7.1 in the next 24h
Could you wait a tiny bit more, please?
I know Lynne and James have important work in progress, maybe they could chim
in on Monday to merge them or not.
jbk
--
Jean-Baptiste Ke
On Fri, 6 Sep 2024, at 16:18, Frank Plowman wrote:
> ffmpeg | branch: master | Frank Plowman | Fri
> Aug 23 13:36:50 2024 +0100| [6df0c5f9f4c3261acf5b0efe43597b9eb765d6b6]
> | committer: Nuo Mi
>
> lavc/vvc: Remove experimental flag
Congratulations.
--
Jean-Baptiste Kempf -
ly feels quite wrong.
>
> I could try to make it a bit more opaque to decode.c, making i call a
> function that would then set any needed post processing callback or
> something like that.
If you could, that would be neat: I was also frustrated by this patch in the
serie.
--
Jea
from VideoLAN, FFmpeg, VLC x264, dav1d, Xodi, libplacebo, mpv
and related projects will be here.
In case you are interested in coming this November, the link to register is
here:
https://framaforms.org/vdd-2024-1723106137
Talks are very welcomed!
Best regards,
--
Jean-Baptiste Kempf - Presiden
--
Jean-Baptiste Kempf - President
+33 672 704 734
https://jbkempf.com/
___
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
hread.c
> index 2654b40058..8777d380bf 100644
> --- a/libavcodec/vvc/thread.c
> +++ b/libavcodec/vvc/thread.c
> @@ -293,10 +293,14 @@ static void schedule_inter(VVCContext *s,
> VVCFrameContext *fc, const SliceContex
> CTU *ctu = fc->tab.ctus + rs;
> for (int lx = 0; lx < 2; lx++) {
>
>> There's an infinite amount of discord clones already.
>
> iam not following that genre that much ...
> so let me ask
> are there any that
> * preserve privacy (discord is not secure/private)
> * allow audio / video / text chat
> * scalable
> * need no central
ese
In summary, IMHO:
I think you should support less versions.
Drop 2.8 and 3.4 (after a point release, if you want).
Maintain 4.2, 4.4, 5.1, 6.1 and drop all the rest (4.0, 4.1, 4,.3, 5.0).
Almost no other project in the world support that many branches.
It's better to have a few ver
On Thu, 4 Apr 2024, at 07:30, Vittorio Giovara wrote:
> On Thu, Apr 4, 2024 at 1:28 AM Jean-Baptiste Kempf wrote:
>
>> On Wed, 3 Apr 2024, at 23:18, Jean-Baptiste Kempf wrote:
>> > As attached.
>>
>> Updated version attached (v2).
>>
>
> lgtm with
On Wed, 3 Apr 2024, at 23:18, Jean-Baptiste Kempf wrote:
> As attached.
Updated version attached (v2).
--
Jean-Baptiste Kempf - President
+33 672 704 734
https://jbkempf.com/From 96f2b0ee578901ebcf00795950dd78d8e924643c Mon Sep 17 00:00:00 2001
From: Jean-Baptiste Kempf
Date: Wed, 3 Apr 2
on IRC, since this is pretty trivial.
jbk
--
Jean-Baptiste Kempf - President
+33 672 704 734
https://jbkempf.com/
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link abo
As attached.
--
Jean-Baptiste Kempf - President
+33 672 704 734
https://jbkempf.com/From bc5a37d34d9a634388e425d894aa1219a32d8394 Mon Sep 17 00:00:00 2001
From: Jean-Baptiste Kempf
Date: Wed, 3 Apr 2024 23:12:54 +0200
Subject: [PATCH] Update the Changelog for 7.0
---
Changelog | 11
s, they give a very
>> non-negligible speedup on many common CPUs, and patch #2 fixes a real bug in
>> the existing impleemntations. (A bug fix patch can of course be backported
>> after the branch too, but performance optimizations aren't generally
>> relevan
Hello,
On Mon, 25 Mar 2024, at 01:03, Michael Niedermayer wrote:
> Should i wait till all issues marked as blocking 7.0 on trac are fixed
> before branching ?
I think you should branch now.
And get things fixed in the 7.0 branch.
--
Jean-Baptiste Kempf - President
+33 672 704 734
On Mon, 18 Mar 2024, at 11:01, Steven Liu via ffmpeg-devel wrote:
> Changelog | 1 +
> 1 file changed, 1 insertion(+)
Obviously LGTM.
jbk
--
Jean-Baptiste Kempf - President
+33 672 704 734
https://jbkempf.com/
___
ffmpeg-devel mailin
his was not recognized.
LGTM.
--
Jean-Baptiste Kempf - President
+33 672 704 734
https://jbkempf.com/
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg
the C++ library of PyTorch as
> LibTorch, the same below.
LGTM. Please apply.
--
Jean-Baptiste Kempf - President
+33 672 704 734
https://jbkempf.com/
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-dev
* data loss
>> * privacy issues
>> * anything the commuity agrees should be in the release
>
> We still have 3 blocking issues on trac
>
> do people want me to wait or ignore them and branch ?
I think you can branch soon.
However, those 3 bugs are quite important, tbh
g must be built with GPL library support available as well as the
> configure switches --enable-libdvdnav and --enable-libdvdread.
Rocks.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://
Hello,
This is missing an "enabled gpl" in the configure.
BR,
On Sat, 2 Mar 2024, at 09:08, Marth64 wrote:
> ffmpeg | branch: master | Marth64 | Sun Feb 18
> 22:01:44 2024 -0600| [a1304272c3a0ef7c3d77c702dd466b3f11bf300f] |
> committer: Anton Khirnov
>
> libavformat/dvdvideo: add DVD-Video de
it can at some point be developed
> again, then removing the codec id to re-add it later will be a bit dirty.
>
> IMO, just disable both modules by default during configure, or tag the
> encoder as experimental to prevent new streams to be created unless
> explicitly requested
t; case DNN_OV:
> return &ff_dnn_backend_openvino;
> #endif
> +#if (CONFIG_LIBTORCH == 1)
> +case DNN_TH:
> +return &ff_dnn_backend_torch;
> +#endif
> default:
> av_log(log_ctx, AV_LOG_ERROR,
> "Module backend_
overs/committers to that repo.
It simplifies the workflow on the admin side, since with a git hook, the server
does "git update" in the directory that will be rsync'd by the mirrors. And it
does not change their workflow, still using rsync.
just my 5c.
--
Jean-Bapt
ert(sizes.size == 5);
Why 5?
> +outputs.order = DCO_RGB;
> +outputs.layout = DL_NCHW;
> +outputs.dims[2] = sizes.at(3);
> +outputs.dims[3] = sizes.at(4);
> +outputs.dt = DNN_FLOAT;
> +outputs.dims[1] = 3;
Why 3?
--
Jean-Baptiste Kempf - President
+33 672
a year on C17 (while adopting C11 immediately), which
My recommendation is still this:
- move to C11 now
- activate C17 on some Fate/CI targets
- recommend C17 compilers modes
- move to C17 at this mid-year when 7.1 is branched (LTS if we follow our plans
afternoon, at the usual place.
See you at FOSDEM,
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
d should be used everywhere to avoid splitting a
number from its unit in various part of the documentation.
—
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ff
q} option removed?
> What to use instead?
> --
> 2.34.1
>
> ___
> 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...@ff
r important these days, is there a chance they could be
>> implemented before merging?
>
> Hi Hendrik,
> Thank you for your help.
>
> Hi Lynne,
> A contributor submitted an IBC implementation at
> https://github.com/ffvvc/FFmpeg/pull/169, but it still needs time to
> finis
+
>> > >>> libavcodec/vvc/vvc_thread.h | 36 +
>> > >>> libavcodec/vvc/vvcdec.c | 1017
>> > >>> libavcodec/vvc/vvcdec.h | 226 ++
>> > >>> libavcodec/vvc/vvcdsp.c |
hanges to the HEVC code.
> Currently, I prefer not to touch the HEVC code as there is no HEVC
> maintainer, and any HEVC code change requires a very long review time.
Yes, keep it up like this.
--
Jean-Baptiste Kempf - President
+33 672 704 734
_
ibutors(based on code merge order):
>>Nuo Mi
>>Xu Mu
>>frankplow
>>Shaun Loo
>
> Minor nitpick: For clarity, I'd prefer if you'd spell out Frank's full
> namw here.
Also, you should use Co-Authored-By:
--
Jean-Baptiste Kemp
, soon™®
Merry Christmas and happy holidays!
--
Jean-Baptiste Kempf - CC
+33 672 704 734
___
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
On Thu, 7 Dec 2023, at 10:14, Nicolas George wrote:
> The community is dead. And you never belonged to it anyway, with your
> superior attitude.
You calling someone "superior attitude" is amazing.
--
Jean-Baptiste Kempf - President
On Thu, 7 Dec 2023, at 10:10, Nicolas George wrote:
> Jean-Baptiste Kempf (12023-12-07):
>> You are delusional.
>
> Oh, this is absolutely appropriate, especially from somebody who just
> got elected to apply the code of conduct.
Keep antagonizing more people in the community,
On Thu, 7 Dec 2023, at 09:59, Nicolas George wrote:
> Jean-Baptiste Kempf (12023-12-07):
>> Why?
>
> Because after twelve years libav has finally managed to take control and
> FFmpeg is now essentially dead.
You are delusional. libav is dead since a long time.
The fact that
mail
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
> Attachments:
> * 0001-MAINTAINERS-remove-myself-from-FFmpeg.patch
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.
$subject
See attachment.
--
Jean-Baptiste Kempf - President
+33 672 704 734From 13eb5105ff6fe664d4a45da6970875ceb763dfe0 Mon Sep 17 00:00:00 2001
From: Jean-Baptiste Kempf
Date: Tue, 5 Dec 2023 10:56:55 +0100
Subject: [PATCH] doc: mention that for RISC-V, we prefer .S files
---
doc
documented official limit?
jb
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
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...@ffmp
mx.at
>> i could vote twice.
>
> I am confused: you would get the same token in the second mail, you
> would not be able to use it twice.
Nicolas is very correct here: in some of the test voting, some people got the
email twice, and could vote only once.
TBH, all e-voting syste
Private Information, according to a GDPR and that you are a process of this
PI, and therefore liable to the law.
However, neither YOU nor the legal owner FFmpeg.org explain how you will retain
this information, process it further, OR, as the most important part,
an being, who understand his limitations.
People have asked for people becoming candidates to post publicly on this
mailing list, I don't see what the big deal in that.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffm
On Thu, 9 Nov 2023, at 23:49, Michael Niedermayer wrote:
> On Thu, Nov 09, 2023 at 08:30:15PM +0100, Jean-Baptiste Kempf wrote:
>>
>>
>> On Thu, 9 Nov 2023, at 19:15, Michael Niedermayer wrote:
>> > On Thu, Nov 09, 2023 at 07:53:33PM +0200, Rémi Denis-Courmo
ld step forward and say so publicly that they are candidates.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
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".
and now the new list was written by Anton
with the new script.
Whatever the old script was, and how wrong it was, I don't think it would
change the result of the re-bootstrapping vote.
And now we have a clean list for the extra members of the GA.
--
Jean-Baptiste Kempf - President
+33 672
his is not acceptable for a vote.
How so? Do you go to and see the list of all the voters in Austria before doing
a vote ?
Especially, here, it is to bootstrap a new way of voting.
If the vote was close, maybe there could be discussion, but here, this is not
the case.
And stop smearing
anymore.
Best,
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
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
{ "0", "1", "2" } },
> +{ AV_HWDEVICE_TYPE_D3D12VA,
> + { "0", "1", "2" } },
> { AV_HWDEVICE_TYPE_OPENCL,
> { "0.0", "0.1", "1.0&q
Hello,
On Mon, 6 Nov 2023, at 16:56, Alexander Strasser wrote:
> Hi all,
> hi J-B!
>
> On 2023-11-06 07:10 +0100, Jean-Baptiste Kempf wrote:
>> Yo,
>>
>> Time is up, results are here:
>> https://vote.ffmpeg.org/cgi-bin/civs/results.pl?id=E_029f7195fed7aadf
>
aken, with a bi-annual update.
Patches for the documentation are welcome.
Best,
--
Jean-Baptiste Kempf - Vice
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit
tion for the voting system I could also add some switches to the
> script to print only names, only emails or name and email for example.
That would be helpful, tbh.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
g will it take you ?
Sorry, I got quite sick, like many people who came from Demuxed.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscri
ists (+ the scripts) only give emails, and not names.
So I'll need to remap that manually to have the list of names. It will take a
bit of time, but I'll do it.
jb
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mail
On Mon, 30 Oct 2023, at 11:33, Thilo Borgmann via ffmpeg-devel wrote:
> Am 30.10.23 um 09:18 schrieb Jean-Baptiste Kempf:
>> Hello,
>>
>> On Sun, 29 Oct 2023, at 10:33, Anton Khirnov wrote:
>>> vote question (unchanged):
>>> How do we update the list of
go with the above for the
> actual vote tomorrow.
This has been launched.
You should be able to vote until Sunday 5th Nov, 23:59
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/
scribe".
>
> Attachments:
> * 0002-aacdec-correctly-skip-padding-at-the-start-of-frames.patch
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-
On Sun, 29 Oct 2023, at 19:46, Thilo Borgmann via ffmpeg-devel wrote:
> Am 29.10.23 um 18:56 schrieb Jean-Baptiste Kempf:
>> On Sun, 29 Oct 2023, at 18:20, Thilo Borgmann via ffmpeg-devel wrote:
>>> In this case as well, I think you
>>> should have transported your reaso
On Sun, 29 Oct 2023, at 19:31, Nicolas George wrote:
> Jean-Baptiste Kempf (12023-10-29):
>> We'll have to agree to disagree.
>
> So you disagree that ffmpeg is not a corporate project where developers
> can be forced to have fixed work hours. Interesting.
IRC has logs
On Sun, 29 Oct 2023, at 19:12, Nicolas George wrote:
> Jean-Baptiste Kempf (12023-10-29):
>> Sorry, I can. Being on IRC is necessary, IMHO.
>
> Completely unacceptable and fortunately not true at all.
We'll have to agree to disagree.
--
Jean-Baptiste Kempf - Presi
nd a longer email to explain.
> cannot blame anyone for not following live discussion like VDD or IRC.
Sorry, I can. Being on IRC is necessary, IMHO.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ff
On Sun, 29 Oct 2023, at 17:49, James Almer wrote:
> On 10/29/2023 1:42 PM, Jean-Baptiste Kempf wrote:
>> Hello,
>>
>> On Sat, 28 Oct 2023, at 18:49, Michael Niedermayer wrote:
>>> noone mentioned 5.1.x and 6.0.x to me before
>>
>> Our last releases from
On Sun, 29 Oct 2023, at 17:40, Nicolas George wrote:
> Jean-Baptiste Kempf (12023-10-29):
>> Because instead of doing the polite and normal thing which would be:
>
> Politeness or not does not make it a personal attack. Moving goalposts
> much?
Being not polite to someone is
not enough new things to cut a
release.
So I'm not against a release for 6.1 at all, but I believe focusing on minor
releases for security and on 7.0 with the next major deprecations is more
important.
If we can do all of those, and keep more or less the timing for 7.0, please be
my guest
On Sun, 29 Oct 2023, at 15:17, Nicolas George wrote:
> Jean-Baptiste Kempf (12023-10-29):
>> > Unsubstantiated opinion, let us ignore it.
>> Again, a personal attack, from you.
>
> YOU are not an OPINION, so, no, this is not a personal attack,
Because instead of doing the
anything and is not an
> argument.
Refusing to attend the developer meetups and also refusing to be on one of the
major discussion media and then complaining about not receiving information is
a problem in an open source community.
jb
--
Jean-Baptiste Kempf - Pre
explain many times why the opportunity has passed for 6.1, but you,
once again, don't listen, or refuse to be on the means where we discuss.
Again, a personal attack, from you.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel maili
On Tue, 10 Oct 2023, at 14:42, Jean-Baptiste Kempf wrote:
>> There was no real prior discussion on the mailing list about this.
>
http://ffmpeg.org/pipermail/ffmpeg-devel/2023-September/314772.html
--
Jean-Baptiste Kempf - President
+33 67
vote rights but add active developers each
> jan/july
>
> Is a more honest choice for the "opposition" than "never update"
That's an extra choice, in my opinion, and we could also have it, but it's a
bit annoying that you say it now.
But it's doable.
Be
e of Conduct.
It's not the first time I remind this fact.
jb
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link
;> - James
>> - J-B
>> - Thilo
>> - Steven
>> - BBB
>
> Iam missing carl on the list
As above.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https
e should make this clear in the docs then.
+1
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
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".
d
I disagree. The infrastructure is un-documented, and the people accessing it
are un-documented.
This is a big problem.
jb
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailm
31,7 @@ version :
> - Support HEVC,VP9,AV1 codec in enhanced flv format
> - apsnr and asisdr audio filters
> - OSQ demuxer and decoder
> +- Support HEVC,VP9,AV1 codec fourcclist in enhanced rtmp protocol
Lgtm
--
Jean-Baptiste Kempf - President
+33 672 704 734
__
On Fri, 25 Aug 2023, at 18:27, Nicolas George wrote:
> Jean-Baptiste Kempf (12023-08-25):
>> So that means mandatory sending to the mailing list :)
>
> And change the name to libav?
Trolling is not going to get you anywhere.
--
Jean-Baptiste Kempf - President
(even completely new filters) without
>> sending them to the ML.
>
> That was not the intend but if you look at "cvslog" and ffmpeg-devel, you will
> notice that there are things being pushed that have not been seen on the
> ffmpeg-devel mailing list.
So that means
Hello,
On Mon, 21 Aug 2023, at 03:35, Steven Liu wrote:
> Jean-Baptiste Kempf 于2023年8月20日周日 16:29写道：
>>
>> Hello,
> Hi
>>
>> On Sun, 20 Aug 2023, at 06:10, Steven Liu wrote:
>> > As the enhanced rtmp Extending NetConnection connect Command section
>>
On Sun, 20 Aug 2023, at 15:01, Tomas Härdin wrote:
> Will it be possible to attend via Jitsi Meet or similar?
For the FFmpeg meeting, of course. For the rest, I dunno yet.
jb
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-de
Hello,
On Sun, 20 Aug 2023, at 06:10, Steven Liu wrote:
> As the enhanced rtmp Extending NetConnection connect Command section
> said, the rtmp should add a property named fourCcLive, but there should
> only one codec can be set for the video stream in rtmp+flv, so user can
> use the option rtmp_e
VDD.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
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".
ing louder does not change this reality.
If you disagree, just get a vote from all people who have commit access, and
you will see.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.o
omething and you will get more feedback
Then, the API will evolve into something better in v2.
jb
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-
an API, it would be trivial to add support to this optional
library as an FFmpeg module, and noone who complain.
jb
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/list
Please merge.
On Thu, 1 Jun 2023, at 12:29, Jean-Baptiste Kempf wrote:
> Hello,
>
> On Thu, 1 Jun 2023, at 02:02, Steven Liu wrote:
>> Neal Gompa 于2023年5月31日周三 13:47写道：
>>>
>>> On Mon, May 15, 2023 at 10:41 PM Neal Gompa wrote:
>>> >
>>&g
gt; Anything anyone wants to have merged or should we branch
> off 6.1 in a few days?
By experience, it requires a bit more than a few days... :D
jb
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffm
Hello,
On Tue, 4 Jul 2023, at 01:00, Michael Niedermayer wrote:
> Suggested-by: Anton
>
> Signed-off-by: Michael Niedermayer
> ---
> doc/developer.texi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/developer.texi b/doc/developer.texi
> index 0c2f2cd7d1..67f7f78e86
On Sun, 2 Jul 2023, at 18:07, Nicolas George wrote:
> Jean-Baptiste Kempf (12023-07-02):
>> Absolutely not.
>> You are the only one who believes that.
>
> Except for the person who created FFmpeg in the first place. And probably
> other people too.
Having talked to Fabr
On Sun, 2 Jul 2023, at 11:58, Nicolas George wrote:
>> Even if it is disabled by default, git master isn't a playground for
>> personal projects.
>
> Yes it is.
Absolutely not.
You are the only one who believes that.
--
Jean-Baptiste Kempf - Pr
On Fri, 30 Jun 2023, at 16:08, Michael Niedermayer wrote:
> Also as said previously, If there is at least a 2nd developer working
> on this then we could & should move this to a seperate libraray (libavradio)
Why wait for a 2nd dev?
--
Jean-Baptiste Kempf - President
+33 6
to exist, so I will
> spend time on these issues, that is all.
Again YOUR goal. It might not be the majority of the community.
We can do an AG vote, if you want.
> go fork yourself.
This is out of line, IMHO.
jb
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
On Sun, 18 Jun 2023, at 23:50, Michael Niedermayer wrote:
> doc/developer.texi | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
+1
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmp
On Thu, 8 Jun 2023, at 19:39, Paul B Mahol wrote:
> Attached.
Missing version bumping?
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
le:
>> > > https://github.com/veovera/enhanced-rtmp/blob/main/enhanced-rtmp-v1.pdf
>> > > The Enhanced flv has been supported by OBS, Simple Realtime Server,
>> > > mpegts.js.
>> > > you can publish hevc, av1 or vp9 codec stream to Youtube over rtmp
On Fri, 12 May 2023, at 05:35, Neal Gompa wrote:
> On Thu, May 11, 2023 at 12:26 PM Jean-Baptiste Kempf
> wrote:
>>
>>
>>
>> On Thu, 11 May 2023, at 18:21, Neal Gompa wrote:
>> > On Wed, May 10, 2023 at 9:40 PM Steven Liu wrote:
>> >>
>>
gt;>> respect to DTS\n");
>> > > > > >>>>>>return AVERROR(EINVAL);
>> > > > > >>>>>>}
>> > > > > >>>>>> - if (par->codec_id == AV_CODEC_ID_H264
Hello,
Just 2 questions:
- could you split this patch into several (3,4 or 5)
- are all those functions checked by chekasm?
Thanks,
jb
On Sun, 30 Apr 2023, at 10:57, myais wrote:
> Hi,
> This is a patch for the aarch64, which completes the neon versions of
> the hevc_pel_uni_w_pixels, qpel_uni
nothing else.
>>
>
> This is a good argument for putting the code in fftools/ and not
> libavutil, fwiw.
This is also my understanding.
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffm
On Sat, 29 Apr 2023, at 07:44, SuperFashi wrote:
> +#define AVERROR_INVALIDDATA (abort(), 0)
Why are you aborting?
--
Jean-Baptiste Kempf - President
+33 672 704 734
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mail
ply here
>>
>> 6.0 release will be maybe 1 week after the branch point
>> once it has branched all important fixes should be backported of course
>
> What name shall 6.0 bear ?
Why don’t you select 3 or 4 names from the list
And we do a proper vote on vote.ffmpeg.org?
-
I can, in the large
percentage of cases, be done without breaking ABI (Sure, it might means that
the structures are not as beautiful as they should be, but...)
I don't see the issue here.
In general, adding big changes should be done at the beginning of a new cycle,
not at the end.
jb
--
1 - 100 of 460 matches
Mail list logo
