On Sun, 26 Oct 2025 17:01:51 +0100
Niklas Haas wrote:
> On Sun, 26 Oct 2025 14:56:30 +0100 Michael Niedermayer
> wrote:
> > Quick vote, should the delegation from where this came from, be
> > revoked to FFmpeg social media? (vote ends in 7 days)
> >
> > Please reply on ffmpeg-devel with your cho
On Tue, 21 Oct 2025 04:28:26 +0200
Lynne via ffmpeg-devel wrote:
> On 20/10/2025 18:14, Michael Niedermayer wrote:
> > Hi everyone
> >
> > We currently have 2 issue trackers (trac and forgejo),
> >
> > Previous discussion:
> > "[RFC] Issue tracker" and "trac ticket statistics"
> > https://lists
On Tue, 16 Sep 2025 10:49:00 +0200
Michael Niedermayer wrote:
> Hi all
>
> 2 months ago we voted on testing Forgejo vs Gitlab, we picked and
> tested Forgejo. And as said in that vote, (and surprisingly, i have
> not forgotten it) heres the "after testing" discussion and vote
>
> do we want to
On Mon, 7 Jul 2025 11:45:36 +0200
Diego Felix de Souza via ffmpeg-devel wrote:
> From: Diego de Souza
>
> The supported YUV pixel formats were separated between planar
> and semiplanar. This approach reduces the number of CUDA kernels
> for all pixel formats.
>
> This patch:
> 1. Adds support
On Tue, 8 Jul 2025 11:19:45 +
Diego de Souza via ffmpeg-devel wrote:
> Hi Andreas,
>
> Do you mean something like this?
>
> struct format_entry {
> enum AVPixelFormat format;
> char name[16];
> };
>
> static const struct format_entry supported_formats[] = {
> {AV_PIX_FMT_YUV420
On Sun, 13 Jul 2025 13:43:57 +0200
Michael Niedermayer wrote:
> Hi all
>
> Do people want Forgejo or Gitlab on code.ffmpeg.org for testing?
>
> F. code.ffmpeg.org should run Forgejo
> G. code.ffmpeg.org should run Gitlab
>
> all GA members can vote, by publically replying here with a
> "F." /
On Wed, 22 May 2024 11:10:31 -0400
"Ronald S. Bultje" wrote:
> Hi,
>
> On Wed, May 22, 2024 at 10:36 AM Hendrik Leppkes
> wrote:
>
> > On Thu, Feb 29, 2024 at 7:19 AM llyyr wrote:
> > >
> > > segmentation.update_map is never reset to 0 on a new frame, and
> > > retains the value from the pr
On Tue, 14 May 2024 19:07:59 -0700
Philip Langdale via ffmpeg-devel wrote:
> On Wed, 15 May 2024 01:36:43 +0530
> [email protected] wrote:
>
> > From: llyyr
> >
> > ab77b878f1 attempted to fix the issue of broken packets being sent
> > to the decode
On Wed, 15 May 2024 01:36:43 +0530
[email protected] wrote:
> From: llyyr
>
> ab77b878f1 attempted to fix the issue of broken packets being sent to
> the decoder by implementing logic that kept attempting to PTS-step
> backwards until it reached a valid point, however applying this
> heuris
On Wed, 31 Jan 2024 17:34:08 +0100 (CET)
Lynne wrote:
> The configure check already had fallback for the previous version
> of glslang, which had different requirements for flags.
> This commit simply moves the flags needed for glslang 13 to the
> fallback, while first trying to use new flags for
On Sat, 2 Dec 2023 23:02:36 +0100
Thomas Mundt wrote:
>
> LGTM, thanks.
>
I am going to squash the three commits and push. There's no real need
to put each filter in a separate diff when the logical change is
identical in all three.
Thanks,
--phil
On Sun, 29 Oct 2023 07:22:46 +0100 (CET)
Lynne wrote:
> Due to making the decode frames context use the coded size, the
> filter started to display those artifacts as it reused the input
> frame's size.
>
> Change it to instead output the real image size for images, not the
> input.
>
> Patch a
On Fri, 27 Oct 2023 12:00:10 +0200
David Rosca wrote:
> This allows some optimizations in driver, such as not having to read
> back the data if write-only mapping is requested.
> ---
> v3: Fix another warning
>
> libavutil/hwcontext_vaapi.c | 11 +++
> 1 file changed, 11 insertions(+)
>
On Fri, 27 Oct 2023 23:37:01 +0800
Zhao Zhili wrote:
> From: Zhao Zhili
>
> av_hwframe_transfer_data try with src_ctx first. If the operation
> failed with AVERROR(ENOSYS), it will try again with dst_ctx. Return
> AVERROR(EINVAL) makes the second step being skipped.
> ---
> libavutil/hwcontext
On Fri, 27 Oct 2023 23:37:00 +0800
Zhao Zhili wrote:
> From: Zhao Zhili
>
> Move it to transfer_get_formats.
> ---
> libavutil/hwcontext_vulkan.c | 25 +
> 1 file changed, 13 insertions(+), 12 deletions(-)
>
> diff --git a/libavutil/hwcontext_vulkan.c
> b/libavutil/hwc
On Thu, 5 Oct 2023 23:26:38 +0200 (CEST)
Lynne wrote:
> This fixes filtering on Nvidia.
>
> Patch attached.
>
Tested locally. Filtering works and vulkan validation passes.
Ship it!
--phil
___
ffmpeg-devel mailing list
[email protected]
https:
On 2019-04-06 09:42, Balint Marton wrote:
Hi All
Here is a call for the people in the voting committee [1] on the
decision of extending it.
Using the same guidelines as in the second extension [2], the
following candidates were found:
git log libav/master..master --no-merges --since=2018-03-3
On 2019-04-08 12:10, Marton Balint wrote:
I emailed Marton out-of-band, but I am not in the list because a few
of my recent commits
were pushed by Timo instead of me pushing them directly. My authored
list is 23 commits
but 4 were pushed by Timo, so Marton's command line returns '19' for
me.
On 2019-04-06 10:35, Marton Balint wrote:
On Sat, 6 Apr 2019, Jean-Baptiste Kempf wrote:
Hello,
On Sat, 6 Apr 2019, at 18:42, Balint Marton wrote:
Here is a call for the people in the voting committee [1] on the
decision of extending it.
Why do you limit at those ones? There are more commit
On Sat, 23 Mar 2019 16:18:48 +
Mark Thompson wrote:
> Set the cropping fields in the AVFrame.
> ---
> libavfilter/vf_crop.c | 74
> +-- 1 file changed, 51
> insertions(+), 23 deletions(-)
>
> There is the slightly unfortunate effect the filter links do
On Sat, 23 Mar 2019 23:51:10 +0800
UsingtcNower wrote:
> Signed-off-by: UsingtcNower
> ---
> Changelog | 1 +
> configure | 1 +
> doc/filters.texi| 31 +++
> libavfilter/Makefile| 1 +
> libavfilter/allfilters.c| 1 +
> libav
21 matches
Mail list logo
