Re: [FFmpeg-devel] [VOTE] Ban Carl Eugen Hoyos

Paul B Mahol wrote: >As requested in the IRC meeting I hereby request for the >voting committee to begin voting on whatever to ban Carl >Eugen Hoyos from mailing list, trac and IRC for 4 months, >starting after the voting has finished. If I have the right to vote, then I vote no. Best regards,

Re: [FFmpeg-devel] bans

Michael Niedermayer wrote: >1. ban carl for 24h >2. ban derek for ~24h >3. ban myself for ~24h May I suggest to stop the Kindergarten for the next 24 years? Kindest regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [VOTE] Ban Carl Eugen Hoyos

Paul B Mahol wrote: >Looks like you prefer to loose valuable developers instead >of punishing bad behaviour, so be it. We like to loose nobody, neither you nor Carl. Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH] avcodec/dpxenc: support colour metadata in DPX encoder, fixes ticket #6023

Vittorio Giovara wrote: >I think the code looks fine. I am just wondering if we >should also offer the possibility to set these flags from >the standard context options (-color_trc and others). I'm >aware that not all values match or are valid but maybe a >small conversion table or extending the

Re: [FFmpeg-devel] FFmpeg 3.3

Michael Niedermayer wrote: >Its a while since the last relase so ill make 3.3 within >the next week(s) Thank you, Michael! >I also intend to make some new point releases from the >currently maintained branches if someone wants to backport >something I suggest to switch "Nash" 2.7.7 to the old

Re: [FFmpeg-devel] [PATCH 1/2] avfilter: change ff_inlink_make_frame_writable() to take AVFrame* argument

Michael Niedermayer wrote: >But id like to ask everyone to NOT escalate this further, >iam sure that nothing good would come out of that. + ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] GSoC 2017

Michael Niedermayer wrote: >also in absence of any other ideas, YCoCg support may be a >qualification task. Maybe not the best choice but certainly >usefull on its own +1 Y'CoCg support would be useful indeed. Best regards, Reto ___ ffmpeg-devel

Re: [FFmpeg-devel] [PATCH]lavf/matroska: Support codec id V_FFV1 for FFV1.

Michael Niedermayer wrote: >> FFV1 didn't have any mapping in matroska before this, so >> what exactly is there to support? > >mkv supports all avi identifers, i assume that is what was >used before > >> Also, format support is technically a feature, so back- >> porting seems ill-advised. > >I

Re: [FFmpeg-devel] [PATCH] Remove the ffserver program and the ffm muxer/demuxer

I'm also very strongly for keeping ffserver. Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] Support limiting the number of pixels per image

wm4 wrote: >Surely not really a worry for ffmpeg, since it's concerned >about video, and 16K video is still "a bit" in the future. If by "video" you mean "YUV", then may I disagree with you? We use daily FFmpeg, and mainly in a "film" ("RGB") context and often with a 5K or 6.6K horizontal

Re: [FFmpeg-devel] [PATCH] ffserver: set format bitexact flag, eliminate warnings about it not being set

Michael Niedermayer wrote: >+ >+if (src->codec->flags & AV_CODEC_FLAG_BITEXACT) >+c->pfmt_ctx->flags |= AVFMT_FLAG_BITEXACT; Works fine here. Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] FFmpeg 2.8.9, 3.1.6, 3.0.5

Michael Niedermayer wrote: >moved 2.5 and 2.6 to olddownloads > >and 2.8.9 release made Thank you! ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] web/index: add news entry for release 3.3

James Almer wrote: >IMO, since the "we strongly recommend" line has been a constant >in all releases, removing it now will (for those that notice >it) rise quite a few red flags and make people come to the >conclusion they should probably skip it altogether. +1 And as for bug report/fixing

Re: [FFmpeg-devel] [PATCH] web/index: add news entry for release 3.3

Michael Niedermayer wrote: >> + April 13th, 2017, FFmpeg 3.3 "Hilbert" >> + >> +FFmpeg 3.3 "Hilbert", >>a new >> +major release, is now available! Some of the highlights: >> + > >> + >> + > >is this valid html ? No! Either a list: . . . or simply the text: . . . is

Re: [FFmpeg-devel] [RFC] FFmpeg 3.3

Steven Liu wrote: >> should we make a 3.3 release from >>0bab78f7e729a76ea7a8cbec7f1de033c52494e8 >> that is 3 weeks ago with backports ? >> >I think this point maybe better, and stable than another >two. +1 ___ ffmpeg-devel mailing list

Re: [FFmpeg-devel] Snapping ffmpeg

Alan Pope wrote: >Snaps are universal Linux packages. On number of Linux distributions you can use Linuxbrew: brew install ffmpeg --with-the-parameters-you-wish It works pretty well! We use it on Ubuntu and on Slackware. Most of the Homebrew packages are available also on Linuxbrew. Best

Re: [FFmpeg-devel] FFmpeg 3.4

Michael Niedermayer wrote: >Of course if the majority wants me to wait with the release, >its easy to wait for as long as people want me to wait ... Form an user's perspective, I would be delighted to have a new release. Thank you very much indeed! Reto

Re: [FFmpeg-devel] [PATCH 8/8] doc: update filter_design.txt.

Nicolas George wrote: >Signed-off-by: Nicolas George >--- > doc/filter_design.txt | 251 >+++--- > 1 file changed, 135 insertions(+), 116 deletions(-) > >diff --git a/doc/filter_design.txt b/doc/filter_design.txt >index

Re: [FFmpeg-devel] [PATCH 3/4] avformat/movenc: force colr atom for uncompressed yuv in mov

Dave Rice wrote: >As required by Apple’s TN2162. >--- > libavformat/movenc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) LGTM ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH 1/2] cmdutils: print missing caps in print_codec().

Jun Zhao wrote: >print full caps type in print_codec(). > >Signed-off-by: Jun Zhao >--- > fftools/cmdutils.c | 10 ++ > 1 file changed, 10 insertions(+) > >diff --git a/fftools/cmdutils.c b/fftools/cmdutils.c >index 8ffc9d2..4f2e0a2 100644 >--- a/fftools/cmdutils.c

Re: [FFmpeg-devel] [PATCH] FFV1: make RGB48 support as non-experimental

Michael Niedermayer wrote: >>Resulting bitstream was tested with a conformance checker >>using the last draft of FFV1 specifications. > >But has the way this is stored been optimized ? > >Once its marked as non exerimental all future decoders must >support the exact way. It can no longer then be

Re: [FFmpeg-devel] Public and private structs and fields (was: lavc: add new API for iterating codecs) and codec parsers

Nicolas George wrote: >Happy days-getting-longer to you all! Is FFmpeg not working in the Southern Hemisphere? Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] GSoC 2018

Thilo Borgmann wrote: >Should I? Yes, please! Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] avcodec/ffv1: Support for RGBA64 and GBRAP16

Michael Niedermayer wrote: >I would prefer if the algorithm would be tuned to 16bit data >before adding more formats to the encoder which require all >decoders to support them. > >Dont you agree that this would be the better strategy ? To my understanding FFV1 v3 is actually stable. Or am I

Re: [FFmpeg-devel] [Cellar] [PATCH] avcodec/ffv1: Support for RGBA64 and GBRAP16

Michael Niedermayer wrote: >To clarify my suggestion, >the algorithm should be tuned for high bit depth before using >it for long term storage. This would be v4 (or later). >Personally i would wait for v4 and not use v3 for high bit >depth. Which is why i think its not smart to extend the v3

Re: [FFmpeg-devel] FFmpeg 3.5 / 4.0

Reto Kromer wrote: >I suggest as well to move the 2.8 branch from the Releases to >the Old Releases. I just noticed that the day before yesterday 2.8.14 has been released, therefore please ignore my suggestion. Thank you! ___ ffmpeg-devel mailin

Re: [FFmpeg-devel] FFmpeg 3.5 / 4.0

Michael Niedermayer wrote: >Is 4.0 or 3.5 preferred ? I would prefer 4.0 for the reasons already mentioned by others. I suggest as well to move the 2.8 branch from the Releases to the Old Releases. >Any name suggestions ? >I do not agree with what you have to say, but I'll defend to >the

Re: [FFmpeg-devel] [PATCH] avfilter/vf_hue: 10bit support

Michael Niedermayer wrote: >Signed-off-by: Michael Niedermayer >--- > libavfilter/vf_hue.c | 103 +++ > +++- > 1 file changed, 92 insertions(+), 11 deletions(-) On my side it works fine, but don't have any official status in the project. Best regards, Reto

Re: [FFmpeg-devel] [PATCH 4/7] Adds gray floating-point pixel formats.

Sergey Lavrushkin wrote: >2018-08-03 16:07 GMT+03:00 Michael Niedermayer >: [...] >>division is slow. This should either be a multiplication with >>the inverse or a LUT with 8bit index changing to float. >> >>The faster of them should be used > >LUT seems to be faster. I am not surprised. In

Re: [FFmpeg-devel] [PATCH 4/7] Adds gray floating-point pixel formats.

Martin Vignali wrote: >But maybe to make tests simpler, we can use/add bit exact >conversion for uint8 to float, we can generate a LUT without >float calc and for uint16 to float, we can add a uint16 to >float conversion without float calc, or maybe, generate a LUT >in bit exact mode (probably

Re: [FFmpeg-devel] [PATCH 3/3] avcodec/utvideodec: use cached bitstream reader

Paul B Mahol wrote: >Byte Order: Little Endian I will check the mixed endian on my PDP-11 ;-) ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] Register for VDD 2018 conference

Paul B Mahol wrote: >So we already have 3 FFV2 variants. > >Which of them are actually useful? Useful for what? E.g. 1 is a great source of inspiration! (At least to me, since Dave Rice tweeted it on 2016-07-15.) Best regards, Reto ___ ffmpeg-devel

Re: [FFmpeg-devel] Register for VDD 2018 conference

Michael Niedermayer wrote: >I think future work should be done as FFV1v5 v6 v7 on >CELLAR/IETF That is how it should be, in my opinion. >why you ask ? >because that way >its on its way to be a proper IETF standard from day 1 >there are already people who are interrested in this there, >like

Re: [FFmpeg-devel] [PATCH v2][GSOC] avfilter: added colorconstancy

Hello Mina, I noticed a typo in the documentation: >@item difford >The order of diffrentation diffrentation -> differentiation Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] avcodec/proresenc_aw improvements

Martin Vignali wrote: >if avtc->profile < 0 or > 4, return an error. Should 5 not become ProRes XQ (ap4x) as in prores_ks? Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] avcodec/prores_aw : add support for alpha encoding

Martin Vignali wrote: >prores_ks take care about alpha data size, for yuv encoding (in >other word reduce quality of yuv data if there is alpha), but >it's seems that this is not the case of the official encoder No, it isn't. >So for prores_aw, i choose to separate yuv encoding and alpha

Re: [FFmpeg-devel] avcodec/proresdec : add 12b decoding support

Martin Vignali wrote: >Only enable 12b decoding if the codec tag is Prores or XQ >let 10b decoding for 422 codecs tag. Indeed! Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] avcodec/proresaw_enc : improvment (vendor and color properties, 4444Xq)

> On 26 Nov 2018, at 15:28, Martin Vignali wrote: > > (alpha 12b encoding is probably > easy to add) Are you sure alpha is 12 bit? As long as I remember, it is 16 bit. Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH]lavf/webvttenc: Always write hours in timestamps with two characters

Carl Eugen Hoyos wrote: >Attached patch fixes ticket #7442 for me. LGTM Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] avformat:matroskadec: use a define to mark the EBML length is unknown

Steve Lhomme wrote: > libavformat/matroskadec.c | 12 +++- > 1 file changed, 7 insertions(+), 5 deletions(-) > >diff --git a/libavformat/matroskadec.c b/libavformat/matroskadec.c >index 5aa8a105dc..0e3a6890c1 100644 Should be fine. Best regards, Reto

Re: [FFmpeg-devel] Bug in YUV decoder

Ben Hutchinson wrote: >What is top posting? I'll try to avoid it if I know what it is. Then please "google" it. Thanks! https://ffmpeg.org/contact.html#MailingLists https://en.wikipedia.org/wiki/Posting_style#Top-posting ___ ffmpeg-devel mailing list

Re: [FFmpeg-devel] Proposal: Homebrew tap for FFmpeg

Carl Eugen Hoyos wrote: >The question is what happens if one of the dependencies >in FFmpeg's formula does not work or disappears. Then the formula will be updated accordingly, as this has been done during all the last years. Best regards, Reto ___

Re: [FFmpeg-devel] Proposal: Homebrew tap for FFmpeg

Gerion Entrup wrote: >do the dependencies of the options need to be maintained in the >repo as well? I guess, this is out of the scope of FFmpeg. Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] Proposal: Homebrew tap for FFmpeg

Werner Robitza wrote: >I propose that FFmpeg maintains its own ffmpeg formula under >its GitHub organization I second the idea. (Homebrew works now on any modern x86_64 architecture running Linux, macOS and Windows with Linux.) >I am happy to maintain this formula – and maybe there are other

[FFmpeg-devel] [PATCH] Makefile: delete unneeded escape

Best regards, Reto 0001-Makefile-delete-unneeded-escape.patch Description: Binary data ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] Makefile: delete unneeded escape

Michael Niedermayer wrote: >if someone adds a line after this he would have to change the >previous line (adding the \ back) >that would make such a patch less tidy (2 lines changed instead >of 1) >i suspect that was the reason why all lines have a \ Possibly. The two other similar instances

[FFmpeg-devel] [PATCH] doc/filters: fix typos

Should fix a few nits in man. Best regards, Reto 0001-doc-filters-fix-typos.patch Description: Binary data ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] [PATCH] doc/muxers: fix typo

Best regards, Reto 0001-doc-muxers-fix-typo.patch Description: Binary data ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] [FFmpeg-cvslog] doc/muxers: fix typo

Carl Eugen Hoyos wrote: >> +Any hexadecimal value between @code{0x01} to @code{0xff} as defined in > >Shouldn't this be "between 0x01 and 0xff"? Yep, of course. I will fix this. Thank you! Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

[FFmpeg-devel] [PATCH] doc/muxers: fix typo

Best regards, Reto 0001-doc-muxers-fix-typo.patch Description: Binary data ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] doc/snow: fix typos

Best regards, Reto 0001-doc-snow-fix-typos.patch Description: Binary data ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

[FFmpeg-devel] [PATCH] doc/faq: update macOS and URLs

Best regards, Reto 0001-doc-faq-update-macOS-and-URLs.patch Description: Binary data ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Re: [FFmpeg-devel] Proposal: Homebrew tap for FFmpeg

Werner Robitza wrote: >On Wed, Feb 6, 2019 at 9:51 PM Carl Eugen Hoyos > wrote: >>We already provide a build script and we believe that it works >>very well, in addition a kind supporter offers osx binaries. > >That's all true, but not all users want to build manually (or >have the technical

Re: [FFmpeg-devel] [PATCH]download: Fix the release link

Michael Niedermayer wrote: >i think we should probably make a new major release ... +1 Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or

Re: [FFmpeg-devel] FFmpeg 4.2

>> FFMPEG 4.2 PANDORA? > > FFmpeg 4.2 CARLS CANS Ada (She deserves much better than that horrible programming language!) ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit

Re: [FFmpeg-devel] [PATCH 1/2] avfilter/vf_lut3d: increase MAX_LEVEL

Paul B Mahol wrote: >Found 65x65x65 3D LUT in wild FYI: 128x128x128 3D LUTs do also exist in film production. Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe,

Re: [FFmpeg-devel] ffmpeg version differences

Mehta, Krishnakant wrote: >Kindly let us know what are major differences in ffmpeg ver 4.2 >and 2.8.11 Please check the informations available on the homepage: https://ffmpeg.org/ You should post such questions on the FFmpeg user mailing list, not the developer's one. Hope this helps! Reto

Re: [FFmpeg-devel] [RFC] How to become release maintainer

James Almer wrote: >>> master nb_commits % 1500 == 0. >And if you make the cut as strict as you suggest, you'll surely >get broken releases. I fully agree that such an orthodoxy would result in broken releases. Seen this from a user of releases perspective, a good compromise between

Re: [FFmpeg-devel] FFmpeg 4.2.3

Michael Niedermayer wrote: >Its quite a while since 4.2.2 so i intend to make 4.2.3 soon >if you want something backported, backport it now Good news, thank you! Out of curiosity, are you also preparing the 4.3 major release? Best regards, Reto ___

Re: [FFmpeg-devel] FFmpeg 4.2.3

Michael Niedermayer wrote: >4.3 is on my todo list, i should have made that already but i >didnt. >realistically 4.3 might happen in 1-2 weeks, if nothing >interferes and nothing unexpected happens. Thank you, most appreciated! Reto ___ ffmpeg-devel

Re: [FFmpeg-devel] [PATCH] avcodec/cfhd: Check transform type

Paul B Mahol wrote: >On 8/28/20, Michael Niedermayer wrote: Is there some specification for this ? i was looking yesterday but google failed to point me to one >>> >>> No specifications, just SDK on github. >>> >>> Also I'm unsure if that is sufficient fix for the underline

Re: [FFmpeg-devel] [PATCH] cineform CFHD encoder addition and decoder improvements

Paul B Mahol wrote: >Added yuv422p10 support to encoder and some comments to tables. LGTM Thank you and best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit

Re: [FFmpeg-devel] [PATCH] avcodec/cfhd: add 3d transform support

Kieran Kunhya wrote: >On Thu, 6 Aug 2020 at 17:28, Paul B Mahol >wrote: > >> patches attached. >> > >Seems ok if tested on various samples. Tested with a few samples only, LGTM. Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] release/4.3

Michael Niedermayer wrote: >>Is there any chance that the naming system could be changed >>for this one release so it's 4:3 instead? > >thats a funny idea but we would be causing pain with that to >anyone trying to grep or sort releases You could have the release 4.3 named "4:3" rather than a

Re: [FFmpeg-devel] [PATCH]lavfi/hflip: Support Bayer pixel formats

Carl Eugen Hoyos wrote: >Am So., 26. Juli 2020 um 21:28 Uhr schrieb Paul B Mahol >: >> >> On 7/26/20, Carl Eugen Hoyos wrote: >> > Hi! >> > >> > Attached patch fixes a part of ticket #8819. >> > >> > Please comment, Carl Eugen >> > >> >> Looks good, but variable name is unfortunate. > >New patch

Re: [FFmpeg-devel] [PATCH 2/4] avdevice/decklink: add AV_OPT_FLAG_DEPRECATED flag for list_devices

Engi Gang wrote: >unsubscribe Please follow the instruction given at the end of each single message: >> To unsubscribe, visit link above, or email >> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". >To unsubscribe, visit link above, or email >ffmpeg-devel-requ...@ffmpeg.org with

Re: [FFmpeg-devel] [PATCH] avfilter: add colortemperature filter

Paul B Mahol wrote: >+@item temperature >+Set the temperature in Kelvins. Allowed range is from 1000 to 4. >+Default value is 6500 K. I would use the singular "Kelvin", otherwise LGTM. ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org

Re: [FFmpeg-devel] [PATCH v2] pixfmt: fixed wrong fix of comment

Valerii Zapodovnikov wrote: - * These values match the ones defined by ISO/IEC 23001-8_2013 § 7.1. + * These values match the ones defined by ISO/IEC 23001-8_2013 § 7.1 and ITU-T H.273. FYI: ISO/IEC 23001-8:2016 has been withdrawn. Its information can be found now in ISO/IEC 23091-1:2018,

Re: [FFmpeg-devel] [PATCH v3] pixfmt: fixed wrong fix of comment

Valerii Zapodovnikov wrote: >This mostly reverts 785bfb1d7bb8de567c3aac1d9cc369b55ac9fb7b. >But I also added some clarifications so that nobody mixes primaries >with matrix again. SMPTE 240 and 170 primaires are the same, while >matrix coeff. are different, because 240 is derived from 170's new

Re: [FFmpeg-devel] 4.4 Release Name

RADSL wrote: >On 4/2/2021 2:59 AM, Michael Niedermayer wrote: >> We still need to choose the name for 4.4 >> previous unused suggestions where: >> Von Neumann, Lorentz, Poincaré, Desitter, De Broglie, Gauss, >> Galois, Viterbi, Darwin Willem de Sitter? If so, then I would write it in two words.

Re: [FFmpeg-devel] 4.4 Release Name

Jan Ekström wrote: >K. R. Rao +1 Yep, I changes my mind (thank you Michael for the hint!) +1 Rao -1 Plandemic Best regards, Reto ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe,

Re: [FFmpeg-devel] FFmpeg 4.4

Michael Niedermayer wrote: >I will branch release/4.4 soon >then like always leave some time for testing, bugfixes, ... and then >make FFmeg 4.4 from release/4.4, its too long since 4.3 Good news! Thank you very much indeed! Reto ___ ffmpeg-devel

Re: [FFmpeg-devel] 5.0 release

Jean-Baptiste Kempf wrote: >On Mon, 13 Dec 2021, at 16:25, Michael Niedermayer wrote: >> previous unused suggestions where: >> Von Neumann, Lorentz, Poincaré, Desitter, De Broglie, Gauss, >> Galois, Viterbi, Darwin > >I'd love a "Lorentz" release :) +1 "Bayer", the inventor of a filter mosaic

Re: [FFmpeg-devel] FFmpeg 6.0

Gijs Peskens wrote: >> Here are some previously suggested names: >> Darwin, De broglie, Desitter, Galois, Gauss, Heaviside, >> Jacobi, Maxwell, Mellin, Perelman, Poincaré, Ramanujan, >> Sagan, Viterbi, Voltaire, Von Neumann > >Assuming with Desitter the Dutch mathematician