On Mon, 20 Feb 2023, at 00:50, Neal Gompa wrote:
> This is not a reasonable response, especially to someone who is
> volunteering their time to develop features for a project. If it
> misses 6.0, it sucks.
>
> My concern though is that major version bumps are supposed to be
> ABI/API breaks, if
On Sun, Feb 19, 2023 at 5:00 PM Kieran Kunhya wrote:
>
> On Sun, 19 Feb 2023 at 18:46, Lynne wrote:
>
> > Feb 19, 2023, 18:43 by kier...@obe.tv:
> >
> > > On Sun, 19 Feb 2023 at 17:36, Kieran Kunhya wrote:
> > >
> > >> Obviously, if we merge it now, and big enough issues are found
> > >>
> >
On Sun, 19 Feb 2023 at 18:46, Lynne wrote:
> Feb 19, 2023, 18:43 by kier...@obe.tv:
>
> > On Sun, 19 Feb 2023 at 17:36, Kieran Kunhya wrote:
> >
> >> Obviously, if we merge it now, and big enough issues are found
> >>
> >>> which we couldn't fix immediately, I'd have no problem reverting
> >>>
On Sat, 18 Feb 2023, Lynne wrote:
This ports the last user of the avfft/avdct/avrdft API.
LGTM, thanks.
Marton
Patch attached.
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To
On Sun, Feb 19, 2023 at 09:00:19PM +0100, Lynne wrote:
> Feb 19, 2023, 20:44 by mich...@niedermayer.cc:
>
> > On Sun, Feb 19, 2023 at 08:02:24PM +0100, Lynne wrote:
> >
> >> Feb 19, 2023, 19:51 by mich...@niedermayer.cc:
> >>
> >> > On Sun, Feb 19, 2023 at 05:53:45PM +0100, Lynne wrote:
> >> >
Feb 19, 2023, 20:44 by mich...@niedermayer.cc:
> On Sun, Feb 19, 2023 at 08:02:24PM +0100, Lynne wrote:
>
>> Feb 19, 2023, 19:51 by mich...@niedermayer.cc:
>>
>> > On Sun, Feb 19, 2023 at 05:53:45PM +0100, Lynne wrote:
>> > [...]
>> >
>> >> Otherwise, I'd like for 6.1 to be released no later than
On Sun, Feb 19, 2023 at 08:02:24PM +0100, Lynne wrote:
> Feb 19, 2023, 19:51 by mich...@niedermayer.cc:
>
> > On Sun, Feb 19, 2023 at 05:53:45PM +0100, Lynne wrote:
> > [...]
> >
> >> Otherwise, I'd like for 6.1 to be released no later than April.
> >>
> >
> > ok
> > release early, release often,
+1 on early 6.1 to get this in
On Sun, 19 Feb 2023 17:56:25 +0100 "Jean-Baptiste Kempf"
wrote:
> On Sun, 19 Feb 2023, at 17:53, Lynne wrote:
> > Otherwise, I'd like for 6.1 to be released no later than April.
>
> Sure, that would be the best solution, instead of rushing code right now.
>
>
Feb 19, 2023, 19:51 by mich...@niedermayer.cc:
> On Sun, Feb 19, 2023 at 05:53:45PM +0100, Lynne wrote:
> [...]
>
>> Otherwise, I'd like for 6.1 to be released no later than April.
>>
>
> ok
> release early, release often, that makes sense
> but rush things, delay things can be probelmatic. It
On Sun, Feb 19, 2023 at 05:53:45PM +0100, Lynne wrote:
[...]
> Otherwise, I'd like for 6.1 to be released no later than April.
ok
release early, release often, that makes sense
but rush things, delay things can be probelmatic. It doesnt have to be
but it can. id much rather do another release
Feb 18, 2023, 15:53 by d...@lynne.ee:
> Feb 18, 2023, 14:58 by jamr...@gmail.com:
>
>> On 2/18/2023 10:45 AM, Lynne wrote:
>>
>>> Feb 18, 2023, 14:32 by jamr...@gmail.com:
>>>
On 2/18/2023 9:49 AM, Lynne wrote:
> Feb 17, 2023, 19:45 by d...@lynne.ee:
>
>> Feb 17, 2023, 18:08
Feb 19, 2023, 18:43 by kier...@obe.tv:
> On Sun, 19 Feb 2023 at 17:36, Kieran Kunhya wrote:
>
>> Obviously, if we merge it now, and big enough issues are found
>>
>>> which we couldn't fix immediately, I'd have no problem reverting
>>> the Vulkan patches from the 6.0 branch.
>>>
>>
>>
>> A major
On Thu, 16 Feb 2023, Marton Balint wrote:
Signed-off-by: Marton Balint
---
doc/encoders.texi | 16
doc/filters.texi | 5 -
doc/muxers.texi | 6 --
3 files changed, 27 deletions(-)
Will apply.
Regards,
Marton
diff --git a/doc/encoders.texi b/doc/encoders.texi
On Sun, 19 Feb 2023 at 17:36, Kieran Kunhya wrote:
> Obviously, if we merge it now, and big enough issues are found
>> which we couldn't fix immediately, I'd have no problem reverting
>> the Vulkan patches from the 6.0 branch.
>
>
> A major LTS release is not your development sandbox.
>
> Kieran
>
> Obviously, if we merge it now, and big enough issues are found
> which we couldn't fix immediately, I'd have no problem reverting
> the Vulkan patches from the 6.0 branch.
A major LTS release is not your development sandbox.
Kieran
___
On Sun, 19 Feb 2023, at 17:58, Lynne wrote:
> Feb 19, 2023, 17:57 by j...@videolan.org:
>
>> On Sun, 19 Feb 2023, at 17:53, Lynne wrote:
>>
>>> Otherwise, I'd like for 6.1 to be released no later than April.
>>>
>>
>> Sure, that would be the best solution, instead of rushing code right now.
>>
>>
Feb 19, 2023, 17:57 by j...@videolan.org:
> On Sun, 19 Feb 2023, at 17:53, Lynne wrote:
>
>> Otherwise, I'd like for 6.1 to be released no later than April.
>>
>
> Sure, that would be the best solution, instead of rushing code right now.
>
> And prepare proper testing for this, with numerous
Feb 19, 2023, 17:54 by d...@lynne.ee:
> Feb 19, 2023, 16:40 by mich...@niedermayer.cc:
>
>> Hi
>>
>>
>> On Sun, Feb 19, 2023 at 01:08:02AM +0100, Lynne wrote:
>>
>>>
>>> Feb 18, 2023, 20:03 by mich...@niedermayer.cc:
>>>
>>> > On Fri, Feb 17, 2023 at 04:43:50AM +0100, Lynne wrote:
>>> >
>>> >>
On Sun, 19 Feb 2023, at 17:53, Lynne wrote:
> Otherwise, I'd like for 6.1 to be released no later than April.
Sure, that would be the best solution, instead of rushing code right now.
And prepare proper testing for this, with numerous different workstations and
laptops.
Best,
--
Feb 19, 2023, 16:40 by mich...@niedermayer.cc:
> Hi
>
>
> On Sun, Feb 19, 2023 at 01:08:02AM +0100, Lynne wrote:
>
>>
>> Feb 18, 2023, 20:03 by mich...@niedermayer.cc:
>>
>> > On Fri, Feb 17, 2023 at 04:43:50AM +0100, Lynne wrote:
>> >
>> >> This small patchset mostly rewrites Vulkan to enable
On Sun, 19 Feb 2023 at 15:40, Michael Niedermayer
wrote:
> ok that works, that said
> is there consensus that i should create the release branch "now"?
> It seems no review is going on in public of these patches and we should do
> the release "soon", i am asking as i dont want to just surprise
Hi
On Sun, Feb 19, 2023 at 01:08:02AM +0100, Lynne wrote:
>
> Feb 18, 2023, 20:03 by mich...@niedermayer.cc:
>
> > On Fri, Feb 17, 2023 at 04:43:50AM +0100, Lynne wrote:
> >
> >> This small patchset mostly rewrites Vulkan to enable using multiplane
> >> images,
> >> and implements video
Any further comments?
On 2023-02-14 06:21 pm, Gyan Doshi wrote:
On 2023-02-14 03:35 pm, Anton Khirnov wrote:
Quoting Gyan Doshi (2023-02-11 12:02:51)
The FLV format can store metadata as numbers which are used and handled
by many streaming platforms.
Now, metadata values can be sent as AMF
23 matches
Mail list logo
