On Sun, Jan 28, 2024 at 11:47 PM Michael Niedermayer
wrote:
> On Sun, Jan 28, 2024 at 01:28:36PM +0100, Anton Khirnov wrote:
> > Previously, the implicit standard was to wait 2 years before deprecation
> > and removal, but it has been widely agreed at developer meetings that
> > time-based measur
On Sun, Jan 28, 2024 at 10:32 PM Connor Worley
wrote:
> I'd like to get this series merged before doing any further DXV work. Is
> anyone able to help with uploading the linked samples?
>
I unfortunately don't have access to the FATE samples server, can you mail
samples-requ...@ffmpeg.org?
--
V
On Mon, Jan 29, 2024 at 8:58 AM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Michael Niedermayer:
> > On Sun, Jan 28, 2024 at 08:52:20PM -0300, James Almer wrote:
> >> On 1/28/2024 7:41 PM, Michael Niedermayer wrote:
> >>> On Sun, Jan 28, 2024 at 02:49:26PM +0100, Andreas Rheinhar
On Thu, Jan 25, 2024 at 2:48 PM James Almer wrote:
> Signed-off-by: James Almer
> ---
> doc/APIchanges| 2 +-
> libavcodec/version.h | 2 +-
> libavcodec/version_major.h| 2 +-
> libavdevice/version.h | 2 +-
> libavdevice/version_major.h | 2 +-
> libavfi
On Wed, Jan 24, 2024 at 9:06 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> It presumably exists because HapContext contains an AVClass*.
> Yet AVClass is actually defined in log.h and even this inclusion
> can be avoided by struct AVClass*. This avoids opt.h inclusions
> in hap.
On Fri, Jan 19, 2024 at 8:17 PM Connor Worley
wrote:
> I've tested the latest patch with both the lavc decoder and Resolume's
> proprietary software, and the encoded outputs are working for me.
>
Pushed, thank you
--
Vittorio
___
ffmpeg-devel mailing
On Fri, Jan 19, 2024 at 5:56 PM Connor Worley
wrote:
> Thanks for the feedback! For the next revision, is it preferred to reply
> to this thread or create a new one?
>
here is fine
> On 1/19/24 08:23, Vittorio Giovara wrote:
> >> diff --git a/libavcodec/allcodecs.c b/l
n order
> extern const FFCodec ff_eacmv_decoder;
> extern const FFCodec ff_eamad_decoder;
> diff --git a/libavcodec/dxvenc.c b/libavcodec/dxvenc.c
> new file mode 100644
> index 00..33080fa1c9
> --- /dev/null
> +++ b/libavcodec/dxvenc.c
> @@ -0,0 +1,358 @@
> +/*
On Tue, Jan 2, 2024 at 4:06 PM Kieran Kunhya wrote:
> >
> > > and not the CLI (something this project is unable to understand).
> >
> > What is exposed by the API is exercised by the CLI (which is a good
> > thing for scripting and for testing).
> >
>
> The CLI can't just write random binary data
On Thu, Dec 21, 2023 at 6:14 PM Nicolas George wrote:
> Vittorio Giovara (12023-12-21):
> > I agree, I hope you can work on your lack of self-awareness.
>
> Oh, the “Ah ?… Et moi, Cyrano-Savinien-Hercule De Bergerac.” comeback.
> You're really scrapping the bottom of
On Thu, Dec 21, 2023 at 5:41 PM Nicolas George wrote:
> Vittorio Giovara (12023-12-21):
> > Not sure what gave you the idea
>
> Mails like this one for example. The lack of self-awareness is
> hilarious.
>
I agree, I hope you can work on your lack of self-aw
On Thu, Dec 21, 2023 at 5:22 PM Nicolas George wrote:
> Vittorio Giovara (12023-12-21):
> > Oh so you know how it feels!
>
> I am not surprised to see your animosity against me is stronger than
> your care about the project.
>
Not sure what gave you the idea, but I have no
On Wed, Dec 20, 2023 at 2:56 PM Vittorio Giovara
wrote:
>
>
> On Wed, Dec 20, 2023 at 2:50 PM Nicolas George wrote:
>
>> Vittorio Giovara (12023-12-20):
>> > If there are no more comments, I'll push this today or tomorrow.
>>
>> I think the change
On Thu, Dec 21, 2023 at 3:05 PM Paul B Mahol wrote:
> On Thu, Dec 21, 2023 at 8:43 PM Tomas Härdin wrote:
>
> > ons 2023-12-20 klockan 20:11 +0100 skrev Michael Niedermayer:
> > > On Wed, Dec 20, 2023 at 05:57:40PM +0100, Tomas Härdin wrote:
> > > > tis 2023-12-19 klockan 15:02 +0100 skrev Nicol
On Thu, Dec 21, 2023 at 3:31 PM Nicolas George wrote:
> Paul B Mahol (12023-12-21):
> > Say what serious feature you contributed ? - Nothing.
>
> I did not want to say it, but since it is now in the open: Not nothing:
> negative. His naysaying discouraged me from working further on the
> built-in
On Wed, Dec 20, 2023 at 2:50 PM Nicolas George wrote:
> Vittorio Giovara (12023-12-20):
> > If there are no more comments, I'll push this today or tomorrow.
>
> I think the change you made after the last request might go too far, but
> I have not had time to look at the c
On Fri, Dec 15, 2023 at 3:12 PM Vittorio Giovara
wrote:
>
>
> 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)
>> &
On Tue, Dec 19, 2023 at 8:12 AM Nicolas George wrote:
> Rémi Denis-Courmont (12023-12-07):
> > You have had heated arguments against Paul in recent times too. You have
> also
> > argued a lot of exercising your review privileges, which sounds like a
> very
> > libavish notion to me
>
> Only becau
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, 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
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 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
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
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
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
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: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
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 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 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 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 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 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 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
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 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
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 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 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: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 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 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 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 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 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 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 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 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 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 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 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: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 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 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 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 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
>
> 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 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 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 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 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 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 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 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 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 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 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 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 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 Tue, Oct 3, 2023 at 12:03 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Signed-off-by: Andreas Rheinhardt
> ---
> libavcodec/rv10.c | 21 +
> 1 file changed, 5 insertions(+), 16 deletions(-)
>
> diff --git a/libavcodec/rv10.c b/libavcodec/rv10.c
> index
On Wed, Oct 4, 2023 at 12:40 PM Vignesh Venkatasubramanian via ffmpeg-devel
wrote:
> They are similar to AVIF images (both use the HEIF container).
> The only additional work needed is to parse the hvcC box and put
> it in the extradata.
>
> With this patch applied, ffmpeg (when built with an HEV
On Thu, Oct 5, 2023 at 8:55 AM Nicolas George wrote:
> Anton Khirnov (12023-10-04):
> > It is IMO perfectly reasonable to wonder why does someone who does not
> > agree with the basic rules participate in the project.
>
> Or you could have given the issue just two more seconds of thought and
> re
On Wed, Oct 4, 2023 at 12:02 AM Vignesh Venkat via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> On Tue, Oct 3, 2023 at 6:32 PM Vittorio Giovara
> wrote:
> >
> > On Tue, Oct 3, 2023 at 8:30 PM Steven Liu
> wrote:
> >
> > > > > 2.42.0.51
On Tue, Oct 3, 2023 at 7:05 PM Vignesh Venkatasubramanian via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> This is not allowed per the spec.
>
> Signed-off-by: Vignesh Venkatasubramanian
> ---
> libavformat/mov.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/libavformat/mov.c b/
On Tue, Oct 3, 2023 at 8:30 PM Steven Liu wrote:
> > > 2.42.0.515.g380fc7ccd1-goog
> > >
> >
> > Any comments/objections on merging this?
>
>
> Can this patch support tiled hevc coded or sequence heif？=
>
I believe that will be possible only after AVStreamGroup is implemented.
Vignesh is there
On Tue, Oct 3, 2023 at 2:50 PM Nicolas George wrote:
> Vittorio Giovara (12023-09-27):
> > This is basically saying that you don't trust the community to make the
> > best decisions for itself, or that the community is not mature enough to
> > stand on its own to suppor
On Fri, Sep 29, 2023 at 5:12 PM John Mather via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:
> This patch makes the libkvazaar encoder respect color settings that are
> present on the codec context, including color range, primaries, transfer
> function and colorspace.
> ---
> libavcodec/libkvaz
On Fri, Sep 29, 2023 at 3:03 AM Nicolas George wrote:
> Well, I think this makes it obvious why I think people representing
> downstream projects should have very little influence on the future of
> FFmpeg.
>
In a previous thread you said SDR shouldn't be a separate library because
it wastes dow
On Thu, Sep 28, 2023 at 3:28 PM Michael Niedermayer
wrote:
> On Thu, Sep 28, 2023 at 12:28:22PM +0200, Anton Khirnov wrote:
> > Quoting Michael Niedermayer (2023-09-23 18:43:44)
> > > Is a seperate library really the right choice for SDR in FFmpeg at
> this stage ?
> > >
> > > Also code can alway
On Thu, Sep 28, 2023 at 11:08 AM Niklas Haas wrote:
> On Wed, 27 Sep 2023 21:07:55 +0200 Michael Niedermayer <
> mich...@niedermayer.cc> wrote:
> > where can i find the text describing this that you refer to ?
>
> It is in SMPTE RDD 5 (DOI 10.5594/SMPTE.RDD5.2006), you can find it on
> the usual
On Wed, Sep 27, 2023 at 6:01 AM Michael Niedermayer
wrote:
> What we have currently is not a king making decissions.
> What we have currently is the founder having a final (very difficult to
> use)
> veto power to prevent something catastrophic
>
This is basically saying that you don't trust the
On Tue, Sep 26, 2023 at 2:24 PM Nicolas George wrote:
> Anton Khirnov (12023-09-26):
> > It is not. From my perspective, the objections to SDR have been largely
> > technical
>
> We have not read the same discussion. The objections to SDR start and
> end at “it does not belong in FFmpeg”, which i
On Thu, Sep 21, 2023 at 3:05 PM Nicolas George wrote:
> Vittorio Giovara (12023-09-21):
> > What about other developers' time for maintenance?
>
> Yes, what about it?
>
> How much time did YOU spend maintaining libavfilter or libavdevice?
> Zero.
>
> How much
On Thu, Sep 21, 2023 at 2:51 PM Nicolas George wrote:
> Vittorio Giovara (12023-09-21):
> > Good, if it's so isolated it can be moved to a separate library and we're
> > arguing over nothing.
>
> Wasting Michael's time for the maintenance and users' time
On Thu, Sep 21, 2023 at 2:19 PM Nicolas George wrote:
> Vittorio Giovara (12023-09-21):
> > Because it adds maintenance burden and it's out of scope with the proejct
>
> The feature is isolated, so that is a lie.
>
Good, if it's so isolated it can be moved to
On Thu, Sep 21, 2023 at 1:16 PM Nicolas George wrote:
> Kieran Kunhya via ffmpeg-devel (12023-09-21):
> > How on earth is it acceptable that you can publish your hobby project
> > under the FFmpeg project name?
>
> How on earth is it acceptable that you continue bikeshedding a feature
> that some
On Fri, Sep 8, 2023 at 11:22 AM Ronald S. Bultje wrote:
> Hi,
>
> On Fri, Sep 8, 2023 at 9:10 AM Michael Niedermayer >
> wrote:
>
> > On Thu, Aug 17, 2023 at 07:42:17PM +0200, Jean-Baptiste Kempf wrote:
> > [...]
> > > Propose a talk, from 5min to 30min.
> >
> > As i will not be at the conferenc
On Mon, Aug 28, 2023 at 2:38 PM James Almer wrote:
> Signed-off-by: James Almer
> ---
> libavcodec/hevcdec.c | 15 ++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/libavcodec/hevcdec.c b/libavcodec/hevcdec.c
> index df40c91ba6..dabfe89d4a 100644
> --- a/libavco
On Fri, Aug 25, 2023 at 5:24 PM Anton Khirnov wrote:
> Quoting Rémi Denis-Courmont (2023-08-25 17:09:55)
> > Le perjantaina 25. elokuuta 2023, 17.58.40 EEST Anton Khirnov a écrit :
> > > > And then sometimes an argument has been argued to death previously
> and
> > > > there is really no point to
On Fri, Aug 25, 2023 at 8:46 AM Nicolas George wrote:
> Vittorio Giovara (12023-08-25):
> > NAK
> > we shouldn't put extra burden on reviewers, nor guilt trap them into
> > suggesting an alternative approach
>
> It is hilarious, in a very sad way, that you prefer
On Thu, Aug 24, 2023 at 9:56 PM Michael Niedermayer
wrote:
> Suggested text is from Anton
>
> Signed-off-by: Michael Niedermayer
> ---
> doc/developer.texi | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/doc/developer.texi b/doc/developer.texi
> index 0c2f2cd7d1..383120daaa 100644
>
On Mon, Aug 21, 2023 at 9:49 PM Andreas Rheinhardt <
andreas.rheinha...@outlook.com> wrote:
> Actually, x264 allows to select only eight or ten bit bitdepth (or both)
> at configure-time. IIRC opening the encoder will fail if an eight-bit
> only libx264 is used when one tries to use a 10bit pixel
On Thu, Aug 10, 2023 at 5:27 PM Michael Niedermayer
wrote:
> Several developers where upset, that from the over 1gb of fate samples 2mb
> are only used
> by the ffmpeg branch with SDR support in https://git.ffmpeg.org/libavradio
>
> This avoids these samples from being downloaded or synchronized.
On Thu, Aug 10, 2023 at 2:39 PM Nicolas George wrote:
> > No. You are taking for granted that SDR belongs in FFmpeg in the first
> place,
> > and that's exactly what people disagree with.
>
> And you are taking for granted that it does not belongs in FFmpeg.
>
> But what you refuse to realize is
On Sat, Aug 5, 2023 at 8:55 PM Michael Niedermayer
wrote:
> Hi
>
> replying to the other question too
>
> On Wed, Aug 02, 2023 at 04:44:14PM +0200, Jean-Baptiste Kempf wrote:
> > On Wed, 2 Aug 2023, at 16:20, Michael Niedermayer wrote:
> > > There are multiple problems but the real problem is tha
On Sun, Jul 30, 2023 at 3:04 PM Nicolas George wrote:
> Kieran Kunhya (12023-07-28):
> > FFmpeg doesn't implement TCP in userspace, it doesn't implement the
> > WiFi protocol etc etc. Different layers are delegated to different
> > programs.
>
> Hi. You seem to be discussing this in more good fai
On Sat, Jul 15, 2023 at 4:51 PM Raphaël Zumer
wrote:
> Hello,
>
> Tagging this as RFC in case there is disagreement on the correct/desired
> behavior.
>
> For context:
> I am working with spatial audio and noticed that FFmpeg does not honor the
> SA3D box metadata, which is used to signal ambison
On Sat, Apr 29, 2023 at 8:29 PM Kieran Kunhya wrote:
> On Sat, 29 Apr 2023 at 05:07, Derek Buitenhuis >
> wrote:
>
> > On 4/29/2023 10:41 AM, Anton Khirnov wrote:
> > > ffprobe:
> > > * is not one of the libraries, but rather their caller
> > > * we are not in business of providing random non-mu
On Fri, Aug 12, 2022 at 12:51 AM Derek Buitenhuis <
derek.buitenh...@gmail.com> wrote:
> As it exists right now though, I don't really see why lavf needs what
> amounts to a URL builder for a service as a "protocol" - this totally
> the wrong layer to do that at...
>
Agreed, this protocol should
On Tue, May 31, 2022 at 7:17 PM Ronald S. Bultje wrote:
> Hi,
>
> On Thu, May 19, 2022 at 4:42 PM Mohammad Izadi <
> izadi-at-google@ffmpeg.org> wrote:
>
> > ffmpeg support YCOCG (YCOCG=YCGCO). However, vf_colorspace is only
> support
> > YCGCO as input. Added YCOCG to the inputs.
> > ---
> >
101 - 200 of 603 matches
Mail list logo
