Le lauantaina 23. syyskuuta 2023, 9.49.47 EEST Neal Gompa a écrit :
> On Fri, Sep 22, 2023 at 12:33 PM Michael Niedermayer
>
> wrote:
> > > What does this mean? Does this mean an FFmpeg release containing code
> > > that
> > > interfaces with your SDR library? Or does it mean the library fully
>
Le torstaina 21. syyskuuta 2023, 21.56.52 EEST Michael Niedermayer a écrit :
> Hi
>
> On Thu, Sep 21, 2023 at 05:33:54PM +0100, Kieran Kunhya via ffmpeg-devel
wrote:
> > On Thu, Sep 21, 2023 at 5:21 PM Michael Niedermayer
> >
> > wrote:
> > > OTOH If a majority of people are against the SDR cod
Paul B Mahol (12023-09-21):
> If this SDR troll code ever get committed in FFmpeg libraries I will
> immediately leave project.
That would be sad for the project. But I am sorry, I sincerely believe
that if you were to follow through with it, it would be a price worth
paying to have Michael workin
On Sun, 24 Sept 2023, 18:34 Paul B Mahol, wrote:
> On 9/24/23, Nicolas George wrote:
> > Paul B Mahol (12023-09-24):
> >> libavdevice is abusing libavformat.
> >>
> >> It should have own API or be removed.
> >
> > libavdevice works.
>
> Define 'works'.
>
> It is clearly sub-optimal.
>
Why shoul
On 9/24/23, Nicolas George wrote:
> Paul B Mahol (12023-09-24):
>> libavdevice is abusing libavformat.
>>
>> It should have own API or be removed.
>
> libavdevice works.
Define 'works'.
It is clearly sub-optimal.
___
ffmpeg-devel mailing list
ffmpeg-de
Paul B Mahol (12023-09-24):
> libavdevice is abusing libavformat.
>
> It should have own API or be removed.
libavdevice works.
--
Nicolas George
signature.asc
Description: PGP signature
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https:/
On Sun, Sep 24, 2023 at 11:12 AM Nicolas George wrote:
> Neal Gompa (12023-09-23):
> > If it's just taking SDR devices as inputs and allowing you to encode
> > audio and video streams, I'm not sure why you *wouldn't* have this as
> > something in libavdevice or extended from it as a separate libr
Neal Gompa (12023-09-23):
> If it's just taking SDR devices as inputs and allowing you to encode
> audio and video streams, I'm not sure why you *wouldn't* have this as
> something in libavdevice or extended from it as a separate library.
The people who oppose Michael's SDR also have been trying t
On Sat, Sep 23, 2023 at 6:55 AM Michael Niedermayer
wrote:
>
> On Sat, Sep 23, 2023 at 02:49:47AM -0400, Neal Gompa wrote:
> > On Fri, Sep 22, 2023 at 12:33 PM Michael Niedermayer
> > wrote:
> > >
> > > On Fri, Sep 22, 2023 at 03:55:57PM +0200, Gijs Peskens wrote:
> > > >
> > > > On 21-09-2023 18
On Sat, Sep 23, 2023 at 02:49:47AM -0400, Neal Gompa wrote:
> On Fri, Sep 22, 2023 at 12:33 PM Michael Niedermayer
> wrote:
> >
> > On Fri, Sep 22, 2023 at 03:55:57PM +0200, Gijs Peskens wrote:
> > >
> > > On 21-09-2023 18:21, Michael Niedermayer wrote:
> > > > Hi all
> > > >
> > > > As the 6.1 re
On Fri, Sep 22, 2023 at 12:33 PM Michael Niedermayer
wrote:
>
> On Fri, Sep 22, 2023 at 03:55:57PM +0200, Gijs Peskens wrote:
> >
> > On 21-09-2023 18:21, Michael Niedermayer wrote:
> > > Hi all
> > >
> > > As the 6.1 release is upcoming and as it was previously stated by me that
> > > sdr
> > >
On Fri, Sep 22, 2023 at 03:55:57PM +0200, Gijs Peskens wrote:
>
> On 21-09-2023 18:21, Michael Niedermayer wrote:
> > Hi all
> >
> > As the 6.1 release is upcoming and as it was previously stated by me that
> > sdr
> > will be part of 6.1. Heres some update of what i intend to do about that.
> >
On 21-09-2023 18:21, Michael Niedermayer wrote:
Hi all
As the 6.1 release is upcoming and as it was previously stated by me that sdr
will be part of 6.1. Heres some update of what i intend to do about that.
People previously agreed to including a SDR input device in libavdevice with
SDR in a
On Thu, Sep 21, 2023 at 9:37 PM Nicolas George wrote:
> Vittorio Giovara (12023-09-21):
> > So this is an example of accusatory tone - discrediting the previous
> author
> > in order to make your arguments have more weight. It's a bad move and
> > easily spottable, you should argue with better el
Vittorio Giovara (12023-09-21):
> So this is an example of accusatory tone - discrediting the previous author
> in order to make your arguments have more weight. It's a bad move and
> easily spottable, you should argue with better elements at your disposal,
> not by claiming that I don't package so
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 time will you spend maintaining SDR?
On Thu, Sep 21, 2023 at 9: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 time will you spend maintaining SDR?
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 time will you spend maintaining SDR? Zero.
What does it change for you and everybody who thinks like you? N
Hi
On Thu, Sep 21, 2023 at 05:33:54PM +0100, Kieran Kunhya via ffmpeg-devel wrote:
> On Thu, Sep 21, 2023 at 5:21 PM Michael Niedermayer
> wrote:
> > OTOH If a majority of people are against the SDR code at the time of
> > branching 6.1. Then i will make a separate release identical to 6.1 with
>
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 for
> installing it in the process. That i
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 for
installing it in the process. That is a completely stupid idea.
> Will you stop with this accusatory t
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 a separate library and we're
arguing
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.
> No thanks, feature creep is a bad mojo.
“Creep” is your opinion, the opinion of somebody who we never see on
users mailing lists by the way.
>
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
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 users have been enthusiastically waiting for?
> I have been worki
On Thu, Sep 21, 2023 at 6:21 PM Michael Niedermayer
wrote:
> Hi all
>
> As the 6.1 release is upcoming and as it was previously stated by me that
> sdr
> will be part of 6.1. Heres some update of what i intend to do about that.
>
Very bold claim.
>
> People previously agreed to including a SDR
On Thu, Sep 21, 2023 at 5:21 PM Michael Niedermayer
wrote:
> OTOH If a majority of people are against the SDR code at the time of
> branching 6.1. Then i will make a separate release identical to 6.1 with
> the SDR code and of course also provide security support
How on earth is it acceptable tha
Hi all
As the 6.1 release is upcoming and as it was previously stated by me that sdr
will be part of 6.1. Heres some update of what i intend to do about that.
People previously agreed to including a SDR input device in libavdevice with
SDR in a seperate library.
If the community and the SDR code
On Wed, Sep 20, 2023 at 11:47:36PM +0100, Kieran Kunhya wrote:
> >
> > also iam not sure "experimental" is the right flag for code that has
> > possible security issues. People might turn experimental on not realizing
> > the security aspect.
> >
>
> We should make this clear in the docs then.
AT
> -Original Message-
> From: ffmpeg-devel On Behalf Of
> Michael Niedermayer
> Sent: wtorek, 19 września 2023 21:16
> To: FFmpeg development discussions and patches
> Subject: Re: [FFmpeg-devel] FFmpeg release 6.1
>
> On Tue, Sep 19, 2023 at 07:18:03PM
Hello,
On Thu, 21 Sep 2023, at 00:47, Kieran Kunhya wrote:
>>
>> also iam not sure "experimental" is the right flag for code that has
>> possible security issues. People might turn experimental on not realizing
>> the security aspect.
>>
>
> We should make this clear in the docs then.
+1
--
Jea
>
> also iam not sure "experimental" is the right flag for code that has
> possible security issues. People might turn experimental on not realizing
> the security aspect.
>
We should make this clear in the docs then.
Kieran
___
ffmpeg-devel mailing lis
On Wed, Sep 20, 2023 at 06:43:18PM +0100, Kieran Kunhya wrote:
> >
> > I dont suggest merging more EVC code before the release. I meant the
> > EVC code already in git, is reading alot of things with no checks.
> > It maybe doesnt matter in most cases, as its not used in most cases without
> > more
On Wed, Sep 20, 2023 at 02:47:19PM +0200, Niklas Haas wrote:
> On Tue, 19 Sep 2023 21:16:08 +0200 Michael Niedermayer
> wrote:
> > what about merging libplacebo into FFmpeg for example ?
> > As far as iam concerned you can have absolute final power about anything
> > in that libplacebo inside FFm
>
> I dont suggest merging more EVC code before the release. I meant the
> EVC code already in git, is reading alot of things with no checks.
> It maybe doesnt matter in most cases, as its not used in most cases without
> more EVC code but still
> Also ATM other things are blocking so EVC still cou
On Tue, Sep 19, 2023 at 11:58:41PM +0200, Lynne wrote:
> Sep 19, 2023, 21:16 by mich...@niedermayer.cc:
>
> > On Tue, Sep 19, 2023 at 07:18:03PM +0200, Niklas Haas wrote:
> >
> >> On Tue, 11 Apr 2023 00:14:28 +0200 Michael Niedermayer
> >> wrote:
> >> > Hi all
> >> >
> >> > There was the reques
On Tue, 19 Sep 2023 21:16:08 +0200 Michael Niedermayer
wrote:
> what about merging libplacebo into FFmpeg for example ?
> As far as iam concerned you can have absolute final power about anything
> in that libplacebo inside FFmpeg.
To respond quickly to this point,
I'm not sure what merging libp
On Di, 2023-09-19 at 20:38 -0400, Neal Gompa wrote:
> On Tue, Sep 19, 2023 at 5:58 PM Lynne wrote:
> >
> > Sep 19, 2023, 21:16 by mich...@niedermayer.cc:
> >
> > > On Tue, Sep 19, 2023 at 07:18:03PM +0200, Niklas Haas wrote:
> > >
> > > > On Tue, 11 Apr 2023 00:14:28 +0200 Michael Niedermayer
>
On Tue, Sep 19, 2023 at 5:58 PM Lynne wrote:
>
> Sep 19, 2023, 21:16 by mich...@niedermayer.cc:
>
> > On Tue, Sep 19, 2023 at 07:18:03PM +0200, Niklas Haas wrote:
> >
> >> On Tue, 11 Apr 2023 00:14:28 +0200 Michael Niedermayer
> >> wrote:
> >> > Hi all
> >> >
> >> > There was the request to make
Sep 19, 2023, 21:16 by mich...@niedermayer.cc:
> On Tue, Sep 19, 2023 at 07:18:03PM +0200, Niklas Haas wrote:
>
>> On Tue, 11 Apr 2023 00:14:28 +0200 Michael Niedermayer
>> wrote:
>> > Hi all
>> >
>> > There was the request to make a 6.1 before end of April
>> > Is that still so ?
>> >
>> > As
On Tue, Sep 19, 2023 at 07:18:03PM +0200, Niklas Haas wrote:
> On Tue, 11 Apr 2023 00:14:28 +0200 Michael Niedermayer
> wrote:
> > Hi all
> >
> > There was the request to make a 6.1 before end of April
> > Is that still so ?
> >
> > Assuming it is, its time to make that branch and release soon
On Tue, 11 Apr 2023 00:14:28 +0200 Michael Niedermayer
wrote:
> Hi all
>
> There was the request to make a 6.1 before end of April
> Is that still so ?
>
> Assuming it is, its time to make that branch and release soon
Hi,
It is now september. What happened to this release? FFmpeg 6.1 is
curre
42 matches
Mail list logo
