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
On Tue, 14 May 2024 19:07:59 -0700
Philip Langdale via ffmpeg-devel wrote:
> On Wed, 15 May 2024 01:36:43 +0530
> llyyr.pub...@gmail.com 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
llyyr.pub...@gmail.com 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
>
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
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
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.
> ---
>
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
>
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
ffmpeg-devel@ffmpeg.org
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
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
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
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 +
>
15 matches
Mail list logo
