Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

On Tue, Dec 3, 2024 at 1:07 AM Kirithika Kalirathnam < kirith...@multicorewareinc.com> wrote: > Hi Vittorio, > > The commits in this PR > were > picked > and pushed to the master branch of x265.(b647da9 > < > https://bitbucket.org/mul

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

Hi Vittorio, The commits in this PR were picked and pushed to the master branch of x265.(b647da9 ,b153007

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

On Thu, Nov 28, 2024 at 3:22 AM Kirithika Kalirathnam < kirith...@multicorewareinc.com> wrote: > Hi All, > > x265 v4.1 is > released with the fixes addressing memory leak and other reported > issues.Please check it out. > > *Thanks,* > *

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

Hi All, x265 v4.1 is released with the fixes addressing memory leak and other reported issues.Please check it out. *Thanks,* *Kirithika* On Mon, Nov 11, 2024 at 9:50 AM Kirithika Kalirathnam < kirith...@multicorewareinc.com> wrote: >

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

Hi all, We would like to update that we have fixed the memory leaks and other issues reported in x265 and will be releasing v4.1 this week. *Thanks,* *Kirithika* On Fri, Oct 18, 2024 at 3:08 PM Kirithika Kalirathnam < kirith...@multicorewareinc.com> wrote: > Hi all , > > We understand your con

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

Hi all , We understand your concern behind marking x265 as experimental but we wanted to let you know that our x265 development team is actively working on resolving multiple issues that have been brought to our notice so far through bitbucket issue tracker(including issue #482) and are planning t

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

No, I strongly disagree. Marking a vital encoder as libx265 that thousands of people rely on as "experimental" after more than 10 years since its inclusion doesn't make any sense and would make more harm than good. Besides, the experimental flag is supposed to be used to indicate that the imple

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

> 在 2024年10月17日，下午10:01，James Almer 写道： > > On 10/17/2024 10:49 AM, Timo Rothenpieler wrote: >>> On 17/10/2024 11:22, Anton Khirnov wrote: >>> Quoting Anton Khirnov (2023-03-15 15:45:25) This encoder leaks and overreads, as can be seen e.g. by running an encode under valgrind with def

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

On 10/17/2024 10:49 AM, Timo Rothenpieler wrote: On 17/10/2024 11:22, Anton Khirnov wrote: Quoting Anton Khirnov (2023-03-15 15:45:25) This encoder leaks and overreads, as can be seen e.g. by running an encode under valgrind with default encoder parameters. This was known upstream since at leas

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

On 17/10/2024 11:22, Anton Khirnov wrote: Quoting Anton Khirnov (2023-03-15 15:45:25) This encoder leaks and overreads, as can be seen e.g. by running an encode under valgrind with default encoder parameters. This was known upstream since at least 2019 (e.g. bitbucket issue #482) but never fixed

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

Quoting Anton Khirnov (2023-03-15 15:45:25) > This encoder leaks and overreads, as can be seen e.g. by running an > encode under valgrind with default encoder parameters. This was known > upstream since at least 2019 (e.g. bitbucket issue #482) but never fixed > until now. > > Since upstream does

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

Tobias Rapp: > On 15/03/2023 15:45, Anton Khirnov wrote: > >> This encoder leaks and overreads, as can be seen e.g. by running an >> encode under valgrind with default encoder parameters. This was known >> upstream since at least 2019 (e.g. bitbucket issue #482) but never fixed >> until now. >> >>

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

Quoting Tobias Rapp (2023-03-15 16:00:04) > On 15/03/2023 15:45, Anton Khirnov wrote: > > > This encoder leaks and overreads, as can be seen e.g. by running an > > encode under valgrind with default encoder parameters. This was known > > upstream since at least 2019 (e.g. bitbucket issue #482) but

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

Quoting James Almer (2023-03-15 15:46:41) > On 3/15/2023 11:45 AM, Anton Khirnov wrote: > > This encoder leaks and overreads, as can be seen e.g. by running an > > encode under valgrind with default encoder parameters. This was known > > upstream since at least 2019 (e.g. bitbucket issue #482) but

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

On 15/03/2023 15:45, Anton Khirnov wrote: This encoder leaks and overreads, as can be seen e.g. by running an encode under valgrind with default encoder parameters. This was known upstream since at least 2019 (e.g. bitbucket issue #482) but never fixed until now. Since upstream does not seem to

Re: [FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

On 3/15/2023 11:45 AM, Anton Khirnov wrote: This encoder leaks and overreads, as can be seen e.g. by running an encode under valgrind with default encoder parameters. This was known upstream since at least 2019 (e.g. bitbucket issue #482) but never fixed until now. Since upstream does not seem t

[FFmpeg-devel] [PATCH] lavc/libx265: flag as experimental

This encoder leaks and overreads, as can be seen e.g. by running an encode under valgrind with default encoder parameters. This was known upstream since at least 2019 (e.g. bitbucket issue #482) but never fixed until now. Since upstream does not seem to practice basic code hygiene, make sure peopl