On Mon, 3 Jun 2024 at 23:41, James Almer wrote:
>
> On 6/3/2024 6:32 PM, Michael Niedermayer wrote:
> > On Sun, Jun 02, 2024 at 03:49:42PM +0200, Sebastian Ramacher wrote:
> >> On 2024-03-03 09:55:15 +0100, Sebastian Ramacher wrote:
> >>> On 2024-03-02 20:39:08 -0500, Sean McGovern wrote:
> O
On 2024-06-04 09:31:38 +0300, Rémi Denis-Courmont wrote:
>
>
> Le 4 juin 2024 00:41:03 GMT+03:00, James Almer a écrit :
> >Well, no. Breakages are expected when you remove API. The real question is
> >why so many projects wait until the old API is gone to migrate. What we
> >removed in 7.0 has
On 2024-06-03 23:32:37 +0200, Michael Niedermayer wrote:
> On Sun, Jun 02, 2024 at 03:49:42PM +0200, Sebastian Ramacher wrote:
> > On 2024-03-03 09:55:15 +0100, Sebastian Ramacher wrote:
> > > On 2024-03-02 20:39:08 -0500, Sean McGovern wrote:
> > > > On Sat, Mar 2, 2024, 18:19 Michael Niedermayer
On Mon, Jun 03, 2024 at 11:32:37PM +0200, Michael Niedermayer wrote:
> On Sun, Jun 02, 2024 at 03:49:42PM +0200, Sebastian Ramacher wrote:
[...]
> > Just as a FYI: ffmpeg 7.0 breaks close to 70 reverse dependencies in
> > Debian. The list is available at [1]. So if you want ffmpeg X to be in
> > De
Quoting Michael Niedermayer (2024-06-04 03:16:11)
> > The real question is
> > why so many projects wait until the old API is gone to migrate. What we
> > removed in 7.0 has had its replacement in place for a couple years, since
> > 5.1.
>
> Because few need or want to migrate to a new API every y
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
___
Le 4 juin 2024 00:41:03 GMT+03:00, James Almer a écrit :
>Well, no. Breakages are expected when you remove API. The real question is why
>so many projects wait until the old API is gone to migrate. What we removed in
>7.0 has had its replacement in place for a couple years, since 5.1.
Because
On Mon, Jun 03, 2024 at 06:41:03PM -0300, James Almer wrote:
> On 6/3/2024 6:32 PM, Michael Niedermayer wrote:
> > On Sun, Jun 02, 2024 at 03:49:42PM +0200, Sebastian Ramacher wrote:
> > > On 2024-03-03 09:55:15 +0100, Sebastian Ramacher wrote:
> > > > On 2024-03-02 20:39:08 -0500, Sean McGovern wr
On 6/3/2024 6:32 PM, Michael Niedermayer wrote:
On Sun, Jun 02, 2024 at 03:49:42PM +0200, Sebastian Ramacher wrote:
On 2024-03-03 09:55:15 +0100, Sebastian Ramacher wrote:
On 2024-03-02 20:39:08 -0500, Sean McGovern wrote:
On Sat, Mar 2, 2024, 18:19 Michael Niedermayer
wrote:
On Sun, Mar 03
On Mon, Jun 3, 2024, 17:32 Michael Niedermayer
wrote:
> On Sun, Jun 02, 2024 at 03:49:42PM +0200, Sebastian Ramacher wrote:
> > On 2024-03-03 09:55:15 +0100, Sebastian Ramacher wrote:
> > > On 2024-03-02 20:39:08 -0500, Sean McGovern wrote:
> > > > On Sat, Mar 2, 2024, 18:19 Michael Niedermayer <
On Sun, Jun 02, 2024 at 03:49:42PM +0200, Sebastian Ramacher wrote:
> On 2024-03-03 09:55:15 +0100, Sebastian Ramacher wrote:
> > On 2024-03-02 20:39:08 -0500, Sean McGovern wrote:
> > > On Sat, Mar 2, 2024, 18:19 Michael Niedermayer
> > > wrote:
> > >
> > > > On Sun, Mar 03, 2024 at 12:06:14AM +
On 2024-03-03 09:55:15 +0100, Sebastian Ramacher wrote:
> On 2024-03-02 20:39:08 -0500, Sean McGovern wrote:
> > On Sat, Mar 2, 2024, 18:19 Michael Niedermayer
> > wrote:
> >
> > > On Sun, Mar 03, 2024 at 12:06:14AM +0100, Sebastian Ramacher wrote:
> > > > On 2024-03-02 23:55:38 +0100, Michael Ni
On Fri, Mar 08, 2024 at 11:00:50AM -0300, James Almer wrote:
> On 3/3/2024 4:35 AM, Jean-Baptiste Kempf wrote:
> >
> > n Sat, 2 Mar 2024, at 23:55, Michael Niedermayer wrote:
> > > On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
> > > > Hi all
> > > >
> > > > As it was a litt
Hi Mark,
Do you think the broken vaapi dec-filter-encode (and other hw acceleration
method using fixed-size pool) is a blocking issue ? See more info below:
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20231220071050.3175819-11-haihao.xi...@intel.com/
https://patchwork.ffmpeg.org/project/ff
It is by no means a blocker but I think it would be nice for users to be
able view subtitle colors with the dvdvideo demuxer, after all it is part
of the presentation. There is a patch for this that has gone through
several reviews. I have (hopefully) addressed the last round of feedback,
but I wil
On Fri, Mar 8, 2024 at 11:41 PM Kieran Kunhya wrote:
> On Fri, 8 Mar 2024 at 15:04, Frank Plowman wrote:
>
> > On 08/03/2024 14:04, James Almer wrote:
> > > On 3/8/2024 11:02 AM, Kieran Kunhya wrote:
> > >> On Fri, 8 Mar 2024 at 14:00, James Almer wrote:
> > >>
> > >>> On 3/3/2024 4:35 AM, Jean
On Fri, 8 Mar 2024 at 15:04, Frank Plowman wrote:
> On 08/03/2024 14:04, James Almer wrote:
> > On 3/8/2024 11:02 AM, Kieran Kunhya wrote:
> >> On Fri, 8 Mar 2024 at 14:00, James Almer wrote:
> >>
> >>> On 3/3/2024 4:35 AM, Jean-Baptiste Kempf wrote:
>
> n Sat, 2 Mar 2024, at 23:55, Mi
On 08/03/2024 14:04, James Almer wrote:
> On 3/8/2024 11:02 AM, Kieran Kunhya wrote:
>> On Fri, 8 Mar 2024 at 14:00, James Almer wrote:
>>
>>> On 3/3/2024 4:35 AM, Jean-Baptiste Kempf wrote:
n Sat, 2 Mar 2024, at 23:55, Michael Niedermayer wrote:
> On Tue, Jan 23, 2024 at 08:22:41PM
On 3/8/2024 11:02 AM, Kieran Kunhya wrote:
On Fri, 8 Mar 2024 at 14:00, James Almer wrote:
On 3/3/2024 4:35 AM, Jean-Baptiste Kempf wrote:
n Sat, 2 Mar 2024, at 23:55, Michael Niedermayer wrote:
On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
Hi all
As it was a little
On Fri, 8 Mar 2024 at 14:00, James Almer wrote:
> On 3/3/2024 4:35 AM, Jean-Baptiste Kempf wrote:
> >
> > n Sat, 2 Mar 2024, at 23:55, Michael Niedermayer wrote:
> >> On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
> >>> Hi all
> >>>
> >>> As it was a little difficult for me
On 3/3/2024 4:35 AM, Jean-Baptiste Kempf wrote:
n Sat, 2 Mar 2024, at 23:55, Michael Niedermayer wrote:
On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
Hi all
As it was a little difficult for me to not loose track of what is
blocking a release. I suggest that for all rele
On 3/3/2024 4:35 AM, Jean-Baptiste Kempf wrote:
n Sat, 2 Mar 2024, at 23:55, Michael Niedermayer wrote:
On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
Hi all
As it was a little difficult for me to not loose track of what is
blocking a release. I suggest that for all rele
On 2024-03-02 20:39:08 -0500, Sean McGovern wrote:
> On Sat, Mar 2, 2024, 18:19 Michael Niedermayer
> wrote:
>
> > On Sun, Mar 03, 2024 at 12:06:14AM +0100, Sebastian Ramacher wrote:
> > > On 2024-03-02 23:55:38 +0100, Michael Niedermayer wrote:
> > > > On Tue, Jan 23, 2024 at 08:22:41PM +0100, M
n Sat, 2 Mar 2024, at 23:55, Michael Niedermayer wrote:
> On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
>> Hi all
>>
>> As it was a little difficult for me to not loose track of what is
>> blocking a release. I suggest that for all release blocking issues
>> open a ticket
On Sat, Mar 2, 2024, 18:19 Michael Niedermayer
wrote:
> On Sun, Mar 03, 2024 at 12:06:14AM +0100, Sebastian Ramacher wrote:
> > On 2024-03-02 23:55:38 +0100, Michael Niedermayer wrote:
> > > On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
> > > > Hi all
> > > >
> > > > As it
On Sun, Mar 03, 2024 at 12:06:14AM +0100, Sebastian Ramacher wrote:
> On 2024-03-02 23:55:38 +0100, Michael Niedermayer wrote:
> > On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
> > > Hi all
> > >
> > > As it was a little difficult for me to not loose track of what is
> > > b
On 2024-03-02 23:55:38 +0100, Michael Niedermayer wrote:
> On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
> > Hi all
> >
> > As it was a little difficult for me to not loose track of what is
> > blocking a release. I suggest that for all release blocking issues
> > open a tic
On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
> Hi all
>
> As it was a little difficult for me to not loose track of what is
> blocking a release. I suggest that for all release blocking issues
> open a ticket and set Blocking to 7.0
> that way this:
> https://trac.ffmpeg.or
On Sun, Feb 25, 2024 at 08:20:13PM -0300, James Almer wrote:
> On 2/25/2024 8:18 PM, Michael Niedermayer wrote:
> > Hi all
> >
> > about a month has passed
> > wanted to remind that we seem to have 2 blocking issues on trac
> >
> > #10826 Short trim inside filter_complex leads to empty outpu
On 2/25/2024 8:18 PM, Michael Niedermayer wrote:
Hi all
about a month has passed
wanted to remind that we seem to have 2 blocking issues on trac
#10826 Short trim inside filter_complex leads to empty output
new defect criticalffmpeg unspe
Hi all
about a month has passed
wanted to remind that we seem to have 2 blocking issues on trac
#10826 Short trim inside filter_complex leads to empty output
new defect criticalffmpeg unspecified
#10857 Stream-level side data propagated to
On 2/9/2024 3:32 AM, Michael Niedermayer wrote:
> please make sure its marked on the bug tracker so it shows up here:
>
> https://trac.ffmpeg.org/query?status=new&status=open&status=reopened&blocking=~7.0
>
> thx
Done: https://trac.ffmpeg.org/ticket/10857
- Derek
___
On Sun, Feb 11, 2024 at 9:35 AM Michael Niedermayer
wrote:
> On Sat, Feb 10, 2024 at 06:03:57PM -0300, James Almer wrote:
> > On 1/23/2024 4:22 PM, Michael Niedermayer wrote:
> > > Hi all
> > >
> > > As it was a little difficult for me to not loose track of what is
> > > blocking a release. I sug
On Sat, Feb 10, 2024 at 06:03:57PM -0300, James Almer wrote:
> On 1/23/2024 4:22 PM, Michael Niedermayer wrote:
> > Hi all
> >
> > As it was a little difficult for me to not loose track of what is
> > blocking a release. I suggest that for all release blocking issues
> > open a ticket and set Bloc
On 1/23/2024 4:22 PM, Michael Niedermayer wrote:
Hi all
As it was a little difficult for me to not loose track of what is
blocking a release. I suggest that for all release blocking issues
open a ticket and set Blocking to 7.0
that way this:
https://trac.ffmpeg.org/query?blocking=~7.0
or for th
On Wed, Feb 07, 2024 at 02:54:23PM +, Derek Buitenhuis wrote:
> Hi,
>
> On 1/23/2024 7:22 PM, Michael Niedermayer wrote:
> > What is blocking? (IMHO)
> > * regressions (unless its non possible to fix before release)
> > * crashes
> > * security issues
> > * data loss
> > * privacy issues
> > *
On 2/7/2024 10:27 PM, Leo Izen wrote:
On 2/7/24 13:56, Andreas Rheinhardt wrote:
Leo Izen:
On 1/23/24 14:22, Michael Niedermayer wrote:
Hi all
As it was a little difficult for me to not loose track of what is
blocking a release. I suggest that for all release blocking issues
open a ticket a
On 2/7/24 13:56, Andreas Rheinhardt wrote:
Leo Izen:
On 1/23/24 14:22, Michael Niedermayer wrote:
Hi all
As it was a little difficult for me to not loose track of what is
blocking a release. I suggest that for all release blocking issues
open a ticket and set Blocking to 7.0
that way this:
h
Leo Izen:
> On 1/23/24 14:22, Michael Niedermayer wrote:
>> Hi all
>>
>> As it was a little difficult for me to not loose track of what is
>> blocking a release. I suggest that for all release blocking issues
>> open a ticket and set Blocking to 7.0
>> that way this:
>> https://trac.ffmpeg.org/quer
> On Jan 23, 2024, at 11:22 AM, Michael Niedermayer
> wrote:
>
> What is blocking? (IMHO)
> * regressions (unless its non possible to fix before release)
> * crashes
> * security issues
> * data loss
> * privacy issues
> * anything the commuity agrees should be in the release
Can we get the a
On 1/23/24 14:22, Michael Niedermayer wrote:
Hi all
As it was a little difficult for me to not loose track of what is
blocking a release. I suggest that for all release blocking issues
open a ticket and set Blocking to 7.0
that way this:
https://trac.ffmpeg.org/query?blocking=~7.0
or for the on
Hi,
On 1/23/2024 7:22 PM, Michael Niedermayer wrote:
> What is blocking? (IMHO)
> * regressions (unless its non possible to fix before release)
> * crashes
> * security issues
> * data loss
> * privacy issues
> * anything the commuity agrees should be in the release
We discussed it at FOSDEM, but
Quoting Niklas Haas (2024-01-24 13:45:33)
> On Tue, 23 Jan 2024 20:22:41 +0100 Michael Niedermayer
> wrote:
> > Hi all
> >
> > As it was a little difficult for me to not loose track of what is
> > blocking a release. I suggest that for all release blocking issues
> > open a ticket and set Blocki
>
> What is blocking? (IMHO)
> * regressions (unless its non possible to fix before release)
> * crashes
> * security issues
>
Is VVC being run through oss-fuzz yet? I think it would be a shame for 7.0
to be released then a ton of CVEs come out and the security community
hysterically saying FFmpeg
Jan 24, 2024, 14:24 by an...@khirnov.net:
> Quoting Lynne (2024-01-24 14:14:00)
>
>> Jan 24, 2024, 13:30 by an...@khirnov.net:
>> >> I have started on everything, and two things are finished but need polish,
>> >> one is difficult and needs debugging while the other is more difficult.
>> >>
>> >>
Quoting Lynne (2024-01-24 14:14:00)
> Jan 24, 2024, 13:30 by an...@khirnov.net:
> >> I have started on everything, and two things are finished but need polish,
> >> one is difficult and needs debugging while the other is more difficult.
> >>
> >> And with that release rate attitude, how do you thin
Jan 24, 2024, 13:30 by an...@khirnov.net:
> Quoting Lynne (2024-01-24 13:07:51)
>
>> Which part of "don't consider as blockers" did you find difficult to
>> understand?
>> I even added newlines top and bottom for you to laser onto that sentence.
>>
>
> Then why are you mentioning them in a thread
On Tue, 23 Jan 2024 20:22:41 +0100 Michael Niedermayer
wrote:
> Hi all
>
> As it was a little difficult for me to not loose track of what is
> blocking a release. I suggest that for all release blocking issues
> open a ticket and set Blocking to 7.0
> that way this:
> https://trac.ffmpeg.org/que
Quoting Lynne (2024-01-24 13:07:51)
> Which part of "don't consider as blockers" did you find difficult to
> understand?
> I even added newlines top and bottom for you to laser onto that sentence.
Then why are you mentioning them in a thread specifically about release
blockers.
> I have started
On 1/24/2024 4:45 AM, Anton Khirnov wrote:
Quoting Michael Niedermayer (2024-01-23 20:22:41)
Hi all
As it was a little difficult for me to not loose track of what is
blocking a release. I suggest that for all release blocking issues
open a ticket and set Blocking to 7.0
that way this:
https://t
On 1/24/2024 4:40 AM, Anton Khirnov wrote:
Quoting Lynne (2024-01-23 21:18:29)
Jan 23, 2024, 20:22 by mich...@niedermayer.cc:
Hi all
As it was a little difficult for me to not loose track of what is
blocking a release. I suggest that for all release blocking issues
open a ticket and set Block
Jan 24, 2024, 08:40 by an...@khirnov.net:
> Quoting Lynne (2024-01-23 21:18:29)
>
>> Jan 23, 2024, 20:22 by mich...@niedermayer.cc:
>>
>> > Hi all
>> >
>> > As it was a little difficult for me to not loose track of what is
>> > blocking a release. I suggest that for all release blocking issues
>>
Quoting Michael Niedermayer (2024-01-23 20:22:41)
> Hi all
>
> As it was a little difficult for me to not loose track of what is
> blocking a release. I suggest that for all release blocking issues
> open a ticket and set Blocking to 7.0
> that way this:
> https://trac.ffmpeg.org/query?blocking=~7
Quoting Lynne (2024-01-23 21:18:29)
> Jan 23, 2024, 20:22 by mich...@niedermayer.cc:
>
> > Hi all
> >
> > As it was a little difficult for me to not loose track of what is
> > blocking a release. I suggest that for all release blocking issues
> > open a ticket and set Blocking to 7.0
> > that way
Jan 23, 2024, 20:22 by mich...@niedermayer.cc:
> Hi all
>
> As it was a little difficult for me to not loose track of what is
> blocking a release. I suggest that for all release blocking issues
> open a ticket and set Blocking to 7.0
> that way this:
> https://trac.ffmpeg.org/query?blocking=~7.0
Hi all
As it was a little difficult for me to not loose track of what is
blocking a release. I suggest that for all release blocking issues
open a ticket and set Blocking to 7.0
that way this:
https://trac.ffmpeg.org/query?blocking=~7.0
or for the ones not closed:
https://trac.ffmpeg.org/query?st
56 matches
Mail list logo
