= {CTL_MACHDEP, CPU_ALTIVEC};
> #else
> int sels[2] = {CTL_HW, HW_VECTORUNIT};
> --
> 2.44.0
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe,
.
> >
> > 95 GBP: Eurostar to Bruxelle-Midi
> > 95 GBP: Eurostar from Bruxelle-Midi
> > Total: 190 GBP
>
> LGTM
>
> PS: maybe we should make a page on trac that links to all talks from all
> FFmpeg developers
>
Is there video/audio from this talk? I would
LAGS) -showIncludes -Zs'
> _cflags_speed="-O2"
> _cflags_size="-O1"
> --
> 2.43.2
>
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
&
usted all other alternatives.
> -- Abba Eban
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmp
t; ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
Co
___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
Not sure if I am allowed to pick, my choice is D
-large: CMD = framecrc -i
> $(TARGET_SAMPLES)/exr/rgb_tile_half_piz_dw_large.exr -vf scale -pix_fmt
> gbrpf32le
>
> FATE_EXR += fate-exr-rgb-tile-uint32-piz-dw-large
> -fate-exr-rgb-tile-uint32-piz-dw-large: CMD = framecrc -i
> $(TARGET_SAMPLES)/exr/rgb_tile_uint32_piz_dw_large.
t
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
This also looks good to me.
-- Sean McGovern
uint8_t src[], int stride, PPContext *c)
> {
> -#if HAVE_7REGS && TEMPLATE_PP_MMXEXT
> +#if TEMPLATE_PP_MMXEXT && HAVE_7REGS
> DECLARE_ALIGNED(8, uint64_t, tmp)[3];
> __asm__ volatile(
> "pxor %%mm6, %%mm6 \n\t"
> --
&g
_
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
I already submitted this change a few we
Hi,
On Fri, Mar 8, 2024, 10:11 Sean McGovern wrote:
> On Wed, Mar 6, 2024, 18:48 Sean McGovern wrote:
>
>> The reference file uses BGRA pixel format, so request it here.
>> ---
>> tests/fate/ffmpeg.mak | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>>
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
OK, looks good to me.
Thanks,
Sean
___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Confirming this patch fixes fate-checkas
email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Confirming that this fixes fate-mpeg4-simple-studio-profile on PowerPC
QEMU with GCC UBsan as noted.
It was not failing on POWER7 (ppc64) or POWER9 (ppc64le).
Thanks,
Sean McGovern
_
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Confirming that this fixes 'fate-vsy
lman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Confirming that this fixes fate-v210 (and probably many more) on my
PowerPC QEMU setup -- it was not failing on POWER7 (ppc64) or POWER9
(ppc64le) and
th subject "unsubscribe".
First of all, thank you for looking into this.
Second, do we feel that this change covers the FIXME immediately above
it that exclaims "there has to be a better way"?
If so, we can remove the comment.
I did not perform a full FATE run as it is expensive
) $(CLEANSUFFIXES:%=libavfilter/dnn/%)
> $(CLEANSUFFIXES:%=libavfilter/opencl/%) \
> + $(CLEANSUFFIXES:%=libavfilter/metal/%) \
>$(CLEANSUFFIXES:%=libavfilter/vulkan/%)
>
> OPENCL = $(subst $(SRC_PATH)/,,$(wildcard
> $(SRC_PATH)/libavfilter/opencl/
gt; -include $(SRC_PATH)/libavcodec/x86/vvc/Makefile
> +-include $(SRC_PATH)/libavcodec/$(ARCH)/vvc/Makefile
> OBJS-$(CONFIG_AANDCTTABLES)+= aandcttab.o
> OBJS-$(CONFIG_AC3DSP) += ac3dsp.o ac3.o ac3tab.o
> OBJS-$(CONFIG_ADTS_HEADER) += adts_
On Fri, Mar 8, 2024, 10:37 Vittorio Giovara
wrote:
> On Fri, Mar 8, 2024 at 4:34 PM Sean McGovern wrote:
>
> > On Fri, Mar 8, 2024, 10:31 Paul B Mahol wrote:
> >
> > > On Fri, Mar 8, 2024 at 4:21 PM Vittorio Giovara <
> > > vittorio.giov...@gmail.com>
On Fri, Mar 8, 2024, 10:31 Paul B Mahol wrote:
> On Fri, Mar 8, 2024 at 4:21 PM Vittorio Giovara <
> vittorio.giov...@gmail.com>
> wrote:
>
> > On Fri, Mar 8, 2024 at 4:10 PM Sean McGovern wrote:
> >
> > > On Fri, Mar 8, 2024, 08:20 Nicolas George wrote:
On Fri, Mar 8, 2024, 10:19 Nicolas George wrote:
> Sean McGovern (12024-03-08):
> > Everybody can we *please* keep the responses civil/professional on the
> ML.
>
> Civil, certainly, provided others are civil to me.
>
> Professional, not a chance. This is L
It's been unreachable since yesterday.
-- Sean McGovern
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject
On Wed, Mar 6, 2024, 18:48 Sean McGovern wrote:
> The reference file uses BGRA pixel format, so request it here.
> ---
> tests/fate/ffmpeg.mak | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tests/fate/ffmpeg.mak b/tests/fate/ffmpeg.mak
> index 669c878c
g.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
Everybody can we *please* keep the responses civil/professional on the ML.
-- Sean McGovern
___
The reference file uses BGRA pixel format, so request it here.
---
tests/fate/ffmpeg.mak | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/fate/ffmpeg.mak b/tests/fate/ffmpeg.mak
index 669c878c7f..77e93693b9 100644
--- a/tests/fate/ffmpeg.mak
+++ b/tests/fate/ffmpeg.mak
@@ -62,6 +62,7
Iterate over 'pmax' instead of 'num_swb'.
---
libavcodec/aacenc_pred.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/aacenc_pred.c b/libavcodec/aacenc_pred.c
index a486c44d42..c5b8aa9665 100644
--- a/libavcodec/aacenc_pred.c
+++ b/libavcodec/aacenc_pred.c
@@
m and branch ?
> > > Iam not sure when the exact deadline is but if we keep waiting
> > > we will not get into ubuntu 24.04 LTS
> >
> > 24.04 is past feature freeze, so it's too late for that.
>
> we should aim earlier in the future then.
>
>
LTS i
tate = 16, pos
> = 2, op = 0;
>
> ht_init(ctx->color_lookback_ht);
Confirming that this does fix the failing test on a big-endian PowerPC
+ Altivec virtual machine.
Thanks,
Sean McGovern
___
ffmpeg-devel mailing list
ffmpeg-
Hi Andreas,
First off all, thanks for having a look! :)
On Tue, Feb 27, 2024 at 1:37 PM Andreas Rheinhardt
wrote:
>
> Sean McGovern:
> > ---
> > libavcodec/aacenc_pred.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/l
On Sun, Feb 25, 2024 at 1:44 PM Sean McGovern wrote:
>
>
> Here is the error reported by FATE (snipped for brevity) for
> 'fate-aac-encode-pred':
>
Ooops! I should copy-paste more often -- that should be
'fate-aac-pred-encode' :)
-
---
libavcodec/aacenc_pred.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/libavcodec/aacenc_pred.c b/libavcodec/aacenc_pred.c
index f87fcd5a00..d3efade85e 100644
--- a/libavcodec/aacenc_pred.c
+++ b/libavcodec/aacenc_pred.c
@@ -162,9 +162,11 @@ void
From: Sean McGovern
Hi FFmpeg-devel,
I've started looking into the results posted by the UBsan FATE node --
http://fate.ffmpeg.org/history.cgi?slot=x86_64-archlinux-gcc-ubsan
Here is the error reported by FATE (snipped for brevity) for
'fate-aac-encode-pred':
[aist#0:0/pcm_s16le @ 0x77fee40
fmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
Confirming this fixes #10868 for me.
Thanks,
Sean McGovern
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
gt; +
> +fprintf(stderr, "%d x %d %s -> %d x %d %s\n", srcW, srcH,
> desc_src->name, dstW, dstH, desc_dst->name);
> +//TODO Slices
> +sws_scale(sws, (const uint8_t * const*)src, srcStride, 0, srcH, dst,
> dstStride);
> +
> +end:
> +sws_fre
compilers modes
> - move to C17 at this mid-year when 7.1 is branched (LTS if we follow our
> plans)
>
I like this approach. It's a shame we can't get metrics on who might be
genuinely affected by a direct move to C17.
I'd be more than willi
Hi everybody,
Sorry I can't be at FOSDEM to meet you all again.
Unfortunately it always falls on a weekend I have to be available at home
for work.
-- Sean McGovern
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman
Hi,
On Thu, Oct 19, 2023, 07:44 Michael Niedermayer
wrote:
> On Wed, Oct 18, 2023 at 01:18:54PM -0400, Sean McGovern wrote:
> > On Sat, Oct 14, 2023, 23:27 Sean McGovern wrote:
> >
> > > It was not introduced until glibc 2.18.
> > > ---
> >
ove, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
Do we get to see the cute outfit when it is done? :)
-- Sean McGovern
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinf
Hi,
If I wanted to purchase a RISC-V developer kit, does anyone have
suggestions of what to buy? Or even what to steer clear of?
Thanks,
Sean McGovern
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
Tangential to the change, but I would be super curious to know if anyone is
using m
rg with subject "unsubscribe".
>
Saying it doesn't work is decidedly nebulous.
Also, ffmpeg-devel is a development-centered list and not the correct forum
for CLI usage help.
-- Sean McGovern
>
___
ffmpeg-devel mailing list
ffmpeg-devel@f
rawer.
>
> To Paul's Patch, a toast we raise,
> In the realm of software, you set ablaze.
> For every bug quivered, and every glitch shivered,
> Thanks to Paul's Patch, we code delivered!
>
> thx
>
> [...]
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611E
gt; https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
This is really unfair to Paul to let this drag on for so long.
If you are genuinely this busy,
if (!s->data)
> --
> 2.17.1
>
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffm
esize[0]) {
>
> bytestream2_get_buffer(, pixels + y_ptr,
> 3*s->avctx->width);
> --
> 2.17.1
>
> ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-
gt;
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
This and 1/2 seem a bit frivolous, but providing they don't violate the
project style guide, LGTM.
-- Sean McGovern
>
___
ff
On Thu, Oct 26, 2023 at 5:40 PM Sean McGovern wrote:
>
> On Tue, Oct 24, 2023 at 8:40 AM Sean McGovern wrote:
> >
> >
> >
> > On Tue, Oct 24, 2023, 08:23 Martin Storsjö wrote:
> >>
> >> Skip doing the whole getauxval(AT_HWCAP) if HWCAP_CPUID isn'
On Tue, Oct 24, 2023 at 8:40 AM Sean McGovern wrote:
>
>
>
> On Tue, Oct 24, 2023, 08:23 Martin Storsjö wrote:
>>
>> Skip doing the whole getauxval(AT_HWCAP) if HWCAP_CPUID isn't
>> defined.
>> ---
>> libavutil/aarch64/cpu.c | 6 +-
>&
mail
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
Looks OK to me.
-- Sean McGovern
>
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
; ___
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
>
Goo
On Sat, Oct 14, 2023, 23:27 Sean McGovern wrote:
> It was not introduced until glibc 2.18.
> ---
> This should fix the ppc32 FATE node.
> ---
> libavutil/ppc/cpu.c | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/libavutil/ppc/cpu.c b/lib
It was not introduced until glibc 2.18.
---
This should fix the ppc32 FATE node.
---
libavutil/ppc/cpu.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/libavutil/ppc/cpu.c b/libavutil/ppc/cpu.c
index 96b491c716..bc8bb5f47c 100644
--- a/libavutil/ppc/cpu.c
+++
53 matches
Mail list logo
