On Fri, May 17, 2024 at 9:50 AM Michael Niedermayer
wrote:
> Hi all
>
> Before this is forgotten again, better start some dicsussion too early
> than too late
>
> I propose that if we have the oppertunity again next year to receive a
> grant
> from STF. That we use it to fund:
>
> * Paul to work
On Fri, May 31, 2024 at 7:49 PM Anton Khirnov wrote:
> ---
> libavcodec/hevc/hevcdec.h | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/libavcodec/hevc/hevcdec.h b/libavcodec/hevc/hevcdec.h
> index 8208268460..33ad4ac0aa 100644
> --- a/libavcodec/hevc/hevcdec.h
> +++ b/libavcodec/hevc/
On Mon, Jun 3, 2024 at 8:50 AM Thilo Borgmann via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> Am 02.06.24 um 22:14 schrieb Tomas Härdin:
> > sön 2024-06-02 klockan 20:01 +0200 skrev Michael Niedermayer:
> >> Hi
> >>
> >>
> >> On Sat, Jun 01, 2024 at 05:19:26PM +0200, Tomas Härdin 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:
> >
> > Le maanantaina 3. kesäkuuta 2024, 21.58.48 EEST Cosmin Stejerean via
> ffmpeg-
> > devel a écrit :
> >> Not sure why you ke
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
> > respond, but shouldn't these kinds of requests go through the GA? If
> > anybody can do whatever they want with the ffmpe
On Tue, Jun 4, 2024 at 8:55 AM Paul B Mahol wrote:
> On Tue, Jun 4, 2024 at 8:53 AM Vittorio Giovara <
> vittorio.giov...@gmail.com>
> wrote:
>
> > On Tue, Jun 4, 2024 at 3:01 AM Cosmin Stejerean via ffmpeg-devel <
> > ffmpeg-devel@ffmpeg.org> wrote:
>
On Tue, Jun 4, 2024 at 3:16 AM Michael Niedermayer
wrote:
> > Breakages are expected when you remove API.
>
> Are Breakages also expected when you do not remove API ?
>
If a tree falls in a forest and no one is around to hear it, does it make a
sound?
--
Vittorio
___
On Tue, Jun 4, 2024 at 12:09 PM Paul B Mahol wrote:
> On Tue, Jun 4, 2024 at 9:09 AM Vittorio Giovara <
> vittorio.giov...@gmail.com>
> wrote:
>
> > On Tue, Jun 4, 2024 at 8:55 AM Paul B Mahol wrote:
> >
> > > On Tue, Jun 4, 2024 at 8:53 AM Vittorio Gio
On Tue, Jun 4, 2024 at 2:02 PM Paul B Mahol wrote:
> On Tue, Jun 4, 2024 at 12:59 PM Vittorio Giovara <
> vittorio.giov...@gmail.com>
> wrote:
>
> > On Tue, Jun 4, 2024 at 12:09 PM Paul B Mahol wrote:
> >
> > > On Tue, Jun 4, 2024 at 9:09 AM Vittorio Gio
On Tue, Jun 4, 2024 at 7:39 PM Paul B Mahol wrote:
> On Tue, Jun 4, 2024 at 2:53 PM Vittorio Giovara <
> vittorio.giov...@gmail.com>
> wrote:
>
> > On Tue, Jun 4, 2024 at 2:02 PM Paul B Mahol wrote:
> >
> > > On Tue, Jun 4, 2024 at 12:59 PM Vittorio Gio
On Tue, Jun 4, 2024 at 5:47 PM Cosmin Stejerean via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
>
>
> > On Jun 3, 2024, at 11:53 PM, Vittorio Giovara <
> vittorio.giov...@gmail.com> wrote:
> >
> > On Tue, Jun 4, 2024 at 3:01 AM Cosmin Stejerean via ffm
On Tue, Jun 4, 2024 at 11:22 PM Michael Niedermayer
wrote:
> > Sure I'm happy to work on this with you! Let's talk offline about it
>
> Why should discussions about a FFmpeg booth be offline ?
>
That's a great question, CC-ing Thilo about it.
--
Vittorio
On Wed, Jun 5, 2024 at 9:21 AM Marton Balint wrote:
>
>
> On Tue, 4 Jun 2024, Vittorio Giovara wrote:
>
> >> If you stop responding with mails on all FFmpeg mailing lists from now
> to
> >> indefinite time in future nothing of value would be lost.
> >>
On Thu, Jun 6, 2024 at 2:07 AM Michael Niedermayer
wrote:
> On Wed, Jun 05, 2024 at 12:31:28PM +0300, Rémi Denis-Courmont wrote:
> >
> >
> > Le 5 juin 2024 12:18:57 GMT+03:00, "Rémi Denis-Courmont" <
> r...@remlab.net> a écrit :
> > >But by reacting *only* to Vittorio trying to defend himself and
On Fri, Jun 7, 2024 at 3:19 PM Anton Khirnov wrote:
> ---
> libavcodec/hevc/hevcdec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/hevc/hevcdec.c b/libavcodec/hevc/hevcdec.c
> index 5fc55d5de9..88f2bcecad 100644
> --- a/libavcodec/hevc/hevcdec.c
> +++ b/lib
On Sat, Jun 8, 2024 at 6:02 PM Michael Niedermayer
wrote:
> On Tue, May 14, 2024 at 01:38:16AM +0200, Michael Niedermayer wrote:
> > Hi all
> >
> > To keep people updated (and as this is not vissible on the ML)
> > heres my current list of issues marked as false positives / intentional
> in Mai &
On Sat, Jun 8, 2024 at 9:45 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Andreas Rheinhardt:
> > Signed-off-by: Andreas Rheinhardt
> > ---
> > libavcodec/dnxhdenc.c | 33 +
> > 1 file changed, 17 insertions(+), 16 deletions(-)
> >
> > diff --gi
On Sun, Jun 9, 2024 at 12:50 AM Timo Rothenpieler
wrote:
> On 08.06.2024 21:49, Vittorio Giovara wrote:
> > On Sat, Jun 8, 2024 at 6:02 PM Michael Niedermayer <
> mich...@niedermayer.cc>
> > wrote:
> >
> >> On Tue, May 14, 2024 at 01:38:16AM +0200,
On Sat, Jun 8, 2024 at 9:58 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Vittorio Giovara:
> > On Sat, Jun 8, 2024 at 9:45 PM Andreas Rheinhardt <
> > andreas.rheinha...@outlook.com> wrote:
> >
> >> Andreas Rheinhard
On Mon, Jun 10, 2024 at 12:04 AM Michael Niedermayer
wrote:
> On Sun, Jun 09, 2024 at 03:10:09PM +0200, Vittorio Giovara wrote:
> > On Sun, Jun 9, 2024 at 12:50 AM Timo Rothenpieler >
> > wrote:
> >
> > > On 08.06.2024 21:49, Vittorio Giovara wrote:
>
On Mon, Jun 10, 2024 at 2:29 PM Michael Niedermayer
wrote:
> On Sun, Jun 09, 2024 at 04:08:48PM -0400, Sean McGovern wrote:
> [...]
> > Side note: it seems GMail now prevents sending patches directly with
> > git send-email
>
> I have difficulty believing this, but if so, the problem is gmail
> a
On Mon, Jun 10, 2024 at 2:41 PM Timo Rothenpieler
wrote:
> > In either case, my point is that email is not a good system for these
> > reports, because they cannot be tracked nor analyzed, and if they do
> pose a
> > security risk they shouldn't be advertised so openly. Having a small
> bounty
>
On Tue, Jun 11, 2024 at 3:49 PM Michael Niedermayer
wrote:
> On Tue, Jun 11, 2024 at 02:26:37PM +0300, Rémi Denis-Courmont wrote:
> >
> >
> > Le 11 juin 2024 12:59:23 GMT+03:00, Michael Niedermayer <
> mich...@niedermayer.cc> a écrit :
> > >On Mon, Jun 10, 2024 at 08:52:08PM -0400, Sean McGovern
On Thu, Jun 13, 2024 at 6:32 PM Sean McGovern wrote:
> On Tue, Jun 11, 2024, 10:15 Vittorio Giovara
> wrote:
>
> > On Tue, Jun 11, 2024 at 3:49 PM Michael Niedermayer <
> > mich...@niedermayer.cc>
> > wrote:
> >
> > > On Tue, Jun 11, 202
On Mon, Jun 17, 2024 at 8:34 PM Michael Niedermayer
wrote:
> On Tue, Apr 30, 2024 at 07:42:53PM +0200, Michael Niedermayer wrote:
> > On Mon, Apr 22, 2024 at 01:32:27PM +0200, Lynne wrote:
> > > Apr 22, 2024, 13:07 by stefa...@gmail.com:
> > >
> > > > On date Sunday 2024-04-21 22:12:56 -0300, Jam
On Mon, Jun 17, 2024 at 9:01 PM Nicolas George wrote:
> Michael Niedermayer (12024-06-17):
> > also if you look at google trends, even today more people search for
> ffserver
> > than txproto. In fact at every point in time more people searched for
> ffserver
> > than txproto.
> >
> > https://tre
On Sun, Jun 16, 2024 at 7:09 PM James Almer wrote:
> diff --git a/libavformat/nal.h b/libavformat/nal.h
> new file mode 100644
> index 00..ce49ea70b0
> --- /dev/null
> +++ b/libavformat/nal.h
> @@ -0,0 +1,66 @@
> +/*
> + * NAL helper functions for muxers
> + *
> + * This file is part of F
On Sat, Jun 22, 2024 at 3:22 PM Niklas Haas wrote:
> Hey,
>
> As some of you know, I got contracted (by STF 2024) to work on improving
> swscale, over the course of the next couple of months. I want to share my
> current plans and gather feedback + measure sentiment.
>
> ## Problem statement
>
>
On Sat, Jun 22, 2024 at 9:57 PM James Almer wrote:
> On 6/22/2024 12:31 PM, James Almer wrote:
> > We need a way to signal the frame has a single view that doesn't map to
> any
> > particular eye, and it should be the default one.
> >
> > Signed-off-by: James Almer
> > ---
> > Now updating all t
On Sun, Jun 23, 2024 at 7:57 PM James Almer wrote:
> On 6/22/2024 7:19 PM, Vittorio Giovara wrote:
> > Needless to say I support the plan of renaming the library so that it can
> > be inline with the other libraries names, and the use of a separate
> header
> > since down
On Sun, Jun 23, 2024 at 1:16 AM James Almer wrote:
> Given that a video stream/frame may have only one or both views coded with
> the packing information being unavailable, this commit adds a new type
> value
> AV_STEREO3D_UNSPEC for this purpose.
>
not to bikeshed the name, but why UNSPEC inste
On Sat, Jun 29, 2024 at 1:47 PM Niklas Haas wrote:
>
> Open questions:
>
> 1. Is this a good idea, or do the downsides outweigh the benefits?
> 2. Is an "advanced configuration" API still needed, in addition to the
>quality presets?
>
Having a sort of preset is a good idea, esp to simplify t
On Fri, Oct 13, 2023 at 10:27 AM Niklas Haas wrote:
> Changes since v1:
>
> - Remove unneeded patch (AVCodecContext.colorspace init)
> - Merge auto-range conversion into auto-scale filter
> - Replace vf_zscale by vf_colorspace in fftools
>
Why is this? I haven't checked what vf_colorspace suppor
On Fri, Oct 13, 2023 at 1:09 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> 2. It is based around the underlying assumption that the set of
> permissible states (tupels) is a cartesian product of a set of color
> spaces, a set of color ranges etc. This is wrong: E.g. VP9 disallow
On Fri, Oct 13, 2023 at 3:19 PM Michael Niedermayer
wrote:
> Hi everyone
>
> I propose using 15k$ from SPI for funding sws cleanup work.
> this is substantially less than what people belive this needs (see IRC
> logs from yesterday or so)
> So it really is more a small price for a good deed and n
On Fri, Oct 13, 2023 at 10:21 AM Niklas Haas wrote:
> From: Niklas Haas
>
> Curiously absent.
> ---
> libavfilter/vf_showinfo.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavfilter/vf_showinfo.c b/libavfilter/vf_showinfo.c
> index bf8580bc8d..71869446c6 10064
On Fri, Oct 13, 2023 at 5:14 PM Lynne wrote:
> Oct 13, 2023, 20:33 by vittorio.giov...@gmail.com:
>
> > On Fri, Oct 13, 2023 at 10:27 AM Niklas Haas wrote:
> >
> >> Changes since v1:
> >>
> >> - Remove unneeded patch (AVCodecContext.colorspace init)
> >> - Merge auto-range conversion into auto-s
On Fri, Oct 13, 2023 at 6:55 PM Niklas Haas wrote:
> On Fri, 13 Oct 2023 19:42:44 -0300 James Almer wrote:
> > Anton wrote and pushed an AVFrame based API. It can surely be
> > improved/extended to use AVFrame metadata.
>
> Yes, this is actually a good idea. This API endpoint already has the
> "
On Sat, Oct 14, 2023 at 9:11 AM Lynne wrote:
> Oct 14, 2023, 00:22 by vittorio.giov...@gmail.com:
>
> > On Fri, Oct 13, 2023 at 5:14 PM Lynne wrote:
> >
> >> Oct 13, 2023, 20:33 by vittorio.giov...@gmail.com:
> >>
> >> > On Fri, Oct 13, 2023 at 10:27 AM Niklas Haas
> wrote:
> >> >
> >> >> Chang
On Sat, Oct 14, 2023 at 1:00 PM Michael Niedermayer
wrote:
>
> PS: whats the real issue with sws ?
> it evolved out of a piece yuv->rgb converter from a video player.
> It evolved from that and stuff was added into it.
> This is a similar situation to why ffmpeg.c needed cleanup
>
I'll give you
On Fri, Oct 20, 2023 at 8:14 AM Ronald S. Bultje wrote:
> 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 i
On Fri, Oct 20, 2023 at 7:30 AM Niklas Haas wrote:
> On Fri, 13 Oct 2023 14:33:11 -0400 Vittorio Giovara <
> vittorio.giov...@gmail.com> wrote:
> > On Fri, Oct 13, 2023 at 10:27 AM Niklas Haas wrote:
> >
> > > Changes since v1:
> > >
> > > - Re
On Sat, Oct 21, 2023 at 4:20 PM Michael Niedermayer
wrote:
> On Fri, Oct 20, 2023 at 07:13:00PM -0400, Ronald S. Bultje wrote:
> > Hi,
> >
> > On Fri, Oct 20, 2023 at 12:14 PM Vittorio Giovara <
> > vittorio.giov...@gmail.com> wrote:
> >
> > > tbh
On Thu, Oct 26, 2023 at 11:59 AM Derek Buitenhuis <
derek.buitenh...@gmail.com> wrote:
> On 10/25/2023 2:14 PM, Thilo Borgmann via ffmpeg-devel wrote:
> > To test the voting beforehand this time, I created a test vote with a
> fake-GA member list. All of the following people should have received a
On Fri, Oct 27, 2023 at 10:06 AM Niklas Haas wrote:
> From: Niklas Haas
>
> PGMYUV seems to be always limited range. This was a format originally
> invented by FFmpeg at a time when YUVJ distinguished limited from full
> range YUV, and this codec never appeared to output YUVJ in any
> circumstan
On Fri, Oct 27, 2023 at 10:05 AM Niklas Haas wrote:
> From: Niklas Haas
>
> Alpha planes are explicitly full range, even for limited range YUVA
> formats. Mark them as such.
> ---
> libavfilter/vf_extractplanes.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/libavfilter/vf_extractp
On Fri, Oct 27, 2023 at 10:06 AM Niklas Haas wrote:
> From: Niklas Haas
>
> When using vf_scale to force a specific output color space, also tag
> this on the AVFrame. (Mirroring existing logic for output range)
> ---
> libavfilter/vf_scale.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff
On Mon, Nov 6, 2023 at 1:50 PM Nicolas George wrote:
> Paul B Mahol (12023-11-06):
> > Gonna apply soon.
>
> No you are not.
>
While I appreciate the brevity of this email, I think this kind of
communication is non constructive.
If the mailing list is the only and universal voice of the project,
On Sun, Nov 5, 2023 at 5:02 AM Anton Khirnov wrote:
> Hi all,
> as previously discussed, we need to re-elect the members of the
> Technical and Community Committees. As a reminder - the Technical
> Committee (TC) resolves technical disputes, while the Community
> Committee (CC) resolves personal
On Mon, Nov 6, 2023 at 3:07 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > Nicolas, have you thought of providing a patch to the bug Paul is
> > describing?
>
> Why do you not ask Paul if he have thought of giving me time to have a
> chance to do so?
>
On Mon, Nov 6, 2023 at 3:28 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > You gave no indication you were willing to, and I thought he gave you
> time
>
> Bullshit. Please do not intervene in a thread when you do not know what
> is going on at all. Paul has
On Mon, Nov 6, 2023 at 3:50 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > world, please make a minimum of effort to keep communication polite
>
> Please realize that politeness resides not only in which words we use,
> like “bullshit”, but also in what we say,
On Mon, Nov 6, 2023 at 4:46 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > Nice try but pointing out your logical fallacies is not being rude, but
> > rather is just showing you how easily your message can be misinterpreted,
>
> You have done nothing of th
On Mon, Nov 6, 2023 at 5:49 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > I'm not misrepresenting anybody's words,
>
> Me: “I never doubted that Paul's patches do make the bug go away in your
> test case.”
>
> You: “you insisted
On Mon, Nov 6, 2023 at 6:05 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > Stop twisting people's words and implying things they never said :)
>
> This is not you presenting excuses.
>
Correct, it's you trying to win arguments with aggressive commun
On Tue, Nov 7, 2023 at 2:44 AM Nicolas George wrote:
> Vittorio Giovara (12023-11-06):
> > Correct, it's you trying to win arguments with aggressive communication
>
> No. You came into an argument without knowing the first thing about it
> and you decided to side wi
On Wed, Nov 8, 2023 at 3:46 PM Alexander Strasser wrote:
> On 2023-11-08 12:40 +0100, Anton Khirnov wrote:
> > Quoting Michael Niedermayer (2023-10-31 09:40:44)
> > > On Mon, Oct 30, 2023 at 02:11:27PM +0100, Andreas Rheinhardt wrote:
> > > > Section 7.4.4 of the MPEG-2 specifications requires th
On Thu, Nov 9, 2023 at 6:55 AM Michael Niedermayer
wrote:
> Fabrice Bellard(Founder of the project over 600 commits in FFmpeg)
> Aman Karmani (17 authored commits in 2020-2023, recently active in
> 2023-June and work all over the codebase)
> Baptiste Coudurier (Pays for our fate server
On Thu, Nov 9, 2023 at 10:40 AM Michael Niedermayer
wrote:
> On Thu, Nov 09, 2023 at 07:11:37AM -0500, Vittorio Giovara wrote:
> > On Thu, Nov 9, 2023 at 6:55 AM Michael Niedermayer <
> mich...@niedermayer.cc>
> > wrote:
> >
> > > Fabrice Bellard(Fou
On Thu, Nov 9, 2023 at 3:17 PM 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-Courmont wrote:
> > >> Le torstaina 9. m
On Fri, Nov 10, 2023 at 2:31 PM Michael Niedermayer
wrote:
> On Fri, Nov 10, 2023 at 02:24:23PM +0200, Rémi Denis-Courmont wrote:
>
> > [...] or at least allow people to resign from the GA discretionarily.
>
> I think this makes alot more sense
>
> Asking "I want to be in the GA" fully in public
On Sat, Nov 11, 2023 at 1:27 PM Nicolas George wrote:
> Paul B Mahol (12023-11-11):
> > I waited enough, applied, now for 100% true statement.
>
> Your teacher called, you forgot your pacifier in class yesterday
>
No, bad Nicolas, stop this language, it's unacceptable and unbecoming. You
can ask
On Sat, Nov 11, 2023 at 2:22 AM Thilo Borgmann via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> Hi,
>
> in [1] JB listed his list of authorized voters for the "GA voters list
> updates"
> vote.
>
> This list does not correlate with the list Josh provided in [2].
> Neither does this list of 51
On Sat, Nov 11, 2023 at 1:42 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-11):
> > No, bad Nicolas, stop this language, it's unacceptable and unbecoming.
> You
> > can ask for more time in a kinder manner.
> > No, don't reply to me with insults or excus
On Sat, Nov 11, 2023 at 1:52 PM Nicolas George wrote:
> itself), but I remember observing that several members were in fact very
> biassed.
>
[citation needed]
--
Vittorio
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailma
On Sat, Nov 11, 2023 at 2:04 PM Nicolas George wrote:
> Vittorio Giovara (12023-11-11):
> > I said don't reply to me!
>
> Fortunately you have no authority over me.
>
I said that to avoid ridiculing yourself any more
> > I'm not bi
This is ridiculous, and everybody involved in this second vote should be
ashamed of themselves.
-- Forwarded message -
From: Thilo Borgmann (CIVS poll supervisor)
If you would like to vote, please visit the following URL:
https://vote.ffmpeg.org/cgi-bin/civs/vote.pl?id=E_07e
On Tue, Nov 14, 2023 at 10:56 AM Tomas Härdin wrote:
> Ballot secrecy cannot actually be guaranteed. While I'm not versed in
> the specifics of CIVS, I doubt it has solved problems like evil
> sysadmin. Ballots should be public IMO, secret voting is cowardice.
> That way duplicate ballots are eas
On Tue, Nov 14, 2023 at 2:28 PM Nicolas George wrote:
> I hope you can grasp the difference between CAN and WOULD. That would be
> better than calling somebody's logical arguments “FUD”.
>
You're right, we should call things by their name, these arguments are
illogical.
--
Vittorio
On Sun, Nov 19, 2023 at 7:11 PM Michael Niedermayer
wrote:
> On Tue, Nov 14, 2023 at 07:46:16PM +0100, Michael Niedermayer wrote:
> > On Tue, Nov 14, 2023 at 06:32:19PM +0100, Hendrik Leppkes wrote:
> > > On Tue, Nov 14, 2023 at 6:21 PM Michael Niedermayer
> > > wrote:
> > > >
> > > > Signed-off
On Mon, Dec 4, 2023 at 1:53 PM Nicolas George wrote:
> Anton Khirnov (12023-12-02):
> > 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.
>
> Only tes
On Tue, Dec 5, 2023 at 2:45 AM Nicolas George wrote:
> Vittorio Giovara (12023-12-04):
> > It's almost 2024, when will you be able to drop it?
>
> Never. When will YOU be able to drop bickering about parts of the code
> that do no harm and do not bother you?
>
I'
On Tue, Dec 5, 2023 at 9:59 AM Nicolas George wrote:
> Vittorio Giovara (12023-12-05):
> > I'm not bickering,
>
> That is exactly what you do.
>
And you are not? The view must be great from that glass house
> actively include testing as part of the bare minimum proce
On Wed, Dec 6, 2023 at 5:30 AM Anton Khirnov wrote:
> Hi,
> this should hopefully be the last version of this set. If nobody has new
> comments, I will push it in a few days.
>
LGTM
--
Vittorio
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
htt
On Wed, Dec 6, 2023 at 3:14 PM Nicolas George wrote:
> Lie.
>
A summary of your proposal or a link to your suggestion would be
appreciated.
Without reference we're all shouting in the void.
> I guess now that your side holds most of the power the mask is off.
>
> This mail you just sent should
I ain't reading all of that
Happy for you
Or sorry that happened
On Wed, Dec 6, 2023 at 3:47 PM Nicolas George wrote:
> Vittorio Giovara (12023-12-05):
> > Your attitude for "omgfeatures" is also pretty toxic, there are heaps of
> > literature about feature cr
On Wed, Dec 6, 2023 at 3:23 AM Marton Balint wrote:
> diff --git a/libavcodec/decode.c b/libavcodec/decode.c
> index 2cfb3fcf97..f9b18a2c35 100644
> --- a/libavcodec/decode.c
> +++ b/libavcodec/decode.c
> @@ -1675,6 +1675,12 @@ FF_ENABLE_DEPRECATION_WARNINGS
>
> validate_avframe_allocation(a
Missed from a5b2b22d9a45c9634e6947d43945ebafe121abec.
0001-MAINTAINERS-Remove-older-s3tc-entry.patch
Description: Binary data
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, vis
Fixes compilation, introduced in e37b15e.
src/libavdevice/avfoundation.m:799:10: error: invalid preprocessing
directive
#elseif (TARGET_OS_OSX && __MAC_OS_X_VERSION_MAX_ALLOWED < 14)
--
Vittorio
0001-lavd-avfoundation-Use-correct-preprocessing-directiv.patch
Description: Binary data
On Mon, Dec 11, 2023 at 12:37 PM Thilo Borgmann via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> Am 11.12.23 um 18:29 schrieb Vittorio Giovara:
> > Fixes compilation, introduced in e37b15e.
> >
> > src/libavdevice/avfoundation.m:799:10: error: invalid preprocess
This is an older filter I wrote and never got around publishing.
It can be used to generate a distortion effect like
https://vimeo.com/104938599?share=copy
Please see attached.
--
Vittorio
0001-Add-new-vf_tiltandshift-filter.patch
Description: Binary data
On Tue, Dec 12, 2023 at 3:00 AM Nicolas George wrote:
> Vittorio Giovara (12023-12-11):
> > This is an older filter I wrote and never got around publishing.
> > It can be used to generate a distortion effect like
> > https://vimeo.com/104938599?share=copy
> > Please
On Fri, Dec 15, 2023 at 12:34 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> > +static int list_add_frame(FrameList **list, size_t *size, AVFrame
> > *frame)
> > +{
> > +FrameList *element = av_mallocz(sizeof(FrameList));
>
> The overhead of this FrameList is unnecessary: You
On Tue, Mar 26, 2019 at 10:47 PM Jing Sun wrote:
> Signed-off-by: Zhengxu Huang
> Signed-off-by: Hassene Tmar
> Signed-off-by: Jun Zhao
> Signed-off-by: Jing Sun
> ---
> configure| 4 +
> libavcodec/Makefile | 1 +
> libavcodec/allcodecs.c | 1 +
> libavcodec/lib
On Fri, Mar 29, 2019 at 5:28 AM Jing Sun wrote:
> +static int config_enc_params(EB_H265_ENC_CONFIGURATION *param,
> + AVCodecContext *avctx)
> +{
> +SvtContext *svt_enc = avctx->priv_data;
> +int ret;
> +
> +param->sourceWidth = avctx->width;
> +param->
On Wed, Apr 17, 2019 at 12:26 AM Gyan wrote:
>
>
> On 13-04-2019 05:23 PM, Gyan wrote:
> > Will be helpful for correct result in filters that paint like
> > fillborders/drawbox or those using drawutils.
>
> Ping.
>
these seem to only work for 8 bit content, is that their only intended
usecase?
i
On Tue, Apr 16, 2019 at 3:42 AM Gyan wrote:
> Patch revised as per
> http://www.ffmpeg.org/pipermail/ffmpeg-devel/2019-April/242591.html
>
> Gyan
>
sorry if i'm late to the party but why are these new fields in
avcodeccontext?
they seem to be perfect candidates for side data, or am i missing som
On Tue, Apr 30, 2019 at 6:07 AM Paul B Mahol wrote:
> Signed-off-by: Paul B Mahol
> ---
> libavfilter/vf_tonemap.c | 39 ++-
> 1 file changed, 34 insertions(+), 5 deletions(-)
>
> diff --git a/libavfilter/vf_tonemap.c b/libavfilter/vf_tonemap.c
> index efd4af
On Thu, May 16, 2019 at 9:32 PM Jun Li wrote:
> On Thu, May 16, 2019 at 4:34 PM Ted Meyer <
> tmathmeyer-at-google@ffmpeg.org> wrote:
>
> > Right now ffmpeg doesn't export a mirroring status when checking the
> > display matrix for rotation.
> > Here is an example video: https://files.tedm.io
On Wed, May 29, 2019 at 2:28 PM Derek Buitenhuis
wrote:
> Uses the crav1e C bindings for rav1e.
> --- a/doc/encoders.texi
> +++ b/doc/encoders.texi
> @@ -1378,6 +1378,35 @@ makes it possible to store non-rgb pix_fmts.
>
> @end table
>
> +@section librav1e
> +
> +rav1e AV1 encoder wrapper.
> +
>
On Sat, Jun 8, 2019 at 9:28 AM Antonin Gouzer
wrote:
> ---
> Some codecs editors had miss interpreted the H264 standart and
> have coded a wrong size in the SEI data.
> size = SEI size + 1.
> The SEI data is detected as "truncated"
> Ex:
> https://drive.google.com/file/d/1cNtLwnfPnyJnYqE7OYhU3SCo
On Thu, Jun 27, 2019 at 9:44 AM Nicolas George wrote:
> Kieran Kunhya (12019-06-27):
> > I'm happy to do it now that I am aware of the issue. I will do it when I
> am
> > at home in a few days.
>
> Thanks. I am sure Steven will not mind waiting a few days.
>
> > This absolutism is absurd.
>
> Do
On Wed, Jul 3, 2019 at 12:51 AM vincenluo(罗永林)
wrote:
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
Great find, your patch is absolutely correct.
Pushing soon, thank you.
--
Vittorio
_
On Tue, Jul 16, 2019 at 10:29 PM Limin Wang wrote:
> On Tue, Jul 16, 2019 at 09:36:32PM -0400, Rick Kern wrote:
> > Testing for the new transfer functions when compiling for OSX 10.12
> reports
> > the color settings as "yuv420p(tv, bt2020nc/bt2020/reserved)" in ffprobe.
> > Is "reserved" (0) the
Some broken apps generate files that have a fake box named 'hoov'
instead of a proper 'moov' one. This is speculation but it seems like
this box contains data to be modified later (eg as file grows in size,
data gets re-written) and its name is supposed to be changed to 'moov'
once it can be used a
On Fri, Aug 9, 2019 at 3:29 AM wrote:
> From: Raphaël Zumer
>
> This is an alias for JEDEC P22.
>
> The name associated with the value is also changed
> from "jedec-p22" to "ebu3213" to match ITU-T H.273.
>
> Signed-off-by: Raphaël Zumer
> ---
> doc/APIchanges | 3 +++
> libavutil/pixdesc
On Thu, Aug 8, 2019 at 10:28 PM Vittorio Giovara
wrote:
> Some broken apps generate files that have a fake box named 'hoov'
> instead of a proper 'moov' one. This is speculation but it seems like
> this box contains data to be modified later (eg as file grows in size
On Mon, Aug 12, 2019 at 9:19 PM Michael Niedermayer
wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavcodec/decode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/decode.c b/libavcodec/decode.c
> index 6c31166ec2..09a509d659 100644
> --- a/libavcodec
On Wed, Aug 14, 2019 at 10:11 PM Reimar Döffinger
wrote:
> On 14.08.2019, at 11:45, Paul B Mahol wrote:
> > I strongly disagree with you. Why some people have subscription to
> security
> > mailing list and I'm not allowed also?
>
> Long version, explaining to the best of my knowledge and memory
On Wed, Aug 22, 2018 at 9:53 PM, Devin Heitmueller <
dheitmuel...@ltnglobal.com> wrote:
> Implement support for including AFD in decklink output. This
> includes making sure the AFD data is preserved when going from
> an AVFrame to a V210 packet (needed for 10-bit support).
>
> Updated to reflect
1 - 100 of 604 matches
Mail list logo
