On 4 Mar 2025, at 20:44, Soft Works wrote:
>> -Original Message-
>> From: ffmpeg-devel On Behalf Of
>> Gianluca Cannata
>> Sent: Dienstag, 4. März 2025 09:40
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: [FFmpeg-devel] GSoC 2025 - OggKate subtitles support
>>
>> Good morning,
>>
>> I have
On 28 Feb 2025, at 0:14, Michael Niedermayer wrote:
> Hi
>
> On Thu, Feb 27, 2025 at 11:46:54PM +0100, epira...@gmail.com wrote:
>> On 27 Feb 2025, at 2:10, Michael Niedermayer wrote:
>>
>>> Signed-off-by: Michael Niedermayer
>>> ---
>>> doc/developer.texi | 11 +--
>>> 1 file changed
On 27 Feb 2025, at 2:10, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> doc/developer.texi | 11 +--
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/doc/developer.texi b/doc/developer.texi
> index a1bfe180c9b..6a753f99da6 100644
> --- a/doc/dev
On 19 Feb 2025, at 3:47, Zhao Zhili wrote:
>> On Feb 19, 2025, at 03:28, James Almer wrote:
>>
>> Signed-off-by: James Almer
>> ---
>> libavcodec/sbcenc.c | 50 +
>> 1 file changed, 41 insertions(+), 9 deletions(-)
>>
>> diff --git a/libavcodec/sbcenc
On 18 Feb 2025, at 13:46, Niklas Haas wrote:
> From: Niklas Haas
>
> Debugging option to dump the filter graph after insertion of auto-filters.
> Named such to avoid clashing with the existing -dumpgraph option on lavfi
> devices.
> ---
> doc/ffmpeg.texi | 18 ++
>
On 7 Feb 2025, at 7:27, softworkz wrote:
> From: softworkz
>
> This commit adds two logging flags: 'timing' and 'datetiming'.
>
> Usage:
>
> ffmpeg -loglevel +timing
>
> or
>
> ffmpeg -loglevel +datetiming
This commit message seems out of date regarding the actual commit contents
given the fl
On 28 Jan 2025, at 18:43, James Almer wrote:
> Fixes stack-buffer-overflow errors running under asan.
>
> Signed-off-by: James Almer
> ---
> tests/checkasm/sw_rgb.c | 18 +-
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/tests/checkasm/sw_rgb.c b/tests/checkas
On 28 Jan 2025, at 18:49, James Almer wrote:
> Fixes coverity #1641638.
>
> Signed-off-by: James Almer
> ---
> libavutil/downmix_info.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/libavutil/downmix_info.c b/libavutil/downmix_info.c
> index feaee28493..7e6c3e854d
On 24 Jan 2025, at 22:40, Martin Storsjö wrote:
> Traditionally, macOS has shipped an old version of rsync that lacked
> support for this version, hence this check (added in
> a8b3f0c5cf548f654e30c981988bb71981a3f8d3).
>
> However, in macOS 15.x, they have switched to providing rsync as a
> differ
On 23 Jan 2025, at 21:35, Alexander Strasser via ffmpeg-devel wrote:
> Since av_match_list was added in commit 0d92b0d5f445d4f2 , this
> function changed its semantics shortly after, especially with
> commit 3c0b98dced394da3 .
>
> Signed-off-by: Alexander Strasser
> ---
>
> Diff to v1:
> * use
On 22 Jan 2025, at 22:59, Alexander Strasser via ffmpeg-devel wrote:
> Since av_match_list was added in commit 0d92b0d5f445d4f2 , this
> function changed its semantics shortly after, especially with
> commit 3c0b98dced394da3 .
>
> Signed-off-by: Alexander Strasser
> ---
> libavutil/avstring.h
On 22 Jan 2025, at 20:32, Dmitrii Ovchinnikov wrote:
> Adds hwcontext_amf, enabling a shared AMF context for encoders,
> decoders, and AMF-based filters, without copy to the host memory.
> Code also was tested in HandBrake.
>
> Benefits:
> - Optimizations for direct video memory access from CP
On 30 Nov 2024, at 1:35, Bryan Kirk via ffmpeg-devel wrote:
> *subject*
>
> https://ffmpeg.org/pipermail/ffmpeg-devel/2024-May/328600.html
Hi,
a later iteration of this is merged, with the movflags flag name
of hybrid_fragmented, you can find it in the docs here:
https://ffmpeg.org/ffmpeg-for
On 27 Nov 2024, at 14:35, Marvin Scholz wrote:
> Move the ff_dovi_configure to happen before ff_encode_add_cpb_side_data
> as the former reallocates the sidedata so the pointer returned from
> ff_encode_add_cpb_side_data would be invalid.
> ---
> libavcodec/libaomenc.c | 8
> 1 file ch
On 22 Nov 2024, at 13:38, Derek Buitenhuis wrote:
> I do not accept this warning, and I do not agree with your reasoning.
>
> The entire point of that thread was paid work, and cost matters. I worded
> in an entirelty legitimate way.
>
> The fact that all the BS that has happened on this list si
On 21 Nov 2024, at 22:11, Peter Ross wrote:
> Fixes CID 1634888
> ---
> libavformat/mm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/libavformat/mm.c b/libavformat/mm.c
> index 74e2716926..07ba6ac4f5 100644
> --- a/libavformat/mm.c
> +++ b/libavformat/mm.c
> @@ -190,6 +190,7 @@ st
On 21 Nov 2024, at 6:24, Marth64 wrote:
> Hi ePirat:
>
> I believe it is safe. ism_free() is invoked as the .deinit procedure
> which will free all of the contexts allocated in ism_write_header().
> To confirm this I triggered a fault with this condition and saw no
> leaks in valgrind. Also if
On 12 Oct 2024, at 19:18, Marth64 wrote:
> Written in the dominant style of the surrounding code block.
>
> Signed-off-by: Marth64
> ---
> libavformat/smoothstreamingenc.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/libavformat/smoothstreamingenc.c
> b/libavfor
On 12 Nov 2024, at 10:09, Diederick C. Niehorster wrote:
> On Tue, Nov 12, 2024 at 9:44 AM martin schitter wrote:
>>
>>
>>
>> On 12.11.24 08:51, Martin Storsjö wrote:
>>> On Tue, 12 Nov 2024, martin schitter wrote:
>>>
The git history of Patches here on this mailinglist are usually
re
On 12 Nov 2024, at 9:44, martin schitter wrote:
> On 12.11.24 08:51, Martin Storsjö wrote:
>> On Tue, 12 Nov 2024, martin schitter wrote:
>>
>>> The git history of Patches here on this mailinglist are usually rewritten
>>> whenever one of the reviewers requests some change, but the typical
>>>
On 17 Oct 2024, at 21:58, Soma Lucz wrote:
> I’d like to reject the v1 version of this patch on Patchwork. What to do if
> the Patchwork registration confirmation email didn’t arrive for more than 2
> days, so I cannot log in? (Password reset emails also don’t arrive.) I
> checked the spam an
On 15 Oct 2024, at 10:30, Anton Khirnov wrote:
> Quoting Alexander Strasser via ffmpeg-devel (2024-10-15 07:34:26)
>> On 2024-10-14 22:35 +0200, Anton Khirnov wrote:
>>> Quoting Alexander Strasser via ffmpeg-devel (2024-10-14 22:21:38)
> It is documented in the header.
I figured as
On 13 Oct 2024, at 13:24, Anton Khirnov wrote:
> This function would otherwise fail to build on the next major bump, as
> inject_global_side_data is marked for removal.
>
> It should also never be needed, as there is now a mechanism for
> supplying global side data to decoders directly.
> ---
>
On 12 Oct 2024, at 23:08, Alexander Strasser via ffmpeg-devel wrote:
> The string representation of the FourCC is only used once for logging.
> ---
>
> Could also merge this with the first patch in this series and make
> it a single patch.
>
> Or drop this one.
>
> I don't have a strong opinion
On 10 Oct 2024, at 17:14, Steven Liu wrote:
> Because there have global varible in libxml2, it cleans up memory allocated by
> the library itself. It is a cleanup function for the XML library.
> It tries to reclaim all related global memory allocated for the library
> processing.
> It doesn't d
On 9 Oct 2024, at 22:15, Alexander Strasser via ffmpeg-devel wrote:
> On 2024-10-03 04:04 +0200, Lynne via ffmpeg-devel wrote:
>> On 01/10/2024 15:24, vipyne wrote:
>>> ---
>>> configure | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/configure b/configure
>>> i
On 4 Oct 2024, at 11:31, Lynne via ffmpeg-devel wrote:
> This is the same as with libavfilter.
>
> We will need SPIR-V compilation for at least three different things,
> like the VC-2 encoder and decoder, AV1 film grain synthesis for
> hardware with no support for it, and possibly other codecs.
>
On 3 Oct 2024, at 21:31, Anton Khirnov wrote:
> Ideally there should be three parts to the filter context - public,
> private to the filter, and private to generic code, but only the first
> and the last of these exist currently. Until the second is implemented,
> this is better than nothing.
>
On 1 Oct 2024, at 9:51, Lynne via ffmpeg-devel wrote:
> On 01/10/2024 08:55, Nuo Mi wrote:
>> We still need several refactors to improve the current VVC decoder's
>> performance,
>> which will frequently break the API/ABI. To mitigate this, we've copied the
>> executor from
>> avutil to avcod
On 28 Sep 2024, at 0:27, James Almer wrote:
> On 9/25/2024 10:29 AM, Anton Khirnov wrote:
>> This function creates AND initializes a filter, so setting any filter
>> options after it is wrong. It happens to work when the filter's init
>> function does not touch the options in question, but is f
On 14 Sep 2024, at 0:12, martin schitter wrote:
> These a very helpful instructive examples.
>
> Nevertheless, I would highly prefer a preconfigured `make fmt` command, which
> works similar to `cargo fmt` or `deno fmt` and corrects and checks formating
> issues without any human intervention.
On 12 Jul 2024, at 20:38, Marvin Scholz wrote:
> ---
> ffbuild/common.mak | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
If no one has objections in the meantime, I will merge it next week.
> diff --git a/ffbuild/common.mak b/ffbuild/common.mak
> index 87a3ffd2b0..023adb8567 100644
>
On 18 May 2024, at 20:22, Andrew Sayers wrote:
> I would have found this very helpful!
Thanks for the review, I just submitted a new version that hopefully
addresses most of your points.
>
> On Sat, May 18, 2024 at 07:00:50PM +0200, Marvin Scholz wrote:
>> Given the frequency that new develop
On 13 Sep 2024, at 19:43, Martin Storsjö wrote:
> On Thu, 12 Sep 2024, Marvin Scholz wrote:
>
>> Previously only the C compiler was set, which would lead to
>> confusing situations where even though clang-asan was selected,
>> it would still use g++ for C++ code, failing because configure
>> doe
On 12 Sep 2024, at 8:03, Martin Storsjö wrote:
> On Wed, 11 Sep 2024, Marvin Scholz wrote:
>
>> The symbol prefix check would incorrectly detect a bogus prefix in
>> circumstances where sanitizers
>> instrument the build, like when configuring with the clang-asan toolchain
>> where it would de
On 9 Sep 2024, at 12:10, Anton Khirnov wrote:
> Quoting Marvin Scholz (2024-09-08 19:43:27)
>> ---
>> fftools/opt_common.c | 12 ++--
>> 1 file changed, 6 insertions(+), 6 deletions(-)
>>
>> diff --git a/fftools/opt_common.c b/fftools/opt_common.c
>> index 9d2d5184a0..059f7a53d2 100644
On 9 Sep 2024, at 3:30, Andreas Rheinhardt wrote:
> Marvin Scholz:
>> The strerror function must not be used here, as the error is a AVERROR
>> errno, which depending on the platform no longer corresponds to the
>> actual errno that can be handled by strerror.
>> ---
>> fftools/opt_common.c | 2
On 31 Aug 2024, at 23:17, James Almer wrote:
> On 8/31/2024 5:45 PM, Marvin Scholz wrote:
>> The ret value here is not yet intialized so the return would return
>> uninitialized data. What was probably meant to be checked here was the
>> return value of ffio_read_size, which can return an error
On 21 Aug 2024, at 3:09, Gnattu OC via ffmpeg-devel wrote:
>> On Aug 21, 2024, at 07:17, epira...@gmail.com wrote:
>>
>>
>>
>> On 21 Aug 2024, at 0:43, Erik Bråthen Solem wrote:
>>
>>> avfoundation.m uses constants prefixed with AVMediaType on Mac OS X > 10.6.
>>> In 10.7 through 10.12 their typ
On 21 Aug 2024, at 0:43, Erik Bråthen Solem wrote:
> avfoundation.m uses constants prefixed with AVMediaType on Mac OS X > 10.6.
> In 10.7 through 10.12 their type was NSString*, but starting with 10.13 a
> new AVMediaType struct type was introduced. In avfoundation.m, the function
> getDevicesW
On 19 Aug 2024, at 16:23, Araz Iusubov wrote:
> From: Evgeny Pavlov
>
> This commit increase precision of Sleep() function on Windows.
> This fix reduces the sleep time on Windows to improve AMF encoding
> performance on low resolution input videos.
>
> Fix for issue #10622
>
> We evaluated Creat
On 17 Aug 2024, at 1:11, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> doc/APIchanges | 4
> libavcodec/avcodec.h | 4
> 2 files changed, 8 insertions(+)
>
> diff --git a/doc/APIchanges b/doc/APIchanges
> index 173f317ea1b..53d164959c0 100644
> --- a/d
On 13 Aug 2024, at 17:51, Rémi Denis-Courmont wrote:
> Le 13 août 2024 17:03:33 GMT+03:00, "J. Dekker" a écrit :
>> From: Niklas Haas
>>
>> Instead of duplicating these common macros in every file, add them to
>> the shared utility file. Also add a base case for sanity.
>
> Is `#error` a standar
On 10 Aug 2024, at 8:13, gnattu via ffmpeg-devel wrote:
> Hardware frames with RGB colorspace will not have a YCbCrMatrixKey.
> Currently, it will spam the console with warning if rgb frame is
> uploaded.
Thanks, LGTM
>
> Signed-off-by: Gnattu OC
> ---
> libavutil/hwcontext_videotoolbox.c | 2
On 2 Aug 2024, at 0:25, gnattu via ffmpeg-devel wrote:
> From: Gnattu OC
>
> Allocate a dedicated attachments dictionary instead of trying to get
> one from the pixel buffer. The attachments got from the pixel buffer
> confuses the CVImageBufferCreateColorSpaceFromAttachments method and
> will
On 23 Jul 2024, at 9:26, Prem Thogiti wrote:
> Hi Team,
>
Hi,
I believe this is the wrong list for such a question.
This is the development list, you want to ask on ffmpeg-user instead.
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> I have a folder with 100+ mp4 files (each 1min duration) a
On 23 Jul 2024, at 9:36, Anton Khirnov wrote:
> HEVCContext.output_frame will be removed in following commits.
>
> Reported-By: Max Bykov
> ---
> Untested, testing welcome.
Tested with fate-hevc-conformance-CONFWIN_A_Sony_1 and works.
LGTM
>
> Cf. '[PATCH 37/39] lavc/hevcdec: use a Container
On 22 Jul 2024, at 0:47, gnattu via ffmpeg-devel wrote:
> The __builtin_available function does not do compile time check
> for the availablity of the CVBufferCopyAttachments function
> which will fail the build. Check the availability during configure.
>
> Signed-off-by: Gnattu OC
> ---
> con
On 18 Jul 2024, at 16:21, Ramiro Polla wrote:
> On Thu, Jul 18, 2024 at 3:41 PM Stefan Oltmanns via ffmpeg-devel
> wrote:
>> Am 18.07.24 um 15:04 schrieb Ramiro Polla:
>> [...]
>>
>> +static VSScriptLibrary vs_script_library;
>
> Does vs_script_library have to be a global?
On 14 Jul 2024, at 21:55, Michael Niedermayer wrote:
> On Sat, Jul 13, 2024 at 11:12:40PM +0200, Kacper Michajlow wrote:
>> On Thu, 27 Jun 2024 at 02:50, Kacper Michajlow wrote:
>>>
>>> On Thu, 27 Jun 2024 at 00:45, Michael Niedermayer
>>> wrote:
On Wed, Jun 26, 2024 at 09:07:42PM +0
On 13 Jul 2024, at 2:50, Andreas Rheinhardt wrote:
> Marvin Scholz:
>> ---
>> libavfilter/vf_yadif_videotoolbox.m | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/libavfilter/vf_yadif_videotoolbox.m
>> b/libavfilter/vf_yadif_videotoolbox.m
>> index c47d3edfb8..eb7026395e 100644
>> -
On 13 Jul 2024, at 2:47, Andreas Rheinhardt wrote:
> Marvin Scholz:
>> ---
>> libavutil/avassert.h | 12
>> 1 file changed, 12 insertions(+)
>>
>> diff --git a/libavutil/avassert.h b/libavutil/avassert.h
>> index 1895fb7551..cdab912fe4 100644
>> --- a/libavutil/avassert.h
>> +++ b/li
On 10 Jul 2024, at 19:26, James Almer wrote:
> On 7/9/2024 5:43 AM, epira...@gmail.com wrote:
>>
>>
>> On 8 Jul 2024, at 8:30, Zhao Zhili wrote:
>>
>>> From: Zhao Zhili
>>>
>>> ---
>>> libavutil/hwcontext_videotoolbox.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff
On 9 Jul 2024, at 21:44, Helmut K. C. Tessarek wrote:
> Thanks for the reply.
>
> On 2024-07-09 02:16, Gnattu OC via ffmpeg-devel wrote:
>> Well the code introduced is to fix certain HDR related bugs and it does not
>> "works perfectly” before, it was just broken.
>
> I was rather talking about b
On 6 Jul 2024, at 11:26, Stefano Sabatini wrote:
> On date Tuesday 2024-07-02 20:38:00 +0200, Marvin Scholz wrote:
>> An incorrect calculation in ff_perlin_init causes a write to the
>> stack array at index 256, which is out of bounds.
>>
>> Fixes: CID1608711
>> ---
>> libavfilter/perlin.c | 2
On 8 Jul 2024, at 8:30, Zhao Zhili wrote:
> From: Zhao Zhili
>
> ---
> libavutil/hwcontext_videotoolbox.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavutil/hwcontext_videotoolbox.c
> b/libavutil/hwcontext_videotoolbox.c
> index 953155ce32..dd89edfa08 100644
>
On 9 Jul 2024, at 8:16, Gnattu OC via ffmpeg-devel wrote:
>> On Jul 9, 2024, at 13:47, Helmut K. C. Tessarek wrote:
>>
>> I'm very sorry to bother the dev list with this, but this is the 2nd time in
>> less than a year that the min version of macOS was changed in videotoolbox.
>>
>> 2023-09-22
On 12 Jun 2024, at 1:45, Sean McGovern wrote:
> Hi,
>
> Can someone help me reset my password on Patchwork? I've used the 'Forgot
> password ' link several times and never received an email.
IIRC patchwork can not send emails, I had the same issue a while ago but
Andriy should be able to manua
On 12 Jun 2024, at 19:46, Michael Niedermayer wrote:
> The 2 links are the clearest i found.
>
> Signed-off-by: Michael Niedermayer
> ---
> doc/faq.texi | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/faq.texi b/doc/faq.texi
> index 477cc60533a..d07ed533dd7 100644
> --- a/do
On 23 May 2024, at 18:05, Zhao Zhili wrote:
>> On May 21, 2024, at 09:56, Gnattu OC via ffmpeg-devel
>> wrote:
>>
>>>
>>> On May 20, 2024, at 09:12, Marvin Scholz wrote:
>>>
>>> Fix #10884
>>> ---
>>> libavutil/hwcontext_videotoolbox.c | 54 +-
>>> 1 file changed,
On 17 May 2024, at 17:44, Andreas Rheinhardt wrote:
> epira...@gmail.com:
>>
>>
>> On 17 May 2024, at 17:25, Andreas Rheinhardt wrote:
>>
>>> Signed-off-by: Andreas Rheinhardt
>>> ---
>>> libavcodec/libaomenc.c | 4 ++--
>>> libavcodec/libkvazaar.c | 4 ++--
>>> libavcodec/libsvtav1.c | 6 ++
On 17 May 2024, at 17:25, Andreas Rheinhardt wrote:
> This is in preparation for using av_dict_iterate().
>
> Signed-off-by: Andreas Rheinhardt
> ---
> libavformat/tee.c | 7 ---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/libavformat/tee.c b/libavformat/tee.c
> index
On 17 May 2024, at 17:25, Andreas Rheinhardt wrote:
> Signed-off-by: Andreas Rheinhardt
> ---
> libavcodec/libaomenc.c | 4 ++--
> libavcodec/libkvazaar.c | 4 ++--
> libavcodec/libsvtav1.c | 6 +++---
> libavcodec/libx264.c| 4 ++--
> libavcodec/libx265.c| 4 ++--
> libavformat/tee
On 17 May 2024, at 17:25, Andreas Rheinhardt wrote:
> Signed-off-by: Andreas Rheinhardt
> ---
> fftools/ffmpeg.c | 4 ++--
> fftools/ffplay.c | 4 ++--
> fftools/ffprobe.c | 2 +-
> libavfilter/avfilter.c | 4 ++--
> libavformat/aacdec.c | 2 +-
> libavformat/http.c | 8 ++
On 4 May 2024, at 23:25, Andrew Sayers wrote:
> On Sat, May 04, 2024 at 09:28:03PM +0200, Michael Niedermayer wrote:
>> Hi
>>
>> On Fri, May 03, 2024 at 03:45:20PM +, Cosmin Stejerean via ffmpeg-devel
>> wrote:
>> [...]
>>> What doesn't exist (yet) is a way to keep people on the exact email
On 2 May 2024, at 21:32, Ondřej Fiala wrote:
> On Thu May 2, 2024 at 4:38 PM CEST, Rémi Denis-Courmont wrote:
>> Le torstaina 2. toukokuuta 2024, 17.25.06 EEST Ondřej Fiala a écrit :
>>> On Wed May 1, 2024 at 7:27 AM CEST, Rémi Denis-Courmont wrote:
I don't use Gmail, and using email for re
On 26 Apr 2024, at 14:27, Niklas Haas wrote:
> From: Niklas Haas
>
> Many filters modify certain aspects of frame data, e.g. through resizing
> (vf_*scale* family), color volume mapping (vf_lut*, vf_tonemap*), or
> possibly others.
>
> When this happens, we should strip all frame side data that w
On 19 Apr 2024, at 16:50, Niklas Haas wrote:
> On Thu, 18 Apr 2024 22:53:51 +0200 Michael Niedermayer
> wrote:
>> A plugin system moves this patch-management to people who actually
>> care, that is the authors of the codecs and (de)muxers.
>
> A plugin system will only solve this insomuch as p
On 18 Apr 2024, at 22:40, Andreas Rheinhardt wrote:
> Andreas Rheinhardt:
>> The API is similar to the ThreadFrame API, with the exception
>> that it no longer has an included AVFrame and that it has its
>> own mutexes and condition variables which makes it more independent
>> of pthread_frame.c
On 18 Apr 2024, at 22:15, Michael Niedermayer wrote:
> On Thu, Apr 18, 2024 at 10:19:50AM +0200, Stefano Sabatini wrote:
>> On date Wednesday 2024-04-17 19:21:39 -0700, Aidan wrote:
>>> The best option is to figure stuff out.
>> [...]
>>> I use FFmpeg to download HLS streams from the internet or
On 18 Apr 2024, at 10:46, Stefano Sabatini wrote:
> On date Wednesday 2024-04-17 15:58:32 +0200, Michael Niedermayer wrote:
>> Hi all
>>
>> The pace of inovation in FFmpeg has been slowing down.
>> Most work is concentarted nowadays on code refactoring, and adding
>> support for new codecs and
On 18 Apr 2024, at 9:52, Stefano Sabatini wrote:
> On date Wednesday 2024-04-17 17:24:02 +0100, Andrew Sayers wrote:
>> On 17/04/2024 14:58, Michael Niedermayer wrote:
> [...]
>> I've occasionally tried getting into ffmpeg for over a decade now, and have
>> lurked here for the past few months as
On 11 Apr 2024, at 5:59, Vittorio Giovara wrote:
> On Wed, Apr 10, 2024 at 9:19 PM Michael Niedermayer
> wrote:
>
>> […]
>>
>> To bring some of the new blood into the project the project needs to
>> first understand why they dont. And asking thouse who manage with
>> difficulty
>> to join could
On 17 Apr 2024, at 13:45, Martin Storsjö wrote:
> Travis is no longer relevant for attempting to run CI jobs in our
> setup.
LGTM
> ---
> .travis.yml | 30 --
> 1 file changed, 30 deletions(-)
> delete mode 100644 .travis.yml
>
> diff --git a/.travis.yml b/.travis.y
On 11 Apr 2024, at 15:59, B-2014 Ariyan Kashyap wrote:
> I was trying to compile the ffmpeg in my local using MSYS2 terminal and i
> am getting this error
>
> gcc is unable to create an executable file.
> If gcc is a cross-compiler, use the --enable-cross-compile option.
> Only do this if you kn
My choice would be Dijkstra as well.
On 2 Apr 2024, at 7:45, AV Preservation by reto.ch (lists) wrote:
> Sean McGovern wrote:
>
>> Not sure if I am allowed to pick, my choice is Dijkstra.
>
> When I started programming in 1975, Edsger W. Dijkstra was one of my heroes,
> which is why I support yo
On 28 Mar 2024, at 17:46, Ondřej Fiala wrote:
> Just want to make sure, since I am aware of some cases of large commercial
> email
> providers blocking my email provider... did anyone with a gmail address
> receive
> this patch?
>
Yes
> Thanks,
> Ondřej
>
> On Tue Mar 26, 2024 at 3:18 AM CET
On 14 Mar 2024, at 10:22, Ignjatović, Lazar wrote:
> avformat: enable UDP IPv6 multicast interface selection
>
> localaddr option now properly works with IPv6 addresses. Properly resolved
> interface index in places where default 0 interface index is used (marked with
> TODO: within udp.c). Adde
On 11 Mar 2024, at 15:26, Andreas Rheinhardt wrote:
> Andreas Rheinhardt:
>> Allan Cady via ffmpeg-devel:
>>> From: "Allan Cady"
>>>
>>> I propose changing the format to "%.6f", which will
>>> give microsecond precision for all timestamps, regardless of
>>> offset. Trailing zeros can be trimmed
On 10 Mar 2024, at 4:00, Michael Niedermayer wrote:
> On Sun, Mar 10, 2024 at 02:36:48AM +0100, epira...@gmail.com wrote:
>> On 10 Mar 2024, at 2:25, Michael Niedermayer wrote:
>>
>>> Hi everyone
>>>
>>> Some members of the CC want to indefinitely ban Balling
>>> from trac. And as our doc/commun
On 10 Mar 2024, at 2:25, Michael Niedermayer wrote:
> Hi everyone
>
> Some members of the CC want to indefinitely ban Balling
> from trac. And as our doc/community.texi says:
> "Indefinite bans from the community must be confirmed by the General
> Assembly, in a majority vote."
>
> Thus some CC m
On 5 Mar 2024, at 16:53, Andreas Rheinhardt wrote:
> Signed-off-by: Andreas Rheinhardt
> ---
> libavutil/dict.c | 10 --
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/libavutil/dict.c b/libavutil/dict.c
> index 7f23d5336a..6fb09399ba 100644
> --- a/libavutil/dict.c
>
On 21 Feb 2024, at 15:38, Niklas Haas wrote:
> On Tue, 20 Feb 2024 20:43:30 +0200 Jan Ekström wrote:
>> Do note that the idea was that this would only be for management of
>> the main archive, so it would not affect clients/runners rsync'ing
>> from the main archive.
>>
>> Of course clients whi
On 17 Feb 2024, at 13:31, Rémi Denis-Courmont wrote:
> Le lauantaina 17. helmikuuta 2024, 13.46.27 EET Gyan Doshi a écrit :
>> As a TC member who is part of the disagreement, I believe your
>> participation is recused.
>
> Obviously not. We don't want to get into a situation whence TC members ha
On 14 Feb 2024, at 13:03, Andreas Rheinhardt wrote:
> Signed-off-by: Andreas Rheinhardt
> ---
> libavfilter/vf_signature.c | 9 ++---
> 1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/libavfilter/vf_signature.c b/libavfilter/vf_signature.c
> index 4896e8f2c1..eb48bf773d 1006
On 8 Feb 2024, at 13:32, Nicolas George wrote:
> Leo Izen (12024-02-07):
>> I don't think this is really a fair statement to make. We have lots of
>> potential reviewers subscribed to this list but very few people actually
>> review code, and those that do review code are expected to provide som
On 31 Jan 2024, at 20:47, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer
> ---
> libavutil/rational.h | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/libavutil/rational.h b/libavutil/rational.h
> index 8cbfc8e0669..c6ac9fb1d91 100644
> --- a/libavutil/rational.h
>
On 31 Jan 2024, at 13:03, Timo Rothenpieler wrote:
> On 31/01/2024 05:31, Roger Pack wrote:
>> On Thu, Jan 18, 2024 at 6:31 AM Timo Rothenpieler
>> wrote:
>>>
>>>
>>>
>>> On 18/01/2024 04:38, Roger Pack wrote:
Hello.
After compiling libx265 as a "static library" (mingw cross compilin
Typo in commit message: liavcodec should be libavcodec
On 22 Jan 2024, at 20:14, Victor Luchits wrote:
> The bitrate option (-b:v) can now be used to specify the bit rate
> of the video stream of the RoQ encoder.
>
> Original patch by Joseph Fenton aka Chilly Willy
>
> Signed-off-by: Victor Luchi
On 1 Jan 2024, at 15:38, David Bohman wrote:
> This is a build failure in the master branch as a result of commit
> e37b15e26fbc7bc31a86a4a2c7c798e20d4f4c2c:
>
> There is no type AVMediaType prior to macOS 10.13.
> ---
> libavdevice/avfoundation.m | 4
> 1 file changed, 4 insertions(+)
>
On 4 Dec 2023, at 13:47, xufuji456 via ffmpeg-devel wrote:
> Building with iOS platform, the compiler has a warning:
> "'devicesWithMediaType:' is deprecated: first deprecated in iOS 10.0 - Use
> AVCaptureDeviceDiscoverySession instead"
>
> Signed-off-by: xufuji456 <839789...@qq.com>
Thanks
On 2 Dec 2023, at 0:26, Michael Niedermayer wrote:
> Fixes: switch_1080p_720p.mp4
> Found-by: Dale Curtis
> Signed-off-by: Michael Niedermayer
> ---
> libavformat/mov.c | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/libavformat/mov.c b/libavformat/mov.c
> inde
On 14 Nov 2023, at 20:32, Ronald S. Bultje wrote:
> On Tue, Nov 14, 2023 at 2:28 PM Nicolas George wrote:
>
>> but nobody here knows
>>
>
> Unsubstantiated FUD.
>
> Move on.
+1
There is no good in even more discussions right now.
If really many people think public ballots are a great idea, t
On 9 Nov 2023, at 9:20, Lynne wrote:
> Nov 7, 2023, 08:36 by d...@lynne.ee:
>
>> Oct 29, 2023, 06:57 by d...@lynne.ee:
>>
>>> Oct 29, 2023, 05:51 by mich...@niedermayer.cc:
>>>
On Sat, Oct 28, 2023 at 09:23:45PM +0200, Lynne wrote:
> Oct 28, 2023, 18:49 by mich...@niedermayer.cc:
On 7 Nov 2023, at 22:44, Frank Plowman wrote:
> On 07/11/2023 20:38, epira...@gmail.com wrote:
>
>> On 7 Nov 2023, at 16:57, Frank Plowman wrote:
>>
>>> Resolves #10636 (http://trac.ffmpeg.org/ticket/10636)
>>>
>>> Texinfo 7.0, released in November 2022, changed the names of various
>>> function
On 7 Nov 2023, at 16:57, Frank Plowman wrote:
> Resolves #10636 (http://trac.ffmpeg.org/ticket/10636)
>
> Texinfo 7.0, released in November 2022, changed the names of various
> functions. Compiling docs with Texinfo 7.0 results in warnings and
> improperly formatted documentation. More old names a
On 7 Nov 2023, at 12:42, Lynne wrote:
> Nov 7, 2023, 12:25 by quinkbl...@foxmail.com:
>
>> Ping.
>>
>>> 在 2023年10月30日，下午4:17，Zhao Zhili 写道：
>>>
>>> From: Zhao Zhili
>>>
>>> VK_KHR_PORTABILITY_ENUMERATION_EXTENSION_NAME is required on macOS,
>>> and VK_INSTANCE_CREATE_ENUMERATE_PORTABILITY_BIT
On 27 Oct 2023, at 5:59, Dave Johansen wrote:
> ---
> doc/muxers.texi | 3 +++
> libavformat/hlsenc.c | 41 +
> 2 files changed, 28 insertions(+), 16 deletions(-)
>
Thanks for the revised patch!
> diff --git a/doc/muxers.texi b/doc/muxers.texi
> ind
On 26 Oct 2023, at 16:05, Niklas Haas wrote:
> On Thu, 26 Oct 2023 10:13:03 -0300 James Almer wrote:
>> On 10/26/2023 9:23 AM, Nicolas George wrote:
>>> Niklas Haas (12023-10-26):
From: Niklas Haas
---
libavfilter/drawutils.c | 3 ---
1 file changed, 3 deletions(-)
On 19 Oct 2023, at 21:05, Michael Koch wrote:
>> IIRC each regex give -10 so multiple matches give more.
>
> So far, the search strings contain only combinations of keywords, for example
> "concretevictoria".
> False positives are almost impossible.
>
> I could add shorter keywords, for exampl
1 - 100 of 117 matches
Mail list logo
